Microsoft Dynamics Sure Step Methodology
The Diagnostic phase should kickoff by establishing the purpose and objectives of the potential engagement. This includes creating an understanding of the customer’s current situation, business environment, and the main pain points or areas of improvement, that have been identified. Information regarding current and future state is gathered in order to determine the scope of the Diagnostic phase and to identify the appropriate skill sets and resources required for the Diagnostic activities.
The Analysis phase represents the official start of the implementation. This phase defines the activities required to initiate and effectively plan the entire project
The goal of the Design phase is to define how the business requirements will be implemented. The phase includes configuration of the overall Microsoft Dynamics solution and the design of specific customizations needed to satisfy business requirements identified during the Analysis phase. The customizations can range from simple user interface or report modifications to moderate-to-complex functionality additions or modifications. Customizations may also include the integrations and interfaces and data migration elements required to support the requirements.
The goal of the Development phase is to build and test the system components defined and approved in the design specifications, including developing the customizations, integrations and interfaces, and data migration processes. The major deliverables include the complete system configuration, completion and freezing of code for customizations, integrations and interfaces, and data migration. Other key deliverables include finalization of the design specifications and the completion of Solution Testing. For an Enterprise project, this may also include Data Acceptance, Process and Integration Testing.
The Deployment phase is where all the efforts of the project team come together for a successful transition to the new Microsoft Dynamics™ solution. Key activities in this phase include End User Training, User Acceptance Testing, and the actual cutover to the new or upgraded production environment. For Enterprise projects, Performance Testing is also completed.
The Operation phase defines the activities required to close the project, provide post-production support, and transition the solution and knowledge to the customer. Key objectives of this phase include providing post–go-live support, transitioning the solution to support, performing a final quality audit, and project closure.