Content
Change management is part of IT service management . The goal of change management in this context is to ensure that standardized methods and procedures are used to efficiently and expeditiously service all changes in the management of the IT infrastructure in order to minimize the number and impact of any related incidents on the service. Changes in IT infrastructure can arise either as a response to problems or requirements imposed from outside, for example, changes in legislation, or as activity in the process of increasing efficiency and effectiveness, or as activities to include or reflect business initiatives, or from programs, projects or initiatives to improve the quality of service. Change management can provide standard methods, processes, and procedures that are used for all changes, facilitating the efficient and timely servicing of all changes and maintaining an appropriate balance between the need for change and its potential harmful effects.
ITIL
Change management in ITSM (as opposed to software engineering or project management ) is often associated with ITIL , but the emergence of changes as a management process in IT was significantly preceded by ITIL, at least according to the IBM publication Information Management System. [one]
Within ITIL, change management is responsible for controlling changes in all configuration elements of the configuration management database (or “EI” in CMDB ) in a real environment, testing and training environments (all environments under the control of “ICT Operations.” Usually it is not responsible for changes to development projects (see below). †
Change Management for Development Projects
Change Management ITSM is usually not responsible for monitoring changes that occur in deployment or development projects. These changes are usually controlled by the change management process established by the project management methodology adopted for the project. However, a close relationship between development project managers and the change manager is necessary, and the project manager may need to use change management for the work or test environment elements needed to test or release the product.
Process Overview
Change management, as a rule, consists of the occurrence and registration of changes, assessing the impact, costs, benefits and risks of the proposed changes, developing a business case and obtaining approval, managing and coordinating the implementation of changes, monitoring and implementation reports, reviewing and closing requirements for changes.
ITIL defines the change management process as follows:
- The goal of the change management process is to provide standardized methods and procedures used to efficiently and promptly service all changes in order to minimize the impact of incidents caused by changes on the quality of service, and to consistently improve the organization's day-to-day operations.
ISO 20000 defines the objectives of Change Management (Part 1, 9.2) as follows:
- Ensure that all changes have been evaluated, approved, implemented and reviewed in a controlled manner .
Change Management is responsible for managing the process of change related to:
- Equipment
- Communication equipment and software
- System software
- All documents and procedures related to the operation, support and maintenance of working systems.
Any proposed changes must be approved by the change management process. Although change management starts the process, the decision body is the Change Advisory Board (CAB), which is composed mostly of people from other parts of the organization. The main areas of change management are:
- Change Filtering
- Change Management and Change Process
- Chairmanship of the CAB and Emergency Change Board (emergency CAB)
- Review and close Requests for Change (RFC)
- Management reporting and management information
Ambiguities
ITIL's change management concept includes the development of business case studies . This broadens the scope of other concepts of change management, and duplicates the tasks of managing the spectrum of IT projects, as well as the areas covered by the initial phases of program and project management.
For example, IBM's Yellow Book on the concept of change management (as a subset of resource management) was strictly focused on transferring results from projects to production. [2] Similarly, Schiesser in the IT Management System defines Change Management as “the process of managing and coordinating all changes in the IT production environment." [3]
See also
- IBM Tivoli Configuration and Change Management Database
- Network configuration and change management
- Organizational Change Management - organizational change management , often referred to simply as “change management”
- Main article on ITIL (IT Infrastructure Library - library of information technology infrastructure)
- ITIL Incident Management
- ITIL Release management
- Main article about ITSM (IT Service Management)
- Microsoft Operations Framework
Notes
- ↑ IBM Global Services. IBM and the IT Infrastructure Library (PDF) (2003). Date of treatment December 10, 2007. Archived on August 26, 2012.
- ↑ IBM. A Management System for the Information Business. - White Plains, New York: IBM, 1980.
- ↑ Schiesser, Rick, 2002. IT Systems Management. New Jersey, Prentice Hall. ISBN 0-13-087678-X