Department of Veterans Affairs

<Project Name>

Transition Plan

<Month><Year>

Version <#.#>
This template contains a paragraph style called Instructional Text in italic and bold italic. Text
using this paragraph style is designed to assist the reader in completing the document. Text in
paragraphs added after this help text is automatically set to the appropriate body text level. For
best results and to maintain formatting consistency, use the provided paragraph styles. Delete all
instructional text before publishing or distributing the document.
This template conforms to the latest Section 508 guidelines. The user of the template is responsible to
maintain Section 508 conformance for any artifact created from this template.

Revision History
Date

Version

Description

Author

Place latest revisions at top of table.

The Revision History pertains only to the content of the actual document and any updates made
after distribution. It does not apply to changes in the formatting of the template for the
document.
Remove blank rows.

<Project Name>
Transition Plan

<Month> <Year>

Instructions
This document is required to plan the transition of application software sustainment
responsibility from the project delivery team to the application product support team. For
projects that are enhancing a product that is currently supported by Product Support, a
transition plan is most likely not required. The need and timing for transition plan should be
identified at Milestone 1.
This template contains a style named Instructional Text. Text using this style is only to provide
guidance in completing the document the final document should not contain Instructional Text.
Text in paragraphs added after Instructional Text is automatically set to the appropriate body
text style. For best results and to maintain formatting consistency:

Use the provided paragraph styles

Delete all Instructional Text before finalizing the document, including these instructions.

The following project types are required to complete this artifact. Exceptions are outlined where
needed throughout the document.
Activity

New Capability

Feature Enhancement

Field Deployment

1a

1b

Cloud/Web
Deployment

2a

2b

Mobile Application

3a

3b

<Project Name>
Transition Plan

<Month> <Year>

Table of Contents
1.

Product / Project Description...............................................................................................1

2.

Product / Project Documentation.........................................................................................1

3.

Product / Project Stakeholders............................................................................................1

4.

Transition Data....................................................................................................................2

5.

Development, Testing and Performance Monitoring Tools...................................................3

6.

Other Technology, Supplies and Material Requirements.....................................................4

7.

Human Resource Requirements, Planning and Organizational Charts...............................4

8.

Transfer of Contracting Officers Representative (COR) Responsibilities and Contract Data

6

9.

Help Desk Contract Requirements and Support.................................................................6

10.

Knowledge Transfer............................................................................................................ 7

11.

Assumptions, Constraints and Risks...................................................................................7

12.

Financial / Budget Estimates...............................................................................................8

13.

Transition Plan Signatures................................................................................................10

<Project Name>
Transition Plan

<Month> <Year>

Office of Information and Technology

Product Support
<Product / Project Name>
Transition Plan
< Initial / Interim / Final> Review Number <n>
<Date>

1. Product / Project Description

<Type text here>
<PMAS Project Number>
<current PMAS state>
Very simply, for a general audience, 2-4 sentences to describe the product.
First review only unless scope significantly changes during development. Include a statement
about PMAS PMAS project number, PMAS state, and outstanding Red Flag issues, etc. If
not in PMAS, specify reason.
For Product Development Projects list the EPS Code(s) for the project. For any non-PD
projects provide a unique identifier for the project.

2. Product / Project Documentation

<Type URL here>
Enter the URL for the Product/Program/Project Document & Artifact Repository. This should
be an officially authorized project repository, not an individual team site which may have
restricted permissions. This is usually the site used by the integrated project team (IPT) to
share documents related to the product. It should have shared permissions for Product
Development, Product Support and Information Security staff working on the IPT. The URL
is a mandatory part of this Transition Plan and is designed to assure that all relevant artifacts
in this plan are available. At a minimum, this Library should contain signed copies of the
Business Requirements Document (BRD) and any Business Process Documents that have
been created.

3. Product / Project Stakeholders

