Release change review

Step by step

1. Prepare the change Release Manager

   Release Manager records the affected service, risk, planned start and end, and rollback plan. The summary should tell the reviewer what will change. A window is useful only when the delivery team can read it as an actual operating plan.

   • Identifies service, risk, window and rollback plan
   • Updates Changes, Services

2. Raise for review Release Manager

   The change enters Review. The CAB reviewer can open Changes In Review and read the same change that delivery will later use. A pending CAB review record identifies the person and meeting date for the decision.

   • Places the change before a reviewer
   • Updates Changes, CAB reviews

3. Record the CAB decision CAB Reviewer

   CAB Reviewer chooses Approve, Reject or Defer and records a reason. Approval is a decision about the planned change. Rejection ends the current route to implementation; deferral asks for more preparation.

   • Records the human decision and reason
   • Updates CAB reviews, Changes
   ApprovalA person approves before the work moves on.

4. Move approved work forward Release Manager

   Release Manager reflects the accepted review in the change state. An approved change remains tied to its original service, window and rollback plan when the engineer begins implementation.

   • Makes approved work visible for delivery
   • Updates Changes

5. Start implementation DevOps Engineer

   DevOps Engineer uses the approved change to begin work. The deployment workflow records a pending deployment, which becomes the working delivery evidence for the environment and version.

   • Creates pending deployment evidence
   • Updates Changes, Deployments

Release Manager

, CAB Reviewer, DevOps Engineer, Admin.