home
>
services
>
implementation
What can we expect from Crestwood during our implementation?
Crestwood follows the Microsoft Dynamics Sure Step model which consists of six primary phases that outline an implementation project:
- Diagnostic
- Analysis
- Design
- Development
- Deployment
- Operations
Each phase consists of activities that progress through the phase in sequence. Most activities consist of tasks, and some tasks have sub-tasks. In most cases, you complete one activity before you start the next. The work that results from an activity or task provides guidance and input into the next activity.
1. Diagnostic Phase
The first phase described in Microsoft Dynamics Sure Step is the Diagnostic phase. The high-level planning and high-level analysis of business processes and infrastructure carried out during the Diagnostic phase are usually an important part of the sales cycle. The goal of the Diagnostic phase is to collect information to define a high-level project scope and then create a finalized customer agreement for the implementation project.
The Diagnostic phase maps to the Solution stage of the Sales Solution Process and culminates in project proposals accepted by the customer. Typically, performing the Diagnostic phase activities will build customer confidence in the validity of the proposed solution before the implementation begins.
The work that performed in the Diagnostic phase results in several key deliverables. Because of the systematic nature of Microsoft Dynamics Sure Step, these deliverables provide important input into the phases of the implementation process.
- Requirements and Process Review report
- Fit and Gap Solution Blueprint report
- Proof of Concept including Conference Room Demonstration if necessary
- Architecture Assessment Report
- Scoping Assessment
- Business Case is usually recommended
- Project Planning Report including High-Level Project Charter, High-Level Project Plan for desired project type and Work Breakdown Structure for desired project type
- Statement of Work and Budgetary Estimate Proposal
2. Analysis Phase
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 documenting 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
3. Design Phase
Building on the deliverables created during Analysis, this phase consists of determining the design for the overall Microsoft Dynamics implementation and designing solutions for specific customizations, integrations, and data migration needed to satisfy business requirements identified during the Analysis phase.
The primary deliverables from this phase are a high-level design specification and a detailed technical design specification, both that satisfy the high-level decisions determined in the previous phases. These design specifications will guide the development activities in the following phase.
The key objectives to achieve during the Design phase are:
- Core team training.
- Functional design specifications for Fit Gap solutions, Integration and Interfaces and Data migration.
- Technical design documents.
- Initial draft of the Solution Design Document.
4. Development Phase
The primary purpose of the Development phase is to develop the customizations, integrations, and data migration processes defined in the design specifications created and approved in the Design phase, and to complete the setup and configuration of the standard solution and any ISV solutions.
The primary deliverables of Development phase are the completed and tested setup, configurations, customizations, reports, integrations, and any data migration programs and processes. Each component developed in this phase is tested and verified to be functioning as defined by the Functional requirements, design specifications, and testing criteria.
Although the deliverables for the Development phase will vary slightly dependant on the project type, they can include:
- Training Guides/Documentation
- Final Process Models
- Final System Configuration
- Final Custom Code Development
- Data Acceptance, Process and Integration Testing complete
- Performance Test and User Acceptance Test Scripts developed
- Production Environment Specification generated
- Final Integration and Interface Code DevelopmentFinal Data Migration Code Development
- Final Solution Design Document (SDD)
5. Deployment Phase
The primary deliverable from the Deployment phase is a functioning live system. Activities in this phase prepare the infrastructure, application environment, and end-users for the cutover to the new system.
Activities in this phase include:
- Prepare Go-Live plans and system test plans.
- Confirm end-user training plans as part of the finalized deployment plan.
- Configure the live and test environments.
- Perform system testing and load testing using a subset of the customer's data.
- Prepare and delivering end-user training.
- Complete final data migration and validation.
- Complete all Go-Live activities to launch the new system.
The primary deliverables from the Deployment phase include all tasks that are required to deploy the new solution to the live environment so that the customer can start to use it in day-to-day business processes. Although the deliverables for the Deployment phase will vary slightly dependant on the project type, they can include:
- Deployment Plan
- Train-the-Trainer (TTT) Training
- End User Training
- User Acceptance Test Results
- Initial Data Migration
- Production Environment Readiness
- Production Operations Guide
- Go-Live Readiness Review and Customer Sign-Off
- Cutover to Production
6. Operations Phase
The primary purpose of the Operations phase is to support the customer technically and functionally during the initial Go Live period for the new system. At the end of the phase, the project is transitioned to the customer, and we welcome the opportunity to provide on-going support and continued account management.
For smooth and successful Dynamics GP implementations, contact Crestwood Associates, your Chicago, Illinois, Wisconsin and Indiana source for successful consulting engagements and effectively managed implementations.
|
