Transition Phase

The Transition Phase begins with the completion of the project deliverables of the Execute Phase.  Both system testing and business-side User Acceptance Testing are completed in the Transition Phase.  The Training Plan is operationalized, and Business Continuity and Service Recovery Plans are finalized.  If created during the Execute Phase, final acceptance of the Run Book and User Manual occurs.  The transition of the production-ready system to a production environment takes place once training has been completed to an agreeable level and official acceptance and sign-off is received from the project sponsor or designated representative.  A link to Project Management Life Cycle templates/tools/examples referenced on this page is available here and at the bottom of this page.

TRANSITION Phase Activities

Hard Freeze Code Development; Execute System Test Plan; Receive Sign-Off The developed system must undergo rigorous testing in preparation for the User Acceptance Testing.  All modules, separately and together, are tested.  All data integrations are also tested to ensure that the system interacts with other systems as expected.
Execute User Acceptance Testing (UAT); Receive Sign-Off Typically the business assembles a team of Subject Matter Experts for this activity, as it is a conflict of interest to have the technical team create test scripts for the customer to utilize.  Sign-Off is crucial to ensure success and scope maintenance going forward.
Execute Training Plan; Accept User Guide The Training Plan and training materials created during the Execute Phase are updated as necessary based upon the UAT findings.  The training delivery strategy (individual, train-the-trainer) is typically determined by the size of the user-base.  Training is most often delivered by the business.
Finalize Business Continuity and service Recovery Plans

Finalize the Business Continuity Plan that prescribes how to conduct business and serve clients following a disruptive event, before restoration of services occurs.  Finalize the Service Recovery (aka Disaster Recovery) Plan detailing a plan of action in the event operations are disrupted by events such as severe weather, fire, earthquake, malicious activity, or electric utility disruption.  Plans should include provisions to update and improve these plans at least annually, or each time services or infrastructure undergoes major changes.   Related activities may include IT security classification, risk assessment, and compliance evaluation.

Accept 'As Built' Run Book and on-Going Operations Manual (as applicable)

A run book is a compilation of the procedures and operations of the system which is used as a reference by system administrators.  An effective run book contains all the information needed to perform day-to-day operations and to respond to emergency situations; the run book typically includes procedures for anticipated scenarios and step-by-step decision trees.

Transition Production-Ready System to Production Environment Follow the Implementation Plan.
Monitor Key Performance Indicators (KPIs) KPIs are high-level snapshots of an organization or a business process using specific predefined measures to target performance levels.  Initial as well as on-going monitoring once the project is closed helps a business understand what is working well and where improvement is needed.
Conduct Phase Gate Review

For governance and practical purposes, the PGR is designed to assure the project is ready to begin the Close Phase and to make sure it still meets the needs that were true at the Proposal/Request period.  The documents created during the Transition Phase are reviewed to verify the project is ready and complete before it reaches the Close phase.

Accept Completed Project Deliverables

Ensure that the project is approved and accepted by relevant stakeholders, including if applicable to the IT Security Team.

TRANSITION Phase Deliverables

Test Reports
End User Training; Finalized User Guide
Business Continuity Plan, Service Recovers (Disaster Recovery) Plan (if needed)
Run Book, On-Going Operations Manual
System Transitions to Production Environment

Additional Resources

Examples of Service Recovery Plans are not available because they contain security information.  If you need assistance completing a Service Recovery Plan or a Run Book, please contact the Project Management Office and appropriate staff will be identified to assist you.

Business Continuity Plan

This is a link to a UNH IT Security website that defines a Business Continuity Plan (BCP), describes when a BCP should be created and links to FEMA's BCP template.  A BCP is required for all Tiers 3-5 projects.  A BCP should be created for all Tiers 1-2 projects if service continuity is required.

Service Recovery Plan Template This document, previously known as a Disaster Recovery Plan, is required for all Tiers 3-5 projects; it is required for Tiers 1-2 projects if the project is implementing a service that could fail.
Phase Gate Review - TRANSITION Template This document is required for all Tiers 3-5 projects.