| Task: Develop the Release Plan |
| |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
Proper development and implementation of a release plan may alleviate some of the project challenges related to
managing scope, quality, communications, and risk. A formal release plan makes distributing software more consistent
for the performing organization and outlines how and when the solution will be made available to the customers.
|
Steps
|
Gather Preliminary Project Documentation
Gather the project schedule,, Implementation Plan, Communication plan and Backout Plan. These will provide information
that will be useful in understanding the project and preparing the Release Plan. This step may require meetings with
the Project Manager and various members of the project team.
|
Prepare the Release Plan
Using the information provided, create the Release Plan.
|
Obtain Approval
Obtain final approval of the Release Plan from the Project Manager, Application Owner and Technical Owner.
|
|
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014
|
|