Last updated on
Plutora Blog - IT Governance, Release Management

CAB and Release Management: The Connection

Reading time 2 minutes

If your organisation follows the ITIL service management framework then you will have a regular Change Advisory Board (CAB) forum setup which approves Change Requests for production deployment. Without getting into the specific conduct of CAB meetings, I wanted to touch on the role of Release Management in the context of the CAB.

Release Managers or delivery managers are responsible for raising Change Request tickets in order to get a slot into the forward schedule of change.  These Change Requests are then assessed at CAB if they are deemed as a major release. in order for the CAB to make an informed decision around approving the release for deployment certain information is required.

A summary of the information includes but not limited to:

  • a description of the release to be implemented and if necessary the release scope to be included.
  • a run down on the test results from User Acceptance Testing and confirmation of the business sign-off sought.
  • confirmation of testing sign off given that CAB members normally require confidence that System Test and/or System Integration Testing is complete and con
  • the deployment plan or implementation plan.
  • availability of resources for the change window.
  • in some cases release managers ask the project or test managers to to support the change at the CAB to answer any detailed question about the release or test results.

The CAB protects the integrity of the target environment and is generally risk averse in nature. The Release Manager is responsible for satisfying the information needs of the CAB to assure the change will not adversely impact the target environment. If the Release Manager comes across as vague or dismissive it is likely that the change will be deferred to the next release.