Delivering business solutions is more than just product play. Software is often viewed as the enabler; however, the key to success is how the solution is implemented and how the implementations are managed. With this as the background, Microsoft has developed Sure Step as the full lifecycle methodology for the Microsoft Dynamics solutions portfolio.

1. AmarnathGupta
Project Manager
Email: imagpt@outlook.com

2. WHAT IS SURE STEP
 Delivering business solutions is more than just product play.
 Software is often viewed as the enabler; however, the key to
success is how the solution is implemented and how the
implementations are managed.
 With this as the background, Microsoft has developed Sure Step
as the full lifecycle methodology for the Microsoft Dynamics
solutions portfolio.
 We always need to work on the same stage is not the foundation
of the time, but it may be limitation of our intelligence.

3. REASONS FOR FAILURE OF ERP IMPLEMENTATION
RigidOrganization Process
Unmanaged Project Execution
Lack ofTraceability
Non DocumentedActivities and Poor Deliverables
Lack of Formal Acceptance from Customers on our
understanding

4. WE SHALL COVER
What is Microsoft Sure Step
Why Microsoft Sure Step
Implementation Phases

5. WHY SURE STEP
 When we are working a working professional with an organization, this is
our duty to be remained focus upon process oriented structure.
 Having implementing Dynamics AX in legacy methodology, create huge
gap between customer need and final deliveries.
 We face major issue of Traceability, and end up facing customer
complaints on non deliverance of their objective.
 Not by capturing customer requirement and depicting them in
architectural form of Dynamics ERP applications, create to have no
interconnection between Requirement <–> Requirement Meetings <–>
Customer Expectation <–> Development <–> Delivery
 Bringing Sure Step as our unified methodology, suitable for entire
Microsoft Dynamics Family, we get maximum uprooting and highest CSAT.

6. WE SHALL LEARN-
 how to effectively use Microsoft Dynamics Sure Step to implement the
right Dynamics business solution with quality, on-time and on-budget
results.
 to leverage the Decision Accelerator offerings in Microsoft Dynamics Sure
Step to create consistent selling motions while helping your customer
ascertain the best solution to fit their requirements.
 to understand the review and optimization offerings available from
Microsoft Dynamics Sure Step to further enhance our business solution
delivery during and after go-live.
 gain knowledge of the project and change management content provided
in Microsoft Dynamics Sure Step.
 to familiarize yourself with the approach to adopting the Microsoft
Dynamics Sure Step methodology as your own.

8.  Diagnostic offering
helps Pre-sales team to
understand and explain
business requirement
and mapping of
customer.
 Best Suited 5 phase
implementation
approach
 Cross phase activities
keeps tightly connected

9. SOLUTION DELIVERY AND PROJECT TYPE
 The Standard project type is a lean approach for implementing Microsoft Dynamics solutions at a single site.
 The Rapid project type depicts an accelerated approach for implementing Microsoft Dynamics solutions with minimal
or no customizations.
 The Enterprise project type represents a standardized approach for implementing Microsoft Dynamics solutions in
complex single-site deployments, or in global/multi-site organization wherein country/site specific unique business
needs have to be factored on top of a core solution.
 The Agile project type represents an iterative approach to implementing Microsoft Dynamics Solutions at a single site
requiring specific features and moderate-to-complex customizations. While the Standard, Rapid, Enterprise and
Upgrade project types are waterfall-based, the Agile project type uses the Sprint cycle approach to solution
deployment.
 The Upgrade project type describes the approach to progress an existing Microsoft Dynamics solution to a subsequent
release of that solution. This approach starts with a Technical Upgrade to address moving existing functionality to the
subsequent release. Any new functionality desired can then be deployed using the above project types, Rapid, Standard,
Agile or Enterprise.

10. Key Purpose
and
Deliverables

11. Analysis Design Development Deployment Operation

12. OBJECTIVES
Standard,Agile, Rapid and Upgrade
• Finalization and approval of the project
charter.
• Finalization and approval of the project
plan.
• Execution of the project Kickoff meeting.
• Documentation and approval of functional
requirements.
• Execution and documentation of Fit Gap
Analysis.
Enterprise – Additional
• Execution of executive kick off meetings
• Development of the organization change
management strategy, communications
strategy and training strategy
• Documentation and approval of functional
and non-functional requirements
• Development of the future state business
process models
• Definition of the master data taxonomy
and management process
• Assessment of the architecture and
infrastructure
Analysis

