Posted by: Robert Davis
Change Control, Change Management, CMDB, Configuration Management, IAP, Information Assets Protection, Infrastructure, IT Infrastructure, ITIM, Service Delivery, Systems
Even a small change in a CI could cause a mission-critical application to fail or disrupt a service. To reduce the likelihood of undesirable consequences, thorough change planning is required for adequate change construction including: back-out planning, change testing and documentation updating. As a particular, back-out planning is necessary should the change result in an unacceptable configuration state. Additionally; since most information systems are frequently too large, integrated and complicated for service design failure or success to be predicted without testing, experimentation should be built into the change process. Lastly, CI documentation affected by the change should be correlated for updating to ensure appropriate resource utilization and maintenance.