You are on page 1of 7

TRANSITION PLAN TEMPLATE

In this template, instructions are included in italics. When you have completed the template and no longer need the instructions, delete them. Provide a brief overview of the transition goals, any assumptions that the plan is based on, and any risks that have been identified that could severely limit your ability to complete the transition on schedule. Goals: Assumptions: Risks: Other:

Transition Team
List the members of the transition team, providing the name of the person who fulfills each roll. Transition Role Transition Team Leader Project Leader Transition Specialist Project Team Database Administrator Systems and Networking Production Support Desktop Support Help Desk OPS Platform Support Project Development Who [Name of Technical Project Manager] [Name of Business Project Manager]

The following table suggests tasks. Technical Project Manager. and a general timeframe for when the task is due. and the general time with a specific due date. You should replace the role names with actual names.Transition Process Tasks List the tasks that must be accomplished during the transition process. Production Support Manager When Is It Due? Initiation Initiation Initiation Review development project schedule Initiation Review deliverables list to determine requirements Initiation Develop matrix of required resources/skills Conduct skill gap analysis against all IS staff Initiation Initiation . Business Project Manager Transition Specialist. Business Project Manager Technical Project Manager Training Coordinator. Some tasks will be repeated for each deliverable—be sure to include each task for each deliverable. You will probably also have additional tasks to add to the list. Technical Project Manager. Business Project Manager Transition Specialist. This list of tasks can then be given to the project manager to be included in the MS Project plan for the development project. Technical Project Manager. and change the text formatting back to regular text (select the text and press Ctrl+Spacebar to remove character formatting). roles for who is responsible for each task. The transition tasks include: Task Coordinate transition planning meeting Distribute project Initiation Plan or Project Plan Attend transition planning meeting Who's Responsible? Technical Project Manager Project Manager (business or technical) Transition Specialist.

Production Support Manager Transition Specialist. Business Project Manager Transition Specialist Transition Specialist. Business Project Manager. Technical Project Manager. Technical Project Manager.Task Identify project activities to be completed before transition can start Who's Responsible? Transition Specialist. Technical Project Manager. Technical Project Manager. Business Project Manager Transition Specialist. Business Project Manager Transition Specialist. Technical Project Manager. Business Project Manager Production Support Manager Training Coordinator. resolve variances. Technical Project Manager. and Production Support Manager Technical Project Manager When Is It Due? Initiation Determine timeline Initiation Establish transition milestones Initiation Assign support staff to the application Determine actual training needed. based on gap analysis Ramp-up Ramp-up Determine roles and responsibilities (such as collect. etc.) Assign evaluator for each transition deliverable Establish support expectations for IS Ramp-up Ramp-up Ramp-up Obtain access/privileges Ramp-up . accept deliverables. review.

Task Acquire software license agreements for production support Who's Responsible? Technical Project Manager and Configuration Manager Training Coordinator. application knowledge. List the skills. in terms of business knowledge. and software knowledge. making sure not to forget the system software knowledge required. . Production Support Manager When Is It Due? Ramp-up Develop training plans Identify necessary training courses Schedule classes Identify necessary knowledge transfer activities Determine measurable tasks to validate that knowledge transfer is acceptable Notify business area(s) of production support procedures Notify C&C units of transition to production status Main Transition Production Support Manager Production Support Manager or Technical Project Manager Production Support Manager Technical Project Manager and Configuration Manager Production Support Manager and Business or Technical Project Manager Go Live Gateway Go Live Gateway Establish new on-call lists Move development documentation and code to production repository Shakedown Steady-State Gateway Transfer user group/steering committee leadership to production support Steady-State Gateway Training Required Skill Levels Estimate the necessary level of skill to support the application. Technical Project Manager.

and include a schedule of when those courses are offered. Transition Resources Estimate the resources needed for the transition. List any courses that will be required. for example: 2 people at 25-75% (1 FTE). and an FTE count. and some knowledge of the skill levels of the production support staff. Resources Production Support Resources Estimate the resources required to support the application in steady-state production and during the shakedown period. moderate. and for knowledge transfer activities. or explain what is necessary Availability Required Indicate where the skill must be available: On the team. or in user area Degree of Applicability Rate the applicability of the skill to the system. in IS. Communication Plan . List recommended knowledge transfer activities. using a scale of 1-5. Provide the estimate as both a head count. including a schedule for completing any necessary course work. expert. with 1=light and 5=heavy Training Needs Based on the estimated skill levels. estimate the training needs. in C&C. Training Plan Provide a training plan.Skill Description of skill Level of Expertise Trainee.

Determine how reports are to be made (at project status meetings. and any other C&C units involved in the transition of this application. at project review meetings. for transition reviews. The following methods will be used to keep stakeholders and outside parties informed and involved in the transition process: Stakeholder Transition Team Method of Communication Face-to-face informal meetings Transition Team Meetings Project Team Project Sponsor C&C Director Project Steering Committee Project Manager Team End Users and other stakeholders Outside Groups. Timelines and Milestones . The communication methods and frequencies included in this table are recommended. etc. Use the project stakeholder table to determine who has a stake in the transition progress. or modify these if necessary. but you may add additional communication techniques.). the production support manager. through email.Establish a schedule for transition team meetings. You should add the actual names for your project's stakeholders in each category. when issues require it Semi-monthly On demand Monthly When application reaches steady-state production As needed This table shows the categories of stakeholders. but weekly during transition Weekly Monthly Monthly Monthly On demand. and for reports to the development project team. such as vendors Project Status Meetings Project Status Report Project Status Report Project Status Report Project Status Meeting Committee Meetings Global Issues Log Project Status Report Transition Status Notification by email Business letters Frequency of Communication Daily Monthly before ramp-up.

In addition. .Estimate the length of the transition period. include the dates for any expected outside training classes for support staff that will be required. going live. Also estimate the length of the expected shakedown period. and the extent of overlap with development. and entering steady-state production should be included. Estimated dates for the milestones of Rampup. Assign a production delivery date.