Releasing a new software program
Allen Allbrook, the release coordinator, has created a request to release a new version of the payroll service and Mary Mann is the change coordinator.
This release is composed of two work items to be rolled out during the Deployment milestone:
- Install a new server.
Allen creates a change request to include in the release manifest.
- Train the users on the new payroll service.
Since this work item is not a change request that needs to be completed by the Change Management team, Allen instead creates an Activity as part of the manifest.
Depending on how your application administrator has configured phases and exit criteria, the activity and change must be completed in the Deployment milestone before the release request can be closed.
The following table describes the typical steps involved in this user scenario.
Releasing a new software program
From the Release Management console, the release coordinator creates a release request.
Allen creates a new request to add a new Payroll Service and would like it by September 1, 2009. Release starts at the Initiate milestone. The service will be released in multiple phases.
Allen creates a change request to install the payroll service on a new server as part of the release manifest.
Allen creates an activity to train employees on the new payroll service as part of the release manifest. He assigns the activity to Francie Stafford.
Allen schedules the change request. He then runs the Collision Detection tool to see if there are any conflicting change requests.
On the Approval Central console, the release approver approves the request to initiate the release.
If approvers are mapped to any approval phases, the release approver must approve the release to move it forward. Otherwise, the release coordinator moves the release request to the next status.
The release coordinator moves the release to the Planning milestone.
The release coordinator reviews the calendar:
Allen opens the change calendar to see if there are any conflicting releases, change requests, or business events.
On the Release Management console, the activity assignee views assigned activity.
Activity is routed to the Francie Stafford, the activity assignee.
On the Activity form, the activity assignee attaches the training plan to work information.
Francie schedules a training session on how to use the new payroll application.
On the Activity form, the activity assignee creates tasks and assigns them to task implementers.
Francie creates tasks to assign the trainers to train Calbro users in Boston, Tokyo, and so on.
On the Activity form, the activity assignee verifies assignments, adds financial information, and schedules the start and end dates.
Francie adds financial and scheduling information to the activity.
Allen oversees assembly of CIs needed to create the new payroll service.
The release coordinator moves the release request to the Test milestone.
Allen oversees the testing of the new service, to make sure that the CIs, IT service, or process meets the specifications and requirements.
The release coordinator moves the release request to the Deployment milestone.
Phased deployment of the new service can start.
In the Deployment milestone, Mary Mann, the change coordinator, moves the change request through its stages.
The task implementer closes each task when it is completed:
In the Deployment milestone, the task moves to Assigned status and Ian Plyment, the task implementer, can start installing the server.
Ian completes the task.
Mary completes the change request to install the server.
The activity assignee performs activities:
In the Deployment milestone, the trainers can start training users at different Calbro locations.
A training task has its own independent lifecycle and continues on its own path, but all tasks must be finished in order for the activity to be completed.
The release coordinator completes the release:
On the Release form, the release coordinator moves the release request to the Close Down milestone.
Allen completes and closes the release request.