Commonwealth of Pennsylvania

Department of Environmental Protection

Bureau of Information Technology

Project Management Office

Transition Plan

For

<Project Title>

Prepared by: <Name of Person Preparing Report>

Date: <January 1, 2005>

Project Manager: <Name of Project Manager>

This page is left intentionally blank.

Document Control

Author

Document Name:	Transition Plan
Version Number:
Version Date:
Project Manager:
Date Issued:

Approvals

The Commonwealth of Pennsylvania, Department of Environmental Protection (DEP) approves the Transition Plan within this document. Approval of this document signifies that this Transition Plan is a complete, quality implementation of the deliverable requirements as specified for the authorized work.

Roles	Name	Signature	Date
Quality Manager
Project Management Officer
Project Sponsor
Chief Information Officer

Change History

Version	Date	Revision Descriptions
V.01
V.02
V.03

TABLE OF CONTENTS

Document Control	i

1.	Introduction	1

2.	Purpose	1

3.	Software Support Resources	1

3.1	Facilities	1

3.2	Hardware	1

3.3	Software	1

3.4	Documentation	1

3.5	Personnel	2

3.6	Training	2

4.	Operational Scenarios	2

5.	Transition Planning	2

5.1	Release Process	2

5.2	Data Migration	2

5.3	Problem Resolution	3

5.4	Transition Schedule	3

Appendix A - Glossary of Abbreviations, Acronyms and Terms	4

1.	Introduction

In this section, write what is relevant as an introduction, including necessary background to explain the current to proposed changes.

<relevant introduction>

2.	Purpose

Describe the purpose of this document.

<purpose>

3.	Software Support Resources

3.1	Facilities

Describe the facilities needed to support the deliverable software. This description may include safety and security requirements, special power needs, cabling, room construction, etc.

<describe needed facilities>

3.2	Hardware

Describe the hardware and associated documentation needed to support the deliverable software. Include a description of any network or data communication requirements.

<describe the hardware and documentation>

3.3	Software

Describe any software and associated documentation needed to support the deliverable software. This may include database platforms, compilers, operating systems, utilities, etc.

<describe software>

3.4	Documentation

List any additional documentation needed to support the deliverable software.

<list any additional documentation>

3.5	Personnel

Describe the personnel needed to accomplish the transition, maintenance, and support of the deliverable software, including the anticipated number of personnel, the types and levels of skills and expertise, and any necessary security clearances. Define the project team’s role during the transition period.

<describe the personnel needed>

3.6	Training

Estimate the training requirements for users, operational staff, and support staff.

<estimate>

4.	Operational Scenarios

Develop and describe detailed operational scenarios to be performed by the operational support staff, maintenance staff, and users. Explain how each scenario will impact transition planning, and describe any specific transition procedures that result from these scenarios.

<develop and describe detailed operational scenarios>

5.	Transition Planning

5.1	Release Process

Document the release process for the deliverable software. Refer to any Configuration Management standards that define an acceptable release, and indicate how Configuration Management will be applied to the operational software product.

<document the release process>

5.2	Data Migration

Describe any data that must be migrated into the deliverable software product. List any special issues with regard to data reconstruction or the migration of historical data.

<describe data>

5.3	Problem Resolution

Specify the procedure for identifying, tracking, and resolving problems with the operational software product.

<specify procedure>

5.4	Transition Schedule

Develop a detailed schedule for transition. Include a breakdown of roles and responsibilities. Address transition through the development, operation, maintenance, and support phases of the software product. Note critical time dependencies on the software support products listed in this document.

<detailed schedule>

Appendix A - Glossary of Abbreviations, Acronyms and Terms

Term	Definition
BIT	Bureau of Information Technology
CIO	A Chief Information Officer is the department’s most senior IT manager, responsible and accountable for the Department’s performance in that area.
Deliverable	A deliverable is a physical item to be delivered for a project. It may include organization attributes, reports and plans, as well as physical products or objects. It can apply to the project itself, such as a risk management plan, or to a system, such as software code.
DEP	Department of Environmental Protection
Project Champion (PC)	The Project Champion is the person who is responsible for acting as the project’s owner/delegate. This person approves the project’s deliverables and coordinates integration of the project’s outcomes into the sponsoring organization.
Project Management Body of Knowledge (PMBoK)	PMBoK is the Project Management Institute’s body of knowledge that includes knowledge of proven, traditional practices, which are widely applied, as well as knowledge of innovative and advanced practices, which may have seen more limited use.
Project Management Methodology (PMM)	The system of practices, techniques, procedures, and rules used by those within the profession of Project Management.
Project Management Office (PMO)	The Project Management Office is an organized body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain. The responsibilities of a PMO can range from providing project management support functions to actually being responsible for then direct management of a project.
Project Manager (PM)	Project Manager. The person assigned by the performing organization to achieve the project objectives.
Project Sponsor (PS)	The person or group that provides the financial resources, in cash or in kind, for the project.
Project Stakeholder	Persons and organizations such as customers, sponsors, performing organization and the public, that are actively involved in the project, or whose interests may be positively or negatively affected by execution of completion of the project. They may also exert influence over the project and its deliverables.
Subject Matter Expert (SME)	An Subject Matter Expert (SME) s a person who is viewed as an expert in a particular field. This person can be a software expert who knows how a software application works or a business expert who understands business forces and requirements. An SME designation is not particular to a discipline; an SME is someone to whom a project manager can go to for accurate information.

References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) Third Edition

Governor’s Office of Administration

http://www.oit.state.pa.us/oaoit/cwp/view.asp?a=671&q=194302

Commonwealth of Pennsylvania	4.E_TP_Final

Department of Environmental Protection

Transition Plan

<Enter Project Name Here>

5	7/28/2006

<Location of Project "file path">

Commonwealth of Pennsylvania

mahockenbe

2005-09-29

mmcdaniel