Skip to main content
All CollectionsData Transformation Office (DTO)Change Control Process
Change Control Guidance - Change Advisory Board (CAB)
Change Control Guidance - Change Advisory Board (CAB)

Description of the role of Change management team (CAB)

v
Written by vladimir.bonilla@mcb-bank.com
Updated over 4 months ago

CAB’s goal is to manage production changes by:

  1. Ensuring that only authorized changes are taking place in the production environment.

  2. Ensuring that these changes follow the standards agreed upon by the CAB

  3. Timely communicating and planning when these changes are taking place.

  4. Avoiding conflicts between changes.

  5. Observing business impact and change freeze periods

In order for CAB to effectively manage the production changes a schedule has been introduced.

  1. Changes that are planned to take place the following week (Monday and on) must be presented to the CAB no later than Thursday’s at 08:00 AM by means of a ticket made in the Service Desk application.

  2. CAB members which are any of the ITD, IT-SS or ISD staff are able to create a Service Desk change request on behalf of the BO.

  3. The change requests will be discussed every Friday AM in the CAB meeting.

  4. During this meeting the changes will be accepted or rejected based on the following criteria:

a.Approvals and sign-offs must be in place.

b.There must be no conflict between this new change and other changes.

c.Rollback scenario must be in place to revert back to the known/save situation if the change fails.

d.DBR steps must be in place to guarantee that this change will continue to work even if we have to move to the DBR site.

e.A test scenario must be conducted to guarantee that the change is working properly.

f.Detailed Action log or Implementation plan must be attached

5.If the criteria’s are not met, the change is rejected and needs to be corrected and resubmitted

6. If the change is accepted the change will be executed on the preset dates.

Note : CAB Submitted changes appear in service desk as NORMAL CHANGE TYPE

A Normal change is one that meets the defined lead time for testing and validation. It can have single or multiple teams involved and can vary in risk level. All Normal Changes require authorization from CAB. Lead times for normal changes provide enough advance notices to present the requested Changes to the CAB.

Approval: These changes need Information Security, Technical, Business, and CAB

Did this answer your question?