Change management is the IT service management discipline. The goal of change management in this context is to ensure that standard methods and procedures are used for efficient and timely handling of all changes to control IT infrastructure, to minimize the number and impact of any related incidents at the time of service. Changes in the IT infrastructure can appear reactively in response to externally imposed problems or requirements, e.g. legislative changes, or proactively seek to improve efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives. Change management can ensure the standard methods, processes and procedures used for all changes, facilitate efficient and rapid handling of all changes, and maintain an appropriate balance between the need for change and the potential adverse impact of change.
Video Change management (ITSM)
Library Information Technology Infrastructure
Changing management within ITSM (as opposed to software engineering or project management) is often associated with ITIL, but the origins of change as IT management processes precede ITIL significantly, at least according to the IBM publication Management System for Business Information .
Within the ITIL framework, change management is part of the "Transition Services" - the transition of something newly developed (ie an update to an existing production environment or deploying something entirely new) from the Service Design phase into Operation Service (also known as Business As Usual) and aims to ensure that standard methods and procedures are used to efficiently handle all changes.
Change management is the process used to manage the planned deployment of changes for all configuration items in the configuration management database (or "CI" in CMDB), which is part of the business life ("production") and testing ("UAT") of shared environment with other environments that a company wants under a change management - generally all environments that are under 'ICT Operations' control. It is usually not responsible for changes in the development environment (see below).
Changes are events that:
- approved by management
- implemented with minimized and accepted risks for existing IT infrastructure
- produces a new status of one or more configuration items (CI)
- provide increased value for businesses (increased revenue, avoided costs, or service upgrades) from the use of new or improved IT systems.
Maps Change management (ITSM)
In the development project
ITSM change management is usually not responsible for overseeing changes occurring in development or deployment projects that are normally delegated to change management processes determined by the project management methodology adopted for the project. However, a close relationship between the development project manager and the Change Manager is expected and the project manager may be required to use change management for items in the production environment or testing required for testing or release.
Process overview
Change management typically consists of improving and recording changes, assessing impacts, costs, benefits and risks of proposed changes, developing business justification and obtaining approval, managing and coordinating the implementation of change, monitoring and reporting on implementation, review and closing the change request.
ITIL defines the change management process in this way:
- The purpose of the change management process is to ensure that standard methods and procedures are used for efficient and appropriate handling of all changes, to minimize the impact of incidents related to changes in service quality, and consequently improve day-to-day operations organization.
ISO 20000 defines the purpose of change management (part 1, 9.2) as:
- To ensure all changes are assessed, approved, applied and reviewed in a controlled manner.
Change management is responsible for managing change processes that involve:
- Hardware
- Communication tools and software
- System software
- All documentation and procedures related to the operation, support and maintenance of the live broadcast system.
Any proposed changes must be approved in the change management process. While change management makes the process happen, the decision authority is the Change Advisory Board (CAB), which generally consists of people from other functions within the organization. The main activities of change management are:
- Filter changes
- Manage changes and change process
- Occupy CAB and CAB/Emergency committees
- Review and close Request for Change (RFC)
- Management reporting and provide management information
Definition
ITIL's concept of change management includes developing business justification. This is an extension of the scope of other change management concepts, and overlaps with the IT portfolio management concerns and areas covered by the initiation phase of the project management and management program.
For example, IBM's "Yellow Book" concept of change control (as part of resource control) is closely related to the transfer of items from the project into production. Similarly, Schiesser in IT System Management defines Change Management as "a process to control and coordinate all changes to the IT production environment."
See also
- ICEFLO
- IBM Tivoli Configuration and Change Management Database
- Network configuration and change management
- Change management
- ITIL Incident Management
- ITIL Release Management
- Main article of ITSM
- Microsoft Operating Framework
References
Source of the article : Wikipedia
0 Comments