Step 2: Analyze

Identify and understand core project goals and deliverables

The Analysis phase marks the official start of the implementation project. The activities in the Analysis phase help identify the decisions the customer must make that will guide the implementation. This phase builds on the Diagnostic phase activities, and involves:

  • Review ‘as-is’ business processes to develop the ‘to be’ (future state) processes.
  • Determine and document the functional requirements for the solution in the Functional Requirements Document (FRD).
  • Describe improved business processes.
  • Describe any modifications needed for the system to support future business processes.
  • Sign-off the documented and finalized FRD.

The analysis work in this phase goes much deeper than the high-level analysis performed in the Diagnostic phase. At the end of this phase, the customer should have a detailed understanding of the proposed Microsoft Dynamics implementation. This includes the project cost, deliverables, and milestones.

Although the deliverables for the Analysis phase will vary slightly dependant on the project type, they can include:

  • Project Kick-off
  • Project Charter
  • Project Plan
  • Risk Register and Issues List
  • Change Control Plan
  • Communications Plan
  • Training Plan
  • Future State Business Process Workflows
  • Functional Requirements Document (FRD)
  • Fit Gap Analysis Spreadsheet
  • Quality and Testing Standards (Test Plan)
  • Infrastructure Scope Document
  • Infrastructure Design Document
  • Integration and Interface Requirements
  • Data Migration Requirements

View pages within this section: