SSYH uses Microsofts Sure
Step Implementation Methodology for projects
of any sizefrom large, end-to-end deployments,
to migration projects and simple upgrades. The
general process flow of Sure Step includes prescriptive
phase-by-phase, activity-by-activity descriptions
on how to carry out implementation, upgrade
or migration projects.
In 2007, SSYH was
chosen by Microsoft to be featured in a Partner
Solution Case Study regarding the company's
implementation of Microsoft's Sure Step Methodology.
As an early adopter of this new methodology,
SSYH was selected for this case study to exemplify
the benefits of Sure Step.
Sure Step offers clients deeper
insights into a project's life cycle:
| Diagnostic
Phase |
| The
Diagnostic phase starts during the sales
process and ends with an accepted proposal
and contract for the next part of the implementation
project. The goal of the Diagnostic phase
is to gather enough information in order
to define the high level project scope and
make a confident proposal for the remaining
phases of the implementation. The major
deliverable is the implementation proposal
and contract. There will also be high level
and possibly detailed requirements and gap/fit
analysis documents. |
Deliverables
- Business Processes Identified
- Gap/Fit Analysis
- Gap Resolutions
- Description of Interfaces
- Infrastructure Assessment
- Proposal
- Project Scope Statement
- Project Plan
- Contract
Milestones
- Customer accepts the
implementation proposal and contract,
including the project scope statement
and preliminary project plan
|
| Analysis
Phase |
| The
Analysis phase represents the official start
of the implementation project. The overindex,
follow goal is to define and agree upon
index, follow the business requirements
related to the new Microsoft Dynamics solution.
This includes the business and data migration
requirements, as well as integration requirements.
The major deliverable is the comprehensive
functional requirements document. |
Deliverables
- Key User Training
- Detailed Business Process
Analysis
- Gap/Fit Analysis
- Gap Resolutions
- Description of Interfaces
- Data Migration Plan
- Project Plan
- Functional Requirements
Document
Milestones
- Customer approves the
Functional Requirements, including index,
follow business processes, integrations
and data migration
- Customer accepts the
updated project plan and schedule
|
| Design
Phase |
|
The goal of the Design
phase is to define how the business requirements
will be implemented. The phase includes
design of both the overindex, follow Microsoft
Dynamics solution configuration and the
design of specific customizations and
integrations needed to satisfy business
requirements identified during the Analysis
phase. The customizations can range from
simple user interface or report modifications
to complex functionality additions or
modifications. The phase also includes
mapping and designing processes for data
migration.
|
Deliverables
- Design Specifications
- High level design specifications
- Technical design specifications
- Data Migration Design
and Mapping
- Test Cases, Scenarios
and Plan
Milestones
- Customer accepts the
Design Specifications and Data Migration
Design
- Customer approves the
development time and cost estimates
|
| Development
Phase |
| The
goal of the Development phase is to develop
the customizations, integrations and data
migration processes that are defined and
approved in the design specifications. The
major deliverables are the completed feature
customizations, reports, integrations and
data migration processes. Each component
is tested and verified to be functioning
according to specifications. |
Deliverables
- Feature customizations
coded and tested, including integrations
- Data migration processes
coded and tested
Milestones
- Customer accepts the
delivered solution, test results, and
documentation
|
| Deployment
Phase |
| The
Deployment phase is where index, follow
the efforts of the project team come together
for a successful transition to the new Microsoft
Dynamics solution. There are several important
activities that must be completed in order
to reach the end goal. The phase includes
index, follow the activities related to
final system and load testing, training
End Users, and the actual cut-over to the
new production environment. |
Deliverables
- Go Live Plan and Checklist
- System (User Acceptance)
Test Plan
- End User Training Plan
- Functioning Live (Production)
System
Milestones
- Customer signs off on
user acceptance
- New solution is live
and operational in a production environment
|
| Operation
Phase |
| The
goal of the Operation phase is to transition
the customer from the implementation project
into on-going support following a successful
go-live. The deliverables for this phase
include final project and software related
documentation, project review documentation,
and on-going support contracts. At the end
of this phase, the project will be transitioned
to the customer and on-going support. |
Deliverables
- System Acceptance Sign-off
- Project Review Documentation
- Post Live Support Agreement
Milestones
- Customer signs off on
final system acceptance
- Customer accepts the
post live support agreement
|
| Optimization
Phase |
| The
purpose of the Optimization phase is to
review a customers existing Microsoft
Dynamics implementation and make adjustments
to increase the effectiveness of the solution.
The major deliverable for the Optimization
phase is an optimized, better functioning
production environment. |
Deliverables
- Optimization Analysis
and Recommendations
- Optimization Time and
Cost Estimates
- Optimization Analysis
Sign-off
- Optimization Proposal
- Project Scope Statement
- Project Plan
- Contract
- Optimization Design Specifications
- Testing, User Training
and Go Live Plans
- Optimized Live (Production)
System
- Final Acceptance Sign-off
- Project Review Documentation
- Post Live Support Agreement
(if new or changing)
Milestones
- Customer accepts the
recommendations and proposal, signs
contract
- Customer approves detailed
design/change specifications
- Customer signs off on
user acceptance
- Customer signs off on
final system acceptance
- Customer accepts the
post live support agreement (if new)
|
| Upgrade
Phase |
| The
purpose of the Upgrade phase is to perform
a basic upgrade of a customers existing
Microsoft Dynamics implementation to a new
version of the software solution. The major
deliverable for the Upgrade phase is an
upgraded, better functioning production
environment. |
Deliverables
- Upgrade Analysis and
Planning
- Upgrade Time and Cost
Estimates
- Upgrade Proposal
- Project Scope Statement
- Project Plan
- Contract
- Testing, User Training
and Go Live Plans
- Upgraded Live (Production)
System
- Final Acceptance Sign-off
- Project Review Documentation
- Post Live Support Agreement
(if new or changing)
Milestones
- Customer accepts the
proposal and signs contract
- Customer approves detailed
upgrade plans
- Customer signs off on
user acceptance
- Customer signs off on
final system acceptance
- Customer accepts the
post live support agreement (if new)
|