Posted: Wed Oct 05, 2016 8:12 pm Post subject: Introducing a new change freeze process?
I'm starting a new CM role and processes maturity seems to be a key thing for me to look at. They will be having a change freeze & period of enhanced change control either side of it. Any experience of introducing a robust process appreciated!
I'm thinking: identify key business & IT stakeholders. Comm to them about these periods & that they will be required to review any submitted RFCs for approval during. Initiators to identify any known RFCs needed during that period & have them raised 1 week before? Rest would be rejected unless business need, risk minimal, due diligence etc documented in the RFC. Then they would go to an e-CAB for approval by identified stakeholders?
Joined: Sep 16, 2006 Posts: 3500 Location: London, UK
Posted: Thu Oct 06, 2016 7:21 am Post subject:
A Change Freeze usually means no Changes except under extremely rigorous conditions
You as the new CM needs to define this first
And then distribute to all stakeholders and change raisers to concur
And then once agreed manage it like it is the reason for being
Only those that meet the conditions get processed
Report to mgmt.
Report to stakeholder
Vulgar: This is where CM separates the sheep from the goats and the wolf.
You are the wolf. You have senior mgmt to override you in accordance with defined process above otherwise.. you become a goat or sheep and are useless as a CM - no authority just a ticket punch checker _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum