Change management best practice
Posted on 2016-09-21
Hi all, I was hoping you could offer some best practice advice in terms of change management where multiple services are affected.
We currently have a change managmenet process in place but where a change encompasses numerous services I.e 20+ what we have been doing is creating one overarching request for change form. This works fine in the majority of cases but I'm concerned about the lack of detail in this form in terms of implementation plans testing, risk assessments etc. For example the implementation plan might say that server x needs to be shut down or moved to anothet DR site and thats it. Whereas if this was to be done on its own it would cover all the steps required to do this.
To overcome this surely you would need an RFC form for each affected service which would be time consuming.
What's the best way of managing these situations as we have had issues arise because correct procedures weren't followed or testing wasn't completed because it was part of the overarching RFC.