<div>
<div class="content wysiwyg-content">
Hi all, &nbsp;I was hoping you could offer some best practice advice in terms of change management where multiple services are affected.<br />
<br />
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, &nbsp;risk assessments etc. &nbsp;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.<br />
To overcome this surely you would need an RFC form for each affected service which &nbsp;would be time consuming.<br />
<br />
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.
</div>
</div>


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.

Change management best practice

A miscellany is defined as a "collection of various pieces of writing by different authors", but it has come to mean something "Of items gathered or considered together of various types or from different sources" or "a collection or group composed of members or elements of different kinds". The word "miscellaneous" comes from the Latin word "miscere", meaning "to mix." You might have heard the expression "a mixed bag," which applies when you don't quite know what you're going to get. More commonly, a miscellaneous group is made up of an odd group of things that don't fit anywhere else.

Miscellaneous

A Document Management System (DMS) is a system (both hardware and software) used to track, manage and store documents and reduce paper. Most are capable of keeping a record of the various versions created and modified by different users (history tracking). It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.

Document Management

Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.

Project Management

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.