Space banner

 

This documentation supports the 19.08 version of Change Management.

To view an earlier version, select the version from the Product version menu.

Releasing a new software program

Allen Allbrook, the release coordinator, has created a request to release a new version of the payroll service.

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.

Mary Mann is the change coordinator.

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

Role

Actions

Explanation

Release coordinator

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.

Release coordinator

  1. On the Release form, the release coordinator creates a new change request and assigns it to the change coordinator.
  2. The release coordinator relates the Install Server task to the change request.
  3. On the Release form, the release coordinator assigns the activity to the Deployment milestone.
  4. The release coordinator can see the change request listed on the manifest of the release.

Allen creates a change request to install the payroll service on a new server as part of the release manifest.

Release coordinator

  1. On the Release form, the release coordinator creates a new activity.
  2. The release coordinator assigns this activity to the Deployment milestone.
  3. The release coordinator can see the activity listed on the manifest of the release.

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.

Release coordinator

  1. The release coordinator runs collision detection to check whether other change requests are scheduled to work on the same CI.
  2. The release coordinator sets the scheduled, actual, and deployment start and end dates for the release. The release coordinator uses the Schedule Assist tool to search for available time segments.
  3. The release coordinator moves the request to the Initiate Approval milestone.

Allen schedules the change request. He then runs the Collision Detection tool to see if there are any conflicting change requests.

Release approver

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.

Release coordinator

The release coordinator moves the release to the Planning milestone.

Release coordinator

The release coordinator reviews the calendar:

  1. The release coordinator sets the request status to In Progress.
  2. The release coordinator views the calendar and makes sure that the release requests are shown in the calendar.
  3. On the Release form, the release coordinator adjusts the scheduled start and end dates.

Allen opens the change calendar to see if there are any conflicting releases, change requests, or business events.

Activity assignee

On the Release Management console, the activity assignee views assigned activity.

Activity is routed to the Francie Stafford, the activity assignee.

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.

Activity assignee

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.

Activity assignee

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.

Release coordinator

  1. The release coordinator oversees building the controlled environment before the release goes into production.
  2. On the Release form, the release coordinator moves the release request to the Build milestone.

Allen oversees assembly of CIs needed to create the new payroll service.

Release coordinator

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.

Release coordinator

The release coordinator moves the release request to the Deployment milestone.

Phased deployment of the new service can start.

Change coordinator

  1. The change coordinator opens the change request and moves it to the Implement stage.
  2. The change coordinator relates tasks to the change requests and assigns the tasks to the task implementer.

In the Deployment milestone, Mary Mann, the change coordinator, moves the change request through its stages.

Task implementer

The task implementer closes each task when it is completed:

  1. From the Change Management Support console, the task implementer searches for assigned tasks.
  2. After performing the task, the task implementer records information about performing the task and changes the status to Closed.

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.

Change coordinator

  1. The change coordinator completes the change request.
  2. The change coordinator opens the change request and moves it to the Completed status.

Mary completes the change request to install the server.

Activity assignee

The activity assignee performs activities:

  1. On the Release Management console, the activity assignee opens the activity and views the status of the assigned tasks.
  2. After all training tasks are finished, the activity assignee changes the status of the activity to Completed.

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.

Release coordinator

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.

Was this page helpful? Yes No Submitting... Thank you

Comments