Transition Plan
Transition plan is a document that describes how the outputs of a project will be transferred either to another organization or to a functional group within the performing organization.
- describes how the project team will transition work to permanent owners at the end of the project
- create during the planning phase
- can create a transition plan as a checklist or a detailed document
Transition Plan Elements
- Roles and responsibilities
- Include
- who owns the transition plan
- who will complete transition activities
- who will own various maintenance activities
- Include
- Transition schedule
- Define the schedule of transition activities
- when the project team will officially end work on the project
- include the go-live date
- Define the schedule of transition activities
- Maintenance schedule
- Identify the ongoing maintenance requirements for the project
- defines the schedule of activities that the operations team will need to build into their work
- Training
- Identify the operational training requirements and delivery channels
- helps the operations team acquire the skills and certifications needed to maintain the system
- Identify the operational training requirements and delivery channels
- Activities
- List all the other tasks required to complete the handoff
- e.g., access setup, asset turnover, and review sessions
- Tools and techniques
- List any specific tools, techniques, or processes the operations team will need long term
- incorporate any access requirements into the activities list
- Product documentation
- transition plan should include product-specific information
- e.g., code documentation, product specifications, configurations, and access and credentials
- Asset turnover
- Create a strategy for how and when assets will move from the project team to the maintenance team
- include a strategy for how the team will distribute assets when both the project team and maintenance team need to use the system
- crucial if the project uses high-cost, low quantity physical assets