Dynamics Implementation Methodology

Key to success of an ERP Implementation is how the solution is implemented and how the implementations are managed.Considering this as the background Microsoft has developed Sure Step as the methodology for the Microsoft Dynamics solutions.

Sure step enablers:

  • Managed Project Execution.
  • Overriding Issue of traceability such as tracing of gaps between customer needs and final deliveries.
  • Proper documentation of all activities.
  • Improved quality of deliverables.
  • Procedural approach for formal acceptance on our understanding from Customers.

Why Sure step?
Sure step helps to interconnect Requirement, Requirement Meetings,Customer expectation,Development and Delivery.

Sure step helps pre sales team to understand and explain business requirement and mapping of customer using Diagnostic phase offering, The purpose of the Diagnostic phase is to collect information to define a high-level project scope and then create a customer proposal for the implementation project.

Best suited 5 phased implementation approach for Dynamics Implementations as depicted below:

  • Analysis phase-The Analysis phase marks the official start of the implementation project.

Objectives :

      • Finalization and approval of the project charter.
      • Finalization and approval of the project plan.
      • Exceution of the project kick off meeting.
      • Documentation and approval of functional and non functional requirements.
      • Execution and documentation of Fit Gap Analysis.
      • Assessment of the architecture and infrastructure.
      • Development of the organizational change management strategy,communications strategy and training strategy.

Milestones :

      • Formal project kick off meeting.
      • Customer approval of Project charter and project plan.
      • Customer approval of requirements and fit gap analysis.

Deliverables :

      • Project charter.
      • Project Plan.
      • Risk and Issues Register.
      • Fit Gap Analysis sheet.
      • Functional Requirements Document(FRD).
      • Infrastructure scope and design document.
      • Business process maps/workflows document.
      • User training requirements document.
      • Data migration requirements document.
      • Organizational change management strategy plan.
      • Communications strategy plan.
      • Training strategy plan.
  • Design Phase-The goal of the Design phase is to define how the customer’s business requirements will be implemented.


      • Core team training.
      • Configurations of overall solution.
      • Design for customization can range from simple to complex functionalities.
      • Integration points,Customizations may include integrations and interfaces.


      • Core team training completion.
      • Design specifications acceptance from customer.
      • Approval of development time line and cost estimates.


      • Functional design document (FDD) for Standard configurations,Gaps ,Integrations Interfaces and Data Migration requirements.
      • Solution design document(SDD).
      • Technical design document(TDD).
  • Development Phase-The purpose of the Development phase is to develop the customization, integrations, and data migration processes defined in the design specifications created and approved in the Design phase.


      • Customization development.
      • Major deliverables.
      • Solution testing.


      • Completion of Development.
      • UAT Testscripts.


      • Final system configuration.
      • Final Custom Code Development.
      • Solution testing to be completed.
      • Final Integration Code Development.
      • Final Data Migration Code Development.
      • UAT Test scripts.
      • Final production environment specification.
  • Deployment Phase-The primary deliverable from the Deployment phase is a functioning live system.


      • Deployment plan of new dynamics solution for successful transition.


      • End user training.
      • UAT complete.
      • Production environment readiness.
      • Final data migration.
      • System go live.


      • UAT Test Results.
      • End User Training.
      • Final system readiness and Go live checklist.
      • Production Environment.
      • Cutover to production.
      • Mile stones.
      • End user training complete.
      • UAT complete.
      • Production environment readiness.
      • Final data migration complete.
      • System go live.
  • Operation Phase-The purpose of the Operations phase is to support the customer technically and functionally during the initial Go Live period for the new system.


      • Close the project.
      • Provide post production support.
      • Transition the solution and provide knowledge to customer.


      • Post Go live support complete.
      • Transition of solution to support complete.
      • Formal project closure.
      • System acceptance and sign off.


    • Project closure report.
    • Final Delivery of all project deliverables to customer.

The above depicted explanation is high level information about sure step ,we can use below resources to follow specific documentation and templates about sure step.

Sure Step 2012 and Sure Step Online:

Sure Step 2012 and Sure Step Online provide options for agile project types, industry, organizational change management, extended CRM development projects and ISV templates. Sure Step projects can be created in both SharePoint 2010 and SharePoint 2007.

Partners can get Sure Step content by downloading the application into their personal computer, or access it in its online format via Sure Step Online.

Sure Step Online Overview -View the latest guidance and content available online without downloading and installing the client. This is a great way to access and share content quickly from anywhere in multiple languages.

Leave a Reply