You can use a Transition Plan Document to describe how project deliverables will be brought to full operational status, integrated into ongoing operations and maintained.

Use the Transition Plan to:

  • Identify transition planning strategies. Schedule the transition from rollout to full operational status.
  • Describe facilities needed to support the deliverable system.
  • Estimate training requirements for users, operations and support.

Table of Contents

1 Introduction
1.1 Purpose of this document
1.2 Product
1.3 Customer information
1.4 Scope
1.5 Risks
1.6 Issues
1.7 Dependencies
1.8 Key Stakeholders
1.9 Relationship to Other Plans
2 Management Approach
2.1 Project Budget
2.1.1 Project Budget location
2.2 Schedule
2.3 Training
2.3.1 Required Skill Levels
2.3.2 Training Needs
2.3.3 Training Plan
2.4 Roles and Responsibilities
2.5 Resource Allocation Chart
3 Communication Plan
4 Transition Planning
4.1 Identify Strategies
4.2 Evaluation Process
4.3 Release Process
4.4 Data Migration
4.5 Performance Measures and Reporting
4.6 Governance and Management Approach
4.7 Problem Resolution
4.8 Documentation Strategies
4.9 Sustainability metrics
4.10 Installation
4.11 Operations and Support
4.12 Maintenance
5 Resource Requirements
5.1 Software Resources
5.2 Hardware Resources
5.3 Facilities
5.4 Other Resources
6 Acceptance Criteria
7 Management Controls
8 Transition Impact Statement
9 Review Process
10 Configuration Control
10.1 Change Classifications
10.2 Identification of Proposed Changes
10.3 Documentation of Proposed Changes
10.4 Evaluation of Proposed Changes
10.5 Problem Resolution Tracking
10.6 System Change Requests
10.7 Configuration Management Libraries
10.8 Release Management
10.9 Version Control
Appendix A
Glossary of Terms

If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at This email address is being protected from spambots. You need JavaScript enabled to view it.



blog comments powered by Disqus