List below all project stakeholder organizations and key associated individuals including
project sponsors, customers, developers, and vendors.
Specify internal vs. external stakeholders. Identify each stakeholders role and interest in the
project. (You can use other program or project documentation if available (i.e., text from
PMAS milestone reviews).
<Project Name>
Transition Plan

<Month> <Year>

Internal stakeholders: Examples: OIT, business owners, and Regional Offices.

Stakeholders / Entity:

Role/ Interest:

External stakeholders: Examples: Congress, OMB, & Federal, state, and local agencies.
Stakeholders / Entity:

Role/ Interest:

4. Transition Data
This transition plan is for a <Indicate if this transition plan is for a phased, national
rollout to several locations listed in the following table, or if it is for one, large implementation
at many sites.

List the current and planned application operating sites in the table below
Current Operating Sites

Planned Operating Sites

Transition of the application to PS is scheduled as follows:

<Type text here>

Indicate exactly when the application, or which portions of the application, is/are scheduled for
transition to PS
If there are proprietary products that are already included under licenses, please describe here.
Note: This data is important to know when dealing with Freedom of Information Act (FOIA) requests
and identifies what is and what is not permitted to be provided to the requestor.
Specify any software which is not Section 508 compliant:

<Type text here>

Has the software application been certified as Section 508 compliant? How was Section 508
compliance determined? Where are test results stored? Specify any software which is not 508
compliant.
<Project Name>
Transition Plan

<Month> <Year>

Specify any software that is not Windows 7 compatible:

<Type text here>

Has the software application been certified as Windows 7 compatible? How was the Windows 7
compatible determined? Where are test results stored? Specify any software which is not Windows 7
compatible.

Please identify any backlog of defects or priority enhancements that exist at the time of the transition,
and what tools you are using to store/conduct change management (CM) on these items.

<Type text here>

Provide a transition Gantt chart with sufficient resolution to depict all transition milestones and reviews.
Milestone Title and
Description

Milestone Completion Criteria

Target Completion
Date Day/Month/Year

5. Development, Testing and Performance Monitoring

Tools
Please list all development tools, code generators, testing tools, and performance monitoring tools.

Explain how these tools will transition to PS.

Specify any development, testing, and performance monitoring tools that are not Section 508
compliant:
Identify any development, testing, and performance monitoring tools that are not Windows 7
compliant:
Tool

Used For

Type

License #

License
Administered
By

In
TRM?

6. Other Technology, Supplies and Material

Requirements
Use the table below to identify the other consumables (e.g., technology, supplies, envelopes,
preprinted forms, and materials) required to support the application/product.
<Project Name>
Transition Plan

<Month> <Year>

Enter the item name, the SKU or ID number, the version number, the release number.
Enter Yes or No to identify whether or not the item is currently owned, needs to be
acquired, is furnished by the vendor, or will be delivered.
Use the last column to identify the budget that is paying for the item.

Item Name

SKU
/
ID #

Ver.
#

Rel
.#

Currentl
y Owned

To Be
Acquire
d

Vendor
Furnishe
d

To Be
Delivere
d

Allocatin
g Budget

7. Human Resource Requirements, Planning and

Organizational Charts
Provide an organization chart of the current application development project. Display the
staffing by full-time employee (FTE)/contractor including any vacancies. Provide the total
number of Government staff.
<Insert chart here>

Identify the current resources supporting the project by resource type, skill set, and associated
organization in the table below.
Of the total resources, <enter #> have overall knowledge of both the application and how all the
components fit together.
Current Resources
Resource Type

Skill Sets Required

Description

Organizatio
n

A Chapter 33 example is provided: below. Please delete from your document.

<Project Name>
Transition Plan

<Month> <Year>

Resource Type

Skill Sets Required

Description

Organizatio
n

Team Developers (9)

JRules, Java J2EE,

LSPS, Jasper Reports,
JavaScript

Create code and conduct

unit/integration testing of
application development
solutions.

PD

Types of Developers
Needed:
JRules (2)
LSPS Whitestein (2)
Java, Jasper Reports
(4)
UI- JQuery, Java
Script (1)

Tortoise SVN,
Subversion, Jrockit,
Eclipse, Oracle Express
and Developer,
WinMerge, WebLogic,
CCTray, Apache HTTP,
ILOG Jrules with rules
studio, SoapUI,
Maven/Nexus, and
Living Systems
Process Design Suite,
SharePoint
SFTP client or
knowledge of SSH via
Terminal

Participate in all JAD/RAD

planning sessions
including backlog
grooming and sizing,
demonstrations, and team
productivity
improvements.
Developers should
possess one or more of
the needed technical
competencies used by
application development
on CH33 LTS.

Use the following table to identify a human resource sustainment strategy including the
resource types and skill sets required (for example: 1 PM, 4 developers, etc.). Identify any
other anticipated, significant, PS resource requirements based on defect and backlog
resolution, upcoming legislative mandates, and Plans of Action and Milestones (POAMs).
Include the total number of FTEs that PS requires for both the Program and IT. This should
include both filled and vacant positions and is meant to represent the projected overall staffing
needs.
Identify any FTE that would transfer over permanent/temporarily from the development effort
for the transition (if any).
Identify any new hires or new positions in PS that will be needed for sustainment of the
application.
Identify new roles/assignments for current Major Initiative (MI)/non-MI development project team
members who may transfer to sustainment:
To Be Support Resource / Skill Set Identification
Resource
Type

Skill Sets

Description

Organizatio
n

#
FTE

#
Contractor

<Project Name>
Transition Plan

<Month> <Year>

Total:

8. Transfer of Contracting Officers Representative

(COR) Responsibilities and Contract Data
If applicable, use the following table to identify current and future CORs. COR
responsibilities include: ensuring that the terms of contracts are fulfilled, managing invoice
payments, reviewing reports, issuing COR designation letters, etc. Enter the CORs name and
responsibility in the first column. In the remaining columns, enter Yes or No in each of
the subsequent columns to indicate the applicability of the COR responsibility to the PS as
appropriate.
Describe any COR transition planning meetings that are required, and specify when COR
duties will transfer, if applicable.
To PS
Current COR Name /
Responsibility

Transfer

Responsibility

To PS
Sustainment COR Name /
Responsibility

Transfer

Responsibility

Sustainment/Maintenance Contract and/or Service Level Agreements (SLA):

Contract
Number

Contractor/
Vendor

Period of
Performanc
e

Annual
Cost
$ amount

Options
Specify #
of options
and cost

COR
Name

Comments
and/or
Description
of Contract

<Project Name>
Transition Plan

<Month> <Year>

9. Help Desk Contract Requirements and Support

Describe the current help desk support activities for each tier of support including Tier 2 and
Tier 3. Support activities include providing technical assistance, consulting with the user, and
recording user support requests. Provide telephone numbers.
Identify the type of help desk software that is currently used, (e.g., Remedy, Unicenter.)
Describe the current, problem ticket resolution process.
Identify the type of help desk software that will be used, (e.g., Remedy, Unicenter.)
If a transition from one type of help desk software to another type is needed, explain how this
transition will occur, and identify the number of help desk staff that will need to be
transitioned.
If Help Desk activities are conducted under a separate contract, and there are plans for a
contract re-compete, provide details here. It is important to explain why this contract should
not be absorbed by one of the current Service Desk support or maintenance contracts.
Contract
Number

Contractor/
Vendor

Period of
Performanc
e

Annual
Cost
$ amount

Options
Specify #
of options
and cost

COR
Name

Comments
and/or
Description
of Contract

10. Knowledge Transfer

In this section, outline the plan that identifies the content, topics, and schedule for knowledge
transfer from the development team to PS for all application functions; hardware; operations;
technology components; development, monitoring, and performance tools; development tool
reports; user communities; required skill sets; and the number of support resources needed.
Include at least one executive-level overview and an application demo, if possible.
Discuss how knowledge will be transferred from the development team to PS. Will you use
documentation / instruction manuals, formal training classes, one-on-one training, etc.?
<Type text here>

11. Assumptions, Constraints and Risks

Assumptions:
Assumptions Which Impact the applications completion:

Business Impact:

<Project Name>
Transition Plan

<Month> <Year>

Assumptions which impact the applications transition to

sustainment:

Business Impact:

Constraints:
Constraints which impact the applications completion:

Constraints which impact the applications transition to

sustainment:

Business Impact:

Business Impact

Risks:
Development Transition
Risk:

Sustainment Risk:

Mitigation
Strategy:

Mitigation
Strategy:

Significance
:

Significance
:

Impact on
Transition:

Impact on
Sustainment:

<Project Name>
Transition Plan

<Month> <Year>

12. Financial / Budget Estimates

<Insert QUAD chart here>
Please include the Life Cycle Funding Requirement (LCFR), QUAD chart for Sustainment
and Five Year Mandatory Sustainment and the current year Budget Tracking Tool (BTT)
spend plan.

<Project Name>
Transition Plan

<Month> <Year>

13. Transition Plan Signatures

Once the text of the Transition Plan is finalized and approved, signature pages will be added and
the document will be circulated to all appropriate parties for their signature.
Signed: _______________________________________________________________________
Project Team Project Manager

Date

Signed: _______________________________________________________________________
Business Owner Representative

Date

Signed: _______________________________________________________________________
PD PM/DM ADCIO

Date

Signed: _______________________________________________________________________
PD PS ADCIO

Date

Signed: _______________________________________________________________________
Other approver as needed

Date

<Project Name>
Transition Plan

<Month> <Year>

Template Revision History

Date

Versio
n

Description

Author

November 2014

1.2

Updated to current Section 508

conformance guidelines and remediated
with Common Look Office tool

Process
Management

April 2013

1.1

Updated to latest ProPath

documentation standards and edited for
Section 508 conformance

Process
Management

December 2012

1.0

Initial Version

Product Development

Place latest revisions at top of table.

The Template Revision History pertains only to the format of the template. It does not apply to the content
of the document or any changes or updates to the content of the document after distribution.
The Template Revision History can be removed at the discretion of the author of the document.
Remove blank rows.

<Project Name>
Transition Plan

<Month> <Year>