You are on page 1of 5

<Organization name goes here>

<Project name goes here> Release Plan


Version x.x

Date
Contributors

Document history
Version Date Author Description

Purpose
The purpose of the Release Plan is to ensure that transition to production from the Pilot phase occurs smoothly and that the XYZ project is able to deliver the levels of quality of service that have been established by the project team.

Table of Contents

Abbreviations
Abbreviation Meaning

Introduction
<describe here briefly the nature of the project and the business goals for the solution>

Proof-of-concept laboratory testing results Capacity planning results Pilot phase results
Metrics Operations cost projections Staffing requirements Other lessons learned

Transition plan
Delivery model
<describe the overall solution delivery briefly. Reference other project documents as needed>

Operations and Maintenance team model


<describe here the team or organizational model for supporting and maintaining the solution>

Roles and responsibilities


<list team members and responsibilities>

Transition procedures
Transfer of responsibilities between teams Development team role Who Responsibility Operations team role Who

Detailed procedure 1 Detailed procedure 2 Deliverables


Artifact Description Physical location Development team owner

Final acceptance procedures

Operations readiness
Backup and disaster recovery Incremental capacity Retirement of old technology Rollback Monitoring Quality of Service Training End-User support

Maintenance strategy
Bug fixes Upgrades to infrastructure components Quality of service Financial tracking
<charge backs vs user subscription vs. sunk operations cost>

Planning
New feature requests Strategic planning Budget

Risk assessment

Mitigation plans

You might also like