ITIL Change Control

ITIL Change Control is the procedure to ensure that all Changes are controlled, including the submission, analysis, decision making, approval, implementation and post implementation of the Change. Many IT organizations are adopting the ITIL framework and other ITIL Change Control methods to help them align their priorities with business objectives and efficiently deliver services. Pink Elephant verification is becoming a key checklist item for these organizations. However, because ITIL covers such a broad range of processes, no single solution currently supports all areas. Therefore, companies need to utilize a network of products. By using ITIL-certified products, organizations can more easily achieve adherence to the framework.

There are many organizations, which act as a process control application for change and release management. It establishes an ITIL Change Control framework, complete with process control, check points and approvals, and auditable change records. It provides comprehensive workflow management, version management, issue management, build management, baseline management, and release management. Change management and ITIL Change Control ensure that standard methods and procedures are used to quickly evaluate and approve/ disapprove every proposed change. The goal is to minimize any negative impact of change-related incidents on IT services.

Different types of changes require different change management procedures. Many changes can be made directly by IT support staff with no involvement from the development team. Other changes, such as rolling out an application update, are more complex and will require involvement from developers and the Change Advisory Board (CAB). Many organizations focus on this second type of change. And they give the CAB knowledge of how a proposed change in one part of an application or IT process will impact other parts, and what services could be impacted by the proposed change. With this information the CAB can develop accurate cost and time estimates for implementing the change, and they can eliminate surprise side effects that cause unplanned downtime.

The objectives of ITIL Change Control are to:

• Assess the impact of scope changes on project schedules, resources, and pricing;
• Provide a formal vehicle for approval to proceed with any changes for this Service Listing; and
• Provide a project audit record of all material changes under this Service Listing

The object of ITIL Change Control is to ensure that standardized methods and procedures are used for efficient and prompt handling of all Changes, in order to minimize the impact of any related Incidents upon service.  Changes in the IT infrastructure may arise reactively in response to Problems or externally imposed requirements, e.g. legislative changes, or proactively from seeking imposed efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives. 

Change Management using ITIL Change Control can ensure standardized methods, processes and procedures are used for all Changes, facilitate efficient and prompt handling of all Changes, and maintain the proper balance between the need for Change and the potential detrimental impact of Changes.

ITIL Change Control is responsible for controlling Change to all CIs within the live environment.  It is not responsible for change within ongoing projects, which are controlled by the project change process.  However close liaison between development project managers and the Change Manager is expected. 

ITIL Change Control would typically comprise the raising and recording of changes, assessing the impact, cost, benefit and risk of proposed Changes, developing business justification and obtaining approval, managing and co-coordinating Change implementation, monitoring and reporting on implementation, reviewing and closing RFCs.