Change Control vs. Change Management: Moving Beyond ITBy Edward Stickel With some of its foundational texts now decades old, IT change management is one of the most studied and utilized elements of the systems and infrastructure management discipline.
With some of its foundational texts now decades old, IT change management is one of the most studied and utilized elements of the systems and infrastructure management discipline. With so much academic thinking and so many years of practical application behind it, one would think that the effective management of change would now be commonplace in IT organizations and the companies they serve.
- Not all changes are logged 95%
- Changes not thoroughly tested 90%
- Lack of process enforcement 85%
- Poor change communication and dissemination 65%
- Lack of centralized process ownership 60%
- Lack of change approval policy 50%
- Frequent change notification after the fact 40% 1
- The scope of the process is not sufficient to cover all the necessary factors and tasks in making well-advised decisions on changes and implementing them effectively
- Because the value of the change control process is not apparent to the parties involved, it is seen as a superfluous, bureaucratic exercise and is not taken seriously, which results in poor compliance
By drawing some clear distinctions between the scope and nature of change management and of change control, this article hopes to point a way for otherwise competent organizations to address their deficits in handling changes to the IT infrastructure.