Release and Deployment Management process overview

The Release and Deployment Management process includes activities necessary to control releases to service assets and configuration items across the entire service lifecycle. It provides standard methods and procedures to use when implementing all releases.

The purpose of Release and Deployment Management is to ensure that:

  • Releases follow a set process
  • Appropriate users are notified at key points in the process
  • Progress of a release is monitored and notification are issued if deadlines are missed
  • Releases are supported throughout a simple or complex lifecycle

Release types

Release and Deployment Management includes three release types: Emergency, Major, and Minor. All three release types utilize the Release Management category and workflow in the Change Management module. Additional categories and workflows can be created if required. The steps of the workflow are represented by the phases and tasks within the phase. Service Manager requires that every release has a category and phase, but tasks are optional.

Release phases and transitions

Service Manager uses phases to describe the steps necessary to complete a release. The phase also determine the release screens users see, the approvals required to advance to the next phase, and the conditions that cause the system to issue notification and alerts. Each phase has workflow transitions that control how the release record will move through the workflow. When the work for a given phase has been completed the user will advance it to the next phase. If the release has encountered a failure condition then the release may be move back to an earlier phase for rework or abandoned.

Release tasks

Release Management utilizes tasks to capture work that is necessary for the overall release. This is work in addition to the Change specific tasks that are required to complete the changes that are associated to the release. Examples of required release activities are: determining if funding is available to support the release, arranging for required contracts and licenses, building and delivering training, evaluating the financial impact of the planned release, and performing knowledge transfer after the release has been deployed. Release Models can be used to pre-define task plans for Releases.

Integration with Change Management

In Service Manager the Release record and workflow control the overall process of the release, including approvals for the release and the release specific activities (tasks) that need to be complete. The release is related to multiple change requests (RFCs) that have their own workflow, approvals, and tasks. The planning, assessment, build, and deployment of each change is tracked and worked in the Change Management module. The Release provides the higher level oversight and provides visibility into the Change Management process through the Related Records section in the release record.

Release roles

The following table describes the responsibilities of the Release and Deployment Management user roles.

Release and Deployment Management user roles

Role

Responsibilities

Release Manager

  • Manages all aspects of the end-to-end release process
  • Reviews and updates the release policy
  • Facilitate the bundling of releases
  • Coordinate planning and preparation for Deployment
  • Coordinate creation of Deployment Plans
  • Ensures coordination between the build and test environment team and release teams
  • Ensures the teams follow the organization’s established policies and procedures
  • Provides management reports on release progress
  • Updates the Service Knowledge Management System

Release Coordinator

  • Registers the release and applies the correct release model and release detail.
  • Schedules the release according to the plan created previously.
  • Creates the release tasks required for the release.
  • Coordinates the Risk and Impact Analysis phase of the release and creates release plan based on the assessment information.
  • Verifies if the release has passed the test criteria.
  • Verifies if the release is implemented successfully in the production environment.
  • After implementation, evaluates the change and closes the request.
  • If a change implementation fails, the coordinator activates a back-out plan to return the system to its original state.

Release Approver

  • Uses the Service Manager tool to Change Advisory Board to approve or deny Releases when requested