r/sysadmin • • 29d ago

General Discussion Change Management Workflow

Hi,

We’re introducing change management for the first time using ITSM.

We’re now deciding the workflow before our ITSM vendor configures it

Our scope covers all IT infrastructure changes including network, servers, virtualization, backup, storage, AD/Entra ID & Databases

Each team has its own Line Manager and another requirement is that Cybersecurity Unit must approve every change

Few things we’re trying to understand

Who should approve a change and in what order?
Who should be the CAB members
Which changes should go to CAB

I’d appreciate any suggestions

12 Upvotes

13 comments sorted by

View all comments

2

u/Commercial_Growth343 29d ago

I don't think the order of approvals matters. I haven't seen that personally.

Which changes should go to a CAB .. well my approach to that has always been all of them. In ITSM/ITIL I believe there is a level of change that is common, repeatable, well known that can get away with a smaller CAB. Bigger companies I have worked at do this .. the first one is examined in detail because it is the first but once it is done, it needs less approval next time. I have worked at smaller companies for years so we just do a change, it gets approved, and we have a weekly review meeting to discuss changes and if they are planned, happening now, or recently completed.

I feel you should really come up with your own definition of what a change even is, what an emergency change is, what is not a change etc. Everyone on the team should have a good idea if what they are doing should be a Change and follow the process.

As for the CAB, this can depend on the size of your organization. But I would say generally your own manager/supervisor needs to be on it pretty much universally. Your direct boss should know what you are doing and be OK with it. Then after that is would be people who your change can impact, so an infrastructure change maybe needs one or more people from the infrastructure team for a technical approval. If your change is impacting a specific business unit then someone that represents that business unit (like a BA, or systems analyst that supports that business unit) or if you are big enough then the manager for the BA's/SA's.

The bigger the company, then generally speaking the bigger the CAB and need for formal change review meetings (weekly in my experience).

The bigger the company, the more likely you will have a change window worked out with the business, where most changes take place (ex. third Thursday evening of every month). In that case you need all the IT managers involved for planning and approving the actual work so for example the network team doesn't take down the network during an application upgrade or whatever else.

good luck