Transition Plan Template

Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template source: CVR/IT Consulting Project Transition Plan Reviewers Department Name/Title The departments and/or individuals listed above should be notified in advance and given a sufficient time period to review this document. The Project Team determines requirements for approval according to the scope of the project. Modification History Revision Date Originator Comments 1 Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Table of Contents Project Transition Plan .................................................................................................... 1 Reviewers ....................................................................................................................... 1 Modification History......................................................................................................... 1 1. Overview .................................................................................................................... 1 1.1 Project Objectives........................................................................................... 1 1.2 Customer Information ..................................................................................... 1 1.3 Transition Plan Objectives .............................................................................. 1 1.4 References ..................................................................................................... 1 1.5 Outstanding Issues......................................................................................... 2 2. System Support Resources ........................................................................................ 2 2.1 Facilities.......................................................................................................... 2 2.2 Hardware ........................................................................................................ 2 2.3 Software ......................................................................................................... 2 2.4 Documentation ............................................................................................... 2 2.5 Budget ............................................................................................................ 3 2.6 Roles and Responsibilities.............................................................................. 3 2.7 Training........................................................................................................... 3 3. Transition Planning ..................................................................................................... 3 3.1 Release Process............................................................................................. 3 3.2 Data Migration ................................................................................................ 3 3.3 Performance Measures and Reporting........................................................... 4 3.4 Governance and Management Approach....................................................... 4 3.5 Problem Resolution ........................................................................................ 4 3.6 Documentation Strategies .............................................................................. 4 3.7 Training........................................................................................................... 4 3.8 Sustainability metrics ...................................................................................... 5 3.9 Transition Schedule........................................................................................ 5 Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Page 1 of 7 Project Name: Prepared by: Date (MM/DD/YYYY): The Transition Plan is used to describe how deliverables of the project will be brought to full operational status, integrated into ongoing operations and maintained. 1. Overview 1.1 Project Objectives Project Objectives may be found in the Project Charter. In the box below, provide a list of other documents that provide additional information relevant to the Transition Plan. 1.2 Customer Information Identify the intended users and the planned operating sites that will be involved in this transition 1.3 Transition Plan Objectives Briefly describe the objectives of this plan, e.g., scheduling the transition from rollout to full operational status, identifying staffing and training needs for system operation and maintenance, planning for ongoing updates, helpdesk operations, ongoing QA oversight, etc. 1.4 References Identify any sources of information used to develop this plan. Include other project documents, such as the Requirements Specification or the Project Plan. Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Page 2 of 7 1.5 Outstanding Issues State any project planning issues or problems relevant to transition planning which are known as of this plan revision. 2. System Support Resources 2.1 Facilities Describe the facilities needed to support the deliverable system. This description may include office space, computing equipment, safety and security requirements, special power needs, cabling, room construction, etc. 2.2 Hardware Describe the hardware and associated documentation needed to support the deliverable system. Include a description of any network or data communication requirements 2.3 Software Describe any software and associated documentation needed to support the deliverable system. This may include database platforms, compilers, operating systems, configuration management, patch process, utilities, etc. 2.4 Documentation List documentation needed to support the deliverable system. . Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Page 3 of 7 2.5 Budget Provide an overview of the budget that will support maintenance and operations (e.g. dollars per year, budget source, etc.). Identify where budget information related to maintenance and operations activities may be found. 2.6 Roles and Responsibilities Identify the roles and responsibilities associated with maintenance and operations as well as the skill set needed to perform those functions. Key roles to identify include the primary business contact, maintenance & operations team lead(s), key technical staff, customer or help desk support, documentation, training and other support staff and vendors who will continue to support an installed product. Define the project team’s role during the transition period. 2.7 Training Estimate the training requirements for users, operational staff, and support staff. If there is a formal Training Plan, provide a link here. Link to Training Plan: 3. Transition Planning 3.1 Release Process Document the release process for the deliverable system. Refer to any Configuration Management standards that define an acceptable release, and indicate how Configuration Management will be applied to the operational system product. 3.2 Data Migration Describe any data that must be migrated into the deliverable system product on an on-going basis. List any special issues with regard to data reconstruction or the migration of historical data. Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Page 4 of 7 3.3 Performance Measures and Reporting Identify key performance measures for maintenance activities and for product or service performance. Include information on how measures will be captured and reported. 3.4 Governance and Management Approach Identify new or reference existing methodologies for establishing maintenance priorities and other change management strategies. 3.5 Problem Resolution Specify the procedure for identifying, tracking, and resolving problems with the operational system product. Describe how stakeholder/customers will be involved in or informed about maintenance & operations activities. Describe key stakeholders and methods for communication where known. 3.6 Documentation Strategies Describe documentation that will be routinely revised or produced such as reports; user, usage, problem and change information; product/service documentation. Include details on where documentation is stored and how it is accessed. 3.7 Training Describe ongoing training activities. Indicate who will be responsible for updating training documentation, training people on updated materials, and training new employees Put your organization logo here Project Transition Plan Template V1.0 4/4/2007 Template Source: CVR/IT Consulting Page 5 of 7 3.8 Sustainability metrics What metrics will be used to ensure solution is sustained? How often will you measure? Will you survey stakeholders 3, 6, or 9 months after go live to ensure adoption? How will you ensure adoption? 3.9 Transition Schedule Develop a detailed schedule for transition. Include a breakdown of roles and responsibilities. Address transition through the implementation, maintenance, and support phases of the system product. Note critical time dependencies on the system support products listed in this document.