13. DELIVERABLES
Mandatory
Baseline
• Project Charter
• Project Plan
• Risk and Issues Register
• Functional
Requirements
Document (FRD)
• Fit Gap Analysis
Spreadsheet
Standard, Agile
and Rapid
• UserTraining
Requirements
• Business Process
Maps/Workflows
• Environment
Specification
• Data Migration
Requirements
Enterprise Projects
• Organization Change Management
Strategy
• Change Control Plan
• Communications Strategy and Plan
• Training Strategy and Plan
• UserTraining Requirements
• Future State Business Process Workflows
• Development Standards
• Quality andTesting Standards
• Infrastructure Scope Document
• Infrastructure Design Document
• Integration and Interface Requirements
• Data Migration Requirements
Upgrade
• Conduct Solutions
Overview
• UpgradeTest Plan
• Data Upgrade
Requirements
Analysis

14. MILESTONES
Formal Project Kickoff
Meeting
CustomerApproval of
Project Charter and
Project Plan
CustomerApproval of
Requirements and Fit
GapAnalysis
Infrastructure and
Environment
definition (All except
Upgrade Projects)
CustomerAcceptance
of the UpgradeTest
Plan (Upgrade
Projects only)
Analysis

15. OBJECTIVES
Implementation
Approach
• The goal of the
Design phase is to
define how the
business
requirements will be
implemented.
Configuration
• It includes
configuration of the
overall Microsoft
Dynamics solution
and the design of
specific
customizations
needed to satisfy
business
requirements
identified during
theAnalysis phase.
Design for
Customization
• The customizations
can range from
simple user
interface or report
modifications to
moderate-to-
complex
functionality
additions or
modifications.
Integration Points
• Customizations
may also include
the integrations and
interfaces and data
migration elements
required to support
the requirements.
Design

16. DELIVERABLES
CoreTeamTraining
• CoreTeam at
customer side who
will impart in brain
storming and UAT
Functional Design
Documents (FDDs)
• Standard
Configurations
Functional Design
Documents (FDDs) for
Gaps
• Requirements
indentified as Gaps in
Standard Solution
• Integration and
Interface Requirements
• Data Migration
Requirements
Technical Design
Documents (TDDs)
Solution Design
Document (SDD)
Additional for Enterprise:
• ProcessTest Scenarios
• Non-Production
Environment Specification
Design

17. MILESTONES
Core team training
complete
Customer accepts
the Design
Specifications
Customer
approves the
development time
and cost estimates
Design

18. OBJECTIVES
Customization
Development
• 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.
Major
Deliverables
• The major deliverables
include the complete
system configuration,
completion and freezing of
code for customizations,
integrations and interfaces,
and data migration.
Key Objectives to
be accomplished
• Other Key Objectives to be
accomplished 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.
Development

19. DELIVERABLES
Final Business Process
Models
Final System
Configuration
Final Custom Code
Development
SolutionTesting
(Process, Integration,
and Data Acceptance)
completed
User AcceptanceTest
Scripts
Final Production
Environment
Specification
Final Integration and
Interface Code
Development
Final Data Migration
Code Development
Development

20. MILESTONES
Core Microsoft Dynamics
application Upgrade
complete
ISV Solution Upgrade
complete (if applicable)
CustomizationCode
Upgrade complete
Integration and Interfaces
Upgrade complete (if
applicable)
UpgradeTesting complete
Data verification via
benchmarks complete
UserAcceptanceTest (UAT)
Test Scripts
development/confirmation
complete
Customer sign-off for
Production Environment
technical architecture
Development

21. OBJECTIVES
Getting ready for customer delivery and Go-Live
• The Deployment phase is where all the efforts of the project
team come together for a successful transition to the new
Microsoft Dynamics™ solution
Deployment

22. DELIVERABLES
End UserTraining
UserAcceptance
Test Results
Final Data Migration
(excluding Upgrade
Projects)
Final System
Readiness & Go-Live
Checklist
Production
Environment
Cutover to
Production
Additional Deliverables
for Enterprise Projects
• Deployment Plan
• Train-the-Trainer (TTT)
Training
• Production Operations Guide
Deployment

23. MILESTONES
End UserTraining
complete
UserAcceptance
Testing complete
Production
Environment ready
Final Data
Migration complete
(excluding Upgrade
Projects)
System Go-Live
Additional Milestones
for Enterprise Projects
• Training ofTrainers
• PerformanceTesting
Deployment

24. OBJECTIVES
Let’s plan to make it success by supporting customer
• Close the project
• Provide post-production support
• Transition the solution and knowledge to the customer
Operation

25. DELIVERABLES
Project Closure Report
Final Delivery of all Project
Deliverables to the customer
Documented Lessons Learned
Operation

26. MILESTONES
Post–Go-Live
Support complete
Transition of
solution to
Support complete
Formal Project
Closure
System
Acceptance and
Sign-off
Operation