| Task: Update Release Plan |
| |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
Main Description
The release plan shows when functionality is deployed to production. A release manager typically manages the plan and
takes requests to schedule functionality deployment. During the planning process, functionality conflicts, resource
constraints, issues, and risks are reviewed and documented. The release plan describes those approved functionalities
scheduled for deployment and their respective deployment dates.
In this task, the team member must request the release date based on the project's needs. If the approved dates do not
meet the needs of the business, negotiation between the release manager, business analyst, and the subject matter
expert should yield an accpetable release date.
|
Steps
|
Identify an appropriate production implementation date
With the help of business users, testers, and the IT release management team, determine the best possible release date.
This often means the date has to be negotiated since business users usually need the functionality yesterday. However,
IT bandwidth is limited and there are other changes that must be implemented in production in the same time.
|
Communicate the release date to the release manager
Organizations assign an individual, team or departments to maintain the production deployment, or release schedule.
The release date must be submitted as a request to teh Release Manager using this link:
Release Date
Request
The request may be accepted, brought into question, or rejected. In the event it is brought into question, or rejected,
the release date must be negotiated between the stakeholders, business anlayst(s), testing resources, and the release
manager.
Once the final date has been negotiated, communicate the release date to the release manager and to the project team to
ensure everyone works to the same date.
|
Update project documents
| If necessary, update the project schedule, project plan, test schedule, test plan, and the communications plan to
reflect the correct deployment date. |
|
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
|
|
