Project Management Framework
Planning - Implementation and Transition Plan
Definition
Implementation is getting the deliverables produced during a project up and running. For a new software application, it is getting the application into production.
Transition is turning the product over to the staff responsible for maintenance and support.
The Implementation and Transition Plan document describes the steps necessary to turn the project's product or service over to the business unit and maintenance & operations support staff. The plan assures that all of the necessary steps are identified and that each of these steps has resources assigned to them. Sources of information for implementation and transition planning should include representation of all those who have assignments or who are affected by the project's outcomes.
Typically, the project team executes most of an Implementation and Transition Plan tasks after completing quality assurance testing and obtaining customer approval. However, parts of the plan may be executed during other phases of the project. For example, the plan may call for establishing a production environment, ordering equipment, acquiring of facilities, or preparing training materials. To accomplish these tasks, the project team will need to do some early preparatory work.
Why is this important?
Implementation and Transition planning is important because it pulls together the tasks necessary for placing the new product or service in the hands of the customer. With a well thought out implementation and transition plan, the project manager will be able to communicate and coordinate the tasks necessary for a successful product transition.
When planning the implementation and transition tasks, be aware of the challenges facing those that have to make a change when the new product or service is implemented. Manage these challenges well in advance of the implementation/transition date to help make the transition smoother.
Instructions
Implementation and Transition planning is started at a high level once the project requirements have been defined. Get input from people who will be involved in the implementation and transition tasks and the people who will be maintaining the product once transition is complete. The project's work breakdown structure, developed at the beginning of a project, should contain the high-level implementation and transition tasks. Add additional detail as the project progresses. The final result will be the detailed Implementation and Transition Plan.
It is a good idea to hold a walkthrough of the implementation and transition plan with all stakeholders to verify that all tasks are accounted for, are in their proper sequence, and assigned to appropriate resources. Tasks for handing off the "new" as well as closing out the "old" should be included in your implementation and transition plan. Track and monitor the implementation and transition tasks along with the rest of the project schedule.
Changes made to the Implementation and Transition Plan may also result in changes to other project planning documents. When the Implementation and Transition Plan changes, review the other project planning documents to make sure updates are made where appropriate.
Perform a dry run, or tabletop exercise, of the Implementation and Transition Plan prior to actual implementation. Conduct the dry run test as close to actual implementation as possible or feasible. Make sure the sequencing and timing of the tasks are correct.
How to Scale
The level of effort required for the implementation and transition tasks varies depending on the amount of change being introduced in the customer's business practices. The number and types of tasks included in the Implementation and Transition Plan will depend on the way the product or service is implemented: running parallel to the old product; a phased approach; a "big bang" cutover; etc.
If the product or service will run in parallel to the old product or service, the implementation plan may include tasks to verify new output against the output from the old product or service. If the implementation is a total cut over to the new product or service, the implementation plan may include tasks to train additional staff to support the customer during and immediately after the cutover. If there are training needs, include tasks for creating training materials and setting up the training environment.
Related Link:
Implementation/Transition Plan Template
Implementation/Transition Plan Execution
Checklists