Very good especially when I have a challenge from the business about CAB and the need to have a CAB meeting - this was very valuable thanks
@lovetoallfromaarav1796 Жыл бұрын
What questions and things discuss on CAB call?
@shaunmckinley1208Ай бұрын
Being that the video is 8 years old I'm not sure if I will get a reply. First off, great video! This content is helping a lot as I am getting ready to introduce CAB meetings into our Change Management process. We do already do TAB meetings and I intend to keep them separate. In the video you mention having both conversations (CAB & TAB) in the same meeting. Is that advisable with a large Enterprise, or am I going about this the right way with separating the two and holding them weekly?
@dibyakantmishra24814 жыл бұрын
This is awesome. I have been a Change Manager temporarily in place of our usual Change Manager. So can you let me know how much technical observation is required to be a successful Change Manager. Love to see a video, kinda this lucid and descriptive.
@NutritionalZero6 жыл бұрын
Guys I just got the error message "Windows registration database is not valid. You can correct it with Word's Setup program." Do I need to submit a CAB? I think this is a "emergency" as without Word I can't type up the RFC and submit it to the CAB to solve the issue described in the error message.
@HamedLatif18 жыл бұрын
Excellent insights on how to run a CAB meeting... I would add, probably circulating RFC's to the CAB members ahead of time so members are not reading the documentation during the meeting. What about distributing minutes?
@Beyond20LLC8 жыл бұрын
That’s an excellent point. It would speed up the CAB tremendously and, more importantly, make it more effective since everyone would be better informed of the proposed changes.
@kundanbansod9256 Жыл бұрын
Great Information. I want to know an answer to an interview question that can be more generic and relatable to all IT service provider. Question : What is the most challenging task/situation you have faced and how you handled it ? Pleas answer.
@rajkumar-uh4co8 жыл бұрын
Nice Video. What about changes which are already discussed in Release CAB Meeting. ? Should they be discussed again in CAB Meeting ? one more thing which needs to be part of Agenda Meeting is Failed Changes I think release manager should also be part of CAB Meetings ?
@Wyatt_Spencer7 жыл бұрын
RE: Failed Changes, absolutely agree. RE: Release CAB, maybe. Why are there two separate meetings? RE: Manager as an attendee... Bear in mind that there is a huge range of IT organizational structures. That you're referring to a "release manager" indicates there may be differences between your organization, and, say... mine, where that isn't a position. In general, the best practice is to manage changes in a way that establishes and maintains stakeholder visibility to change.
@patoc28576 жыл бұрын
Guys/All, who in the organisation is responsible for sending change notifications to the business and why? I'm guessing that Service Desk plays a part here but the content of the notifications needs to come from Operations as the function that is implementing the change. How is this commonly handled in medium sized businesses? Seems that it may make more sense for Operations to assign someone a communications role instead specifically for Change notifications.
@Beyond20LLC6 жыл бұрын
Great questions! The Change Manager is responsible for creating the Forward Schedule of Changes. In general, communicating this would be the responsibility of the Service Desk, since they are responsible for operational communication with users. The Service Level Manager might also communicate aspects of this to specific Service Owner within the business, particularly if the change in question will impact an agreed service level.
@patoc28576 жыл бұрын
Thanks for the reply! I'm looking to provide some structure around communications as it can be time consuming when also factoring in major incident management but obviously critical for the business. It is a key role with little tolerance for mistakes. At the same time if we have 10 SD analysts in a virtual team who's job it is to handle incident management/service requests I don't think they shouldn't be asked to send these emails as they are generally v busy plus may have differing levels of English. Also as SD manager, it is too much to handle without delegating plus who does it if I am out of the office. Seems that all the information comes mainly from operations engineers/management where SD ends up copy and pasting the content prepared by operations into an email, checking the language used and picking send. From a business perspective it would make more sense for Operations to formalise the communications role within Operations itself as it would simplify the process by a) needing less people to send an email and b) have the service owner/source of information send directly. This is obviously subjective and dependent on the size of the team. It would be interesting to know how this is handled in larger corporations like banks and what is the job title of the person responsible.
@Rickety32633 жыл бұрын
Great content
@EssKayTee12 жыл бұрын
This approach is soooo out of date in the world of Agile & DevOps
@achmadzaky34472 жыл бұрын
why is you think that? since i think this personally a great approach too and can be adopted as well to the world of Agile and DevOps or you might mention also DevSecOps..
@shaunmckinley1208Ай бұрын
In the world of DevOps and Agile you still want to have CAB and TAB meetings. Just for the pipelines you might want to go towards a more automated process like what the ServiceNow DevOps module provides. You can set your criteria and have pipelines approvals automated.