Posted: Thu Dec 12, 2013 10:42 pm Post subject: How detailed should a back out plan be?
I've had a look through previous discussions and cant see an exact answer to my question. Apologies if I am repeating anything.
I am currently trying to encourage my IT colleagues to include more detail in their RFC backout plans. Currently I am lucky if I get more than 2 lines of text! I go along the lines of "if you were hit by a bus tomorrow and your RFC had failed, we would need to be able to open your RFC and back it out from your plan". They on the other hand are fighting this as it they feel that if someone were to back out their RFC in their absence, it would be someone in their team and so 1 - 2 lines of information would be enough to tell them what to do.
I was just wondering what other people's thoughts were? and what stance you take in your roles as fellow Change Management, ITIL professionals?
Joined: Sep 16, 2006 Posts: 3233 Location: London, UK
Posted: Sat Dec 14, 2013 4:08 am Post subject:
the answer is it depends
It depends solely on what is the requirement from the change management policy and process.
The back out plan needs to be a statement or series of statements that indicate that there is a process - standard or otherwise - that will be actioned if there is a need to undo the work or restore to a previous version.
If there is a standard process - back up etc - then the change raiser needs to make sure the info in the CM form is clear enough to satisfy the CAB
It is one of those subjective questions that truly depends on the context _________________ 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