Change, Project, and Release: the core of IT Service Supply Chain (Part 1)
By Laurent Duenas, March 15th 2013
Main objectives of Change Management
Control Change impact on Live environment
This is definitely the main objective of Change Management. Knowing that 80% of incidents in Production stem from poorly controlled changes, nobody contests the role of this process, whose goal is to limit any negative impact of change on IT Service released into the Live environment, and implicitly, limit any impact on business activity.
The objective of Change Management is to get sure that components themselves or planned operations are controlled in order to prevent risks, by checking the quality of the new or modified components involved in change or by securing operations aimed at releasing them.
Control Change costs
In line with the basics of the ITIL framework, search for cost optimization is part of the major objectives of this process. Due to competitive pressure, an IT organization must rely on permanent controls to make sure that any business or technical evolution keeps costs as low as possible. Another way of optimizing cost is not to incur any change at all unless it is justified by a business benefit.
The goal of the Change Management process is to manage change in an optimal way without “uselessly reinventing the wheel”. Classifying changes leads to the implementation of “change models”, structuring tasks, controls and requirement levels during the stages of build, integration or deployment into the live environment. Efforts from teams involved in change are therefore better integrated and as a result more efficient.
Contribute to the agility of the organization
Last but not least, one of the main objectives of Change Management is to make sure that change implementation deadlines are met. Just because it is poorly organized, an IT organization cannot miss business opportunities, jeopardize the time-to-market of its products, or disregard its legal obligations due to its inability to implement change within deadlines. This is especially true when it comes to business requirements.
Through change classification and capitalization of experiences, Change Management makes sure that the right change models are implemented in order to optimize both process and release timeframes.
► No link
► No link
► Ebook "Change & Release ...."
Copyright © 2013 - PRACT Publishing