Please enable JavaScript to view the comments powered by Disqus. How to Run a Successful CAB For ITIL Change Management?

 

How to Run a Successful CAB For ITIL Change Management?

NovelVista

NovelVista

Last updated 04/07/2020


How to Run a Successful CAB For ITIL Change Management?

ITIL® (Information Technology Infrastructure Library®) is an industry acknowledged set of IT Service Management best practices. It promotes a realistic and scalable approach to identifying, planning, delivering and supporting IT services to the business and is comprised of five stages: Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement.

What is IT Change Management?

IT Change Management is a key procedure inside the Service Transition stage. The Change Management process utilizes normalized methodology to deal with IT Changes productively while downplaying disturbance. At the point when actualized, ITIL Change Management brings about a certifiable improvement in administration accessibility, more prominent efficiency, upgraded business view of IT, and expanded consumer loyalty.

What is the CAB?

The Change Advisory Board (CAB) is an integral part of the Change Management process. The CAB is a cross-functional group, which actively supports the Change Manager in the assessment, prioritization, scheduling, and approval of all IT Changes.

Running a CAB for Optimum Results

CAB Attendees

IITIL suggests that the CAB incorporates delegates from all zones inside the IT Service Provider, Business, Third Party Supplier, and, where proper, Customer people group. This permits the CAB to altogether check and thoroughly evaluate the effect of changes from both a specialized and business point of view. It is the duty of the IT Change Manager, who seats and encourages the CAB, to settle on sure that the fitting leaders are welcomed and that in the event that they can't join in, they send a reasonable delegate.

Frequency

ITIL advocates working the CAB all the time. Exactly how every now and again relies to a great extent upon the size and development of every association, except it for the most part differs from week by week to quarterly. Nowadays, the gathering is similarly prone to occur through a sound/video meeting as a vis-à-vis meeting.

Activities

Requests for Change (RFCs) are circled to CAB individuals for audit preceding each gathering. The spotlight will in general be on RFCs that will have a wide-scale or critical effect on the association. Those Changes that are characterized as 'generally safe' or 'schedule' are frequently barred from the plan.

The CAB typically performs some or all of the following activities:

  • A review and assessment of proposed RFCs
  • A review of failed Changes
  • A review of rolled back Changes
  • A review of implemented Changes
  • A periodic review of the Change Management process itself

This encourages CAB members to focus on lessons learned and fosters a culture of continual service improvement.

Approving RFCs

The CAB must take into account all of the following before giving technical, business, financial and third party supplier approval:

  • Risk / impact to the business (including the accuracy of the initial Change priority assessment)
  • Impact of the Change upon the wider infrastructure and other services
  • Impact of the Change upon customer service and Service Level Agreements (SLAs)
  • Impact of the Change upon capacity and performance
  • Impact of the Change upon security and compliance
  • Impact of the Change upon contingency / Disaster Recovery plans
  • The IT and business resources required to implement and support the Change
  • Risk/impact of not implementing the Change (business justification)
  • Potential conflict with other Changes or scheduled maintenance
  • Back out plan
  • Test results (including User Acceptance Testing)

If the CAB rejects a Change, the Change Manager will document the reasons for rejection and communicate this to the Change Requester.

Emergency Change Advisory Board

ITIL approach perceives that IT firms should be sufficiently lithe to satisfy the needs of present-day business. The ITIL Change Management process, in this manner, consolidates an Emergency Change method, which can be possibly summoned when a Change is required to fix a high seriousness IT Incident that is majorly affecting business tasks. As Emergency Changes require quick usage, they can be endorsed by the ECAB (Emergency Change Advisory Board): a little subset of the CAB enabled to settle on a prompt endorsement choice.

Topic Related Post

Is ITIL certification worth your time & efforts?
Is ITIL certification worth your time & efforts?
How to implement ITIL?
How to implement ITIL?
What are the Most Common Root Cause of Major Incidents?
What are the Most Common Root Cause of Major Incidents?

About Author

NovelVista Learning Solutions is a professionally managed training organization with specialization in certification courses. The core management team consists of highly qualified professionals with vast industry experience. NovelVista is an Accredited Training Organization (ATO) to conduct all levels of ITIL Courses. We also conduct training on DevOps, AWS Solution Architect associate, Prince2, MSP, CSM, Cloud Computing, Apache Hadoop, Six Sigma, ISO 20000/27000 & Agile Methodologies.

 
 

SUBMIT ENQUIRY

 
 
 
 
 
 
 
 
 

Upcoming Events

ITIL-Logo-BL
ITIL

Every Weekend

AWS-Logo-BL
AWS

Every Weekend

Dev-Ops-Logo-BL
DevOps

Every Weekend

Prince2-Logo-BL
PRINCE2

Every Weekend

Topic Related

Take Simple Quiz and Get Discount Upto 50%
     
  18002122003
 
  
 
  • Disclaimer
  • PRINCE2® is a registered trade mark of AXELOS Limited. All rights reserved.
  • ITIL® is a registered trade mark of AXELOS Limited. All rights reserved.
  • MSP® is a registered trade mark of AXELOS Limited. All rights reserved.
  • DevOps® is a registered trade mark of DevOps Institute Limited. All rights reserved.