I’m hitting a wall mentally with a somewhat specific scenario. We have our application owner’s review and endorse changes prior to Change Manager or CAB review, and that works fine for most situations.
Where I’m caught is for changes that impact many systems, for example firmware upgrades on routers in a datacentre. This has the ability (due to lack of redundancy, etc. but that’s another issue
) to bring down most of our applications, but at the same time it doesn’t seem efficient to have 20+ each review and endorse a change, as we all know it would take months to get everyone to sign off.My thoughts would be for such large impacts the change will be going to CAB anyway, to which these application owners are members (if they decide to attend!), and the review and endorsement is completed at that stage. I’m wondering how others in the CM field would approach this sort of situation?
