Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2021
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I understand we have the go-live check list, after UAT. How do we handle the phased go-live rapid turn projects? We could have a situation where we have a live on September 1st and a planned UAT starting on August 13th for two weeks with a one week cutover plan.
However in the guide it states: "Typically, the checklist is completed four to six weeks before the proposed go-live date, when UAT is completed or almost completed." In this scenario the UAT is complete 1 week before the proposed live date, to it is not typical - but is this still acceptable?
This leads onto part 2 which is the telemetry and elements Microsoft focus upon to decide if the customer is go-live ready. What are these and when would the Microsoft solution architect say "No" or will it always be a recommendation or mitigation plan but ultimately the customer can request the production environment?
Hello Weaveriski , thank you for your question! Our charter is to enable successful go-lives, not to prevent them, while at the same time ensuring that go-lives are happening with good quality and to decrease the risk of escalations and issues after go-live.
Our SLA for the assessment report is 2 business days, and DSE team’s SLA for Production deployment is another 2 days.
In your example – UAT starting August 13, planned for 2 weeks; cutover starting August 27; go-live September 1 - it would be best to send the fully populated checklist after the first week of UAT, no later than August 20. Assuming that everything looks good and there are no mitigations whatsoever, we would send you the Assessment report no later than Wednesday, August 22, and deploy Production immediately afterwards, provided that you have requested it.
We look for good usage of the UAT environment over the UAT period – e.g. not just one day where all data got uploaded and then no further usage. We like to see a good mix of activity that tests the real end-to-end processes.
Some of the most common issues that we call out are the following:
Microsoft FastTrack Solutions Architect
In many cases the success of a go-live can only be measured many months later :-) If the customer insists upon going live despite all recommendations from the partner or Microsoft will they still be allowed to have access to a Production system and go-live?
Hello Steve, ultimately, we do not refuse the Production environment deployment, if the code has been fully tested on a sandbox environment. If there are open issues that the customer does not want to address before going live, we will ask for a confirmation from the customer that they fully understand the risks and that they understand their responsibility to put mitigations in place. It is important for us to ensure that both the partner and the customer are on the email thread of the assessment report. What we have seen in some projects where there were many issues turning up in the assessment is that they rethink their approach to Go-live in terms of date and scope.
Business Applications communities