Editar

Compartir a través de

Use the go-live checklist to make sure your solution is ready for go-live

  • Artículo

Before you launch your Microsoft Dynamics 365 solution, you need to make sure that it meets your business needs and works as expected. The go-live checklist helps you assess the readiness, completeness, and quality of your solution and make informed decisions about going live.

The checklist covers the following areas:

Go-live readiness

Done? Task
✓ Align the solution scope with the solution that's going live, share it with stakeholders, and get their agreement.
✓ Complete all test cycles with exit criteria met and signed off by the business stakeholders. The recommended test cycles include system integration, performance, user acceptance, and other tests.
✓ Test and sign off on all scripts and processes that are planned for the cutover migration.
✓ Align external dependencies, such as partner systems and services, with the timelines and scope for go-live.
✓ Plan and implement all change management activities from the Initiate through the Prepare phases, such as training, user support, user engagement, and communication.
✓ Have a plan for monitoring and maintenance for production and for transitioning to support teams.
✓ Prepare the production environment and train administrators and IT on monitoring, troubleshooting procedures, and support options.
✓ Create a cutover plan that considers all dependencies, the timing of activities, roles and responsibilities, instructions, verification steps, and any other documentation that's associated with each activity.

Cutover

Done? Task
✓ Complete all activities in sequence.
✓ Meet the exit criteria.
✓ Get sign-off from stakeholders at the cutover go/no-go checkpoint.

Solution scope review

Done? Task
✓ Explain the scope of the project to business stakeholders in terms of the business processes that the solution supports.
✓ Consider the following items:
  • The business processes that the solution supports
  • The applications and solutions that are used in the solution
  • Whether the solution contains customizations and ISV solutions
  • The type and volume of integrations
  • The number of go-lives or rollouts
  • The number of users at go-live and in future rollouts
✓ Get sign-off from business stakeholders on the solution scope.

The solution scope review helps you confirm that the solution you're going to launch meets your business needs and expectations. The expected outcome is that the solution scope matches the solution that's going live, you've shared it with stakeholders, and they agree that it covers their expectations. The risks of not reaching this outcome are delays, dissatisfaction, and project failure.

Solution acceptance review

Done? Task
✓ Test all aspects of your complete solution.
✓ Complete end-to-end unit testing successfully.
✓ Get sign-off from business stakeholders on the solution acceptance.

The solution acceptance review helps you confirm that the solution you're going to launch works as expected and meets your business needs. The expected outcome is that you've completed end-to-end unit testing successfully and business stakeholders have signed off on the results. The risks of not reaching this outcome are operational difficulties, technical issues, and project failure. To avoid problems with solution acceptance, follow the testing strategy best practices and perform several types of tests before going live, especially user acceptance testing (UAT), performance testing, and system integration testing (SIT).

User acceptance test completion

Done? Task
✓ Test all requirements in scope, both "happy path" and edge scenarios.
✓ Test with migrated data to validate how data behaves in real life.
✓ Assign correct security roles to users. Don't use a general security role or assign the System Admin role to all users.
✓ Comply with regulatory requirements specific to your company, industry, or country/region. Document all features and testing results.
✓ Run UAT in an environment in a Microsoft apps subscription so that it approximates your production environment as much as possible.
✓ Get sign-off from business stakeholders on UAT.

UAT helps you validate that the solution you're going to launch supports all the expected business processes and meets user needs. The expected outcome is that you've tested all requirements in scope, used migrated data, assigned correct security roles, complied with regulatory requirements, and conducted UAT in an environment that approximates production. The risks of not reaching this outcome are delays, difficulties, and project failure. Address any items identified during UAT with an owner and a completion date for each.

Performance testing completion

Done? Task
✓ Test load times with peak volumes of transactions.
✓ Test data search performance.
✓ Test end-to-end processes and specific business processes.
✓ Test performance on different devices, browsers, and virtualized environments.
✓ Test integrations.
✓ Test in representative environments, data, and test cases that can reliably predict performance in production.
✓ Get sign-off from stakeholders on performance testing.

Performance testing helps you ensure that the solution you're going to launch can handle the expected load and speed of your business processes. The expected outcome is that the solution performs as expected and meets the business performance criteria. The risks of not reaching this outcome are issues with the system's performance after go-live that can be difficult or expensive to fix. Do performance testing in parallel with UAT in a test environment before going live and address any issues with an owner and a completion date.

System integration testing completion

Done? Task
✓ Test with expected peak volumes.
✓ Simulate external systems that are down and how those scenarios are communicated and affect the user experience.
✓ Get sign-off from stakeholders on SIT.

SIT helps you validate that the solution you're going to launch works well with other applications and external systems. The expected outcome is that the solution and its integrations work as expected and you have a plan for handling unexpected situations. The risks of not reaching this outcome are issues with the integrations after go-live. Do SIT before UAT in a test environment before going live and choose the right integration pattern for your solution.

Data migration readiness and validation

Done? Task
✓ Test data migration several times before cutover.
✓ Validate your strategy and processes, identify and address issues of data corruption or duplication, and make sure performance fits in the cutover time window.
✓ Test and sign off on all scripts and processes planned for cutover migration by the business.
✓ Log any migration issues and risks and make a mitigation plan.

Data migration readiness helps you ensure that the data you're going to use in your solution is accurate, complete, and available. The expected outcome is that you've tested data migration several times before cutover, validated your strategy and processes, addressed any issues or risks with the data migration, and got sign-off from the business. The risks of not reaching this outcome are delays or difficulties in go-live migration, inaccurate or corrupted data in your solution, and reduced user and customer confidence. Prepare a migration plan and execute multiple dry runs, prepare configuration data, master data, security configurations, open transactions, and balances in advance, and follow recommended practices for data management.

Confirmation of external dependencies

Done? Task
✓ Align any external dependencies, such as ISV solutions and partner systems and services, with your timelines and scope for go-live.
✓ Coordinate with providers to make sure expectations are aligned, their solutions match the roadmap timelines, and all requirements are met.

Checking external dependencies helps you ensure that the solutions, systems, or services you need for your project are compatible and reliable. The expected outcome is that the dependencies and their interactions work as planned and you have a strategy for dealing with potential problems. The risks of not reaching this outcome are delays or failures in your project due to dependency issues. To avoid problems with external dependencies, coordinate with the providers of the dependencies, align your expectations, timelines, and requirements with them, and have regular meetings to review their status and resolve any conflicts.

Change management for initial operations readiness

Done? Task
✓ Assess change readiness early in the project and reassess throughout.
✓ Deliver effective training to users on how to use the new solution.
✓ Engage users with the solution and get their input and feedback.
✓ Communicate the value of the new solution with business sponsorship.
✓ Create a community of super-users and provide resources for user support.

Change management readiness helps you ensure that your organization adopts and engages with the new business solution you're launching. The expected outcome is that you assess and address the needs and concerns of the users throughout the project, and provide them with training, communication, sponsorship, and support. The following key elements help drive change management close to go-live:

  • Training: Teach users how to use the new solution effectively and efficiently before they start working with it.
  • User engagement strategy: Involve users in the design, testing, and feedback of the solution, and keep them informed and excited about the benefits.
  • Business sponsorship: Get a trusted and influential leader to champion the solution and communicate its value to the organization.
  • User support: Create a community of super-users and provide resources and service notifications to help users after go-live.

The risks of not reaching this outcome are poor execution, low confidence, and resistance to the new solution. To avoid problems with change readiness, reassess the change management plan throughout the implementation project.

Operational support readiness

Done? Task
✓ Have a system monitoring and maintenance plan for the production environment.
✓ Have a plan for transitioning operational support from the implementation team to a support team.
✓ Train support teams on the solution and give them the resources, tools, and access they need.
✓ Have a help desk and ticket management process in place.
✓ Notify stakeholders and users when the system is ready to go into production and provide them with a support contact.

Support readiness helps you ensure that your solution works well and meets the needs of the users after it's live. The expected outcome is that you have a plan to transition support from the implementation team to the support team, and that the support team has the resources, tools, access, and training they need to provide help. The following items should be included in the operational support and maintenance plan:

  • Continuous deployment plan: Stay updated on the latest version of the system and incorporate new features and fixes as soon as possible.
  • Monitoring: Track performance issues, errors, feature usage, and adoption to manage and report on the post-go-live process.
  • Hypercare: Provide an elevated level of support right after go-live to ensure smooth adoption.

The risks of not reaching this outcome are poor communication, delayed resolution, and unexpected updates that might affect system operations. Plan to transition support before go-live and share the plan with all parties involved.

Next steps