Introduction

CHANGE management is described in several areas, untiger article refers to the world of computer science. With respect to ITIL (IT infrastructure http://www.itil.org/ or http://de.wikipedia.org/wiki/IT_Infrastructure_Library) we differentiate with respect to several disciplines, between:

• Incident management (disturbance recovery)
• Problem management (problem of Eruierung)
• CHANGE management (change controls)
• Config/ate management adjust (stocktaking of computer science)

These disciplines are described as service management and to concern always all parts of the software (SW) hardware (HW) and networks of a IT infrastructure. The discipline CHANGE management covers a coordinating of changes in the IT and in the following article in the detail is explained.

CHANGE management

IT becomes an increasingly more critical factor for the enterprises. Business requirements constantly change, new technologies are used, for users demand a ever higher service extent, in order to be able to fulfill their tasks. All these factors cause an IT-environment, in the managements and control of CHANGEs are very exactly regulated. The experience shows that a high portion of problems can be retraced concerning the IT-service-quality up to a CHANGE at the system. Such problems cause enormous business costs and become less and less acceptable. This article describes the Best Practices for CHANGE management and deals with the fundamental role of this range for the implementation of many other ITSM (IT service management) Best Practices. Finally each development of the IT-infrastructure, whether it refers now to Capacity management, network services management or the service Desk, brings CHANGEs with itself, which mean again a risk. Therefore a very strict proceeding for an effective CHANGE management is meaningful.

CHANGE management - goals

The principal purpose CHANGE management of the process is to be guaranteed that standardized methods and procedures for the execution of efficient and fast CHANGEs are used, so that the effects of CHANGEs are minimized on the service quality and the execution of the enterprise activities. Such a procedure is necessary, in order to manufacture a balance between the need for a CHANGE and effects of the CHANGE. It is particularly important that the CHANGE managements process transparency is and plans open communication interfaces, so that changes without disturbances can be accomplished in the productive environment.

Mission statement

Within the strategic objective (mission statement) the term has "authorized Changesl' a very strong meaning and is exactly fixed. One could in-interpret even But good CHANGE management procedures become fair both the small everyday CHANGEs, and the CHANGEs, which are necessary for the immediate re-establishment of a critical service or which effects for a large number of customers have. If for example a user liked to change its password, a complete Request would be inadequate for CHANGE inclusive following discussion of the CHANGE Advisory board for permission. Also a CHANGE, which must take place immediately, in order to restore a critical service, should go through a faster working on path than normal CHANGEs. In this module is received still more in greater detail on that. Some see additional bureaucracy in the implementation of comprehensive function-spreading CHANGE management processes with formal documentation, discussions and permission. At first sight one could do mine that this all-comprehensive CHANGE management process will obstruct those, which must accomplish the CHANGEs, in order to keep the enterprise of the IR environment upright. Actually processes however the necessity for constant Ad-Hoc-CHANGEs should reduce suitable CHANGE management (and Configuration management), which one finds in environments, which cover no or no sufficient CHANGE and Configuration management procedure. A durchdachter CHANGE and Configuration management process should work on and approve CHANGEs, which are necessary, briskly. These authorized CHANGEs are supported by the IT management and are examined at risk, expense and effects.

Process implementation

In the today's commercial world the dependence on IT systems and technology demands from the management that much time is invested into the estimation of the meaning of enterprise changes on the IT and the influence of IT changes on the enterprise. The administration of CHANGEs became a VoIlzeit task. If CHANGEs can be administered in such a way that the risk, which are optimized weight of the effect and possible interruptions and CHANGEs naturally also with the first attempt are successful is it for the enterprise of fundamental importance that this process is fast implemented.

CHANGE management - tasks

CHANGE management is responsible to administer the CHANGE process. The process cares and controls only that CHANGEs are approved and efficiently, economically and with minimum risk for the new and the existing services are implemented. In order to accomplish this in a suitable kind, a process is needed. But procedures and guidances also detailed are used, as the different things are to be accomplished in the process. In order to be able to estimate the risk of each CHANGE, it is very important the fact that detailed information about the individual Cis (Configuration Items) and their relations is to each other available. The components of the left infrastructure, Configuration Items, are administered in the context of the Configuration management. The CHANGE management covers typically:

• Initiate, documenting and authorizing changes
• Estimate of the effects, costs, advantages and risks of the considered changes
• Justification and permission of CHANGEs
• Tarpaulins and coordinating of the implementation of CHANGEs ~ supervising and reporting over the implementation
• Examination and locking treatment of Request before CHANGEs (RfCs)

An important task is that CHANGEs are planned. Only planned and CHANGEs provided with an appropriate schedule can be effectively controlled, since this guarantees that sufficient time is present, in order an overview to receive, which must be done and that is done, what be done must. Around effective to accomplish well planned CHANGEs need we view of necessary and available resources. In addition we need a good Tool. Communication is the key for a successful CHANGE process. Communication is OF the reason too little that CHANGEs are not correctly accomplished and Incidents to arise. The more coworker to be informed, the more largely is the chance that the CHANGE is analyzed appropriately and supervised, so that execution is error free. Therefore a communication structure (e.g. the CAB, CHANGE Advisory board) is necessary. Important are naturally also report. These help to communicate the CHANGEs themselves and like these were accomplished.

Terminology

The definition of the terms are

CHANGE

Adding, changing or removing from authorized, supported or frozen hardware, network, software, Anwenungen, environment components, systems, Desktop Builds or appropriate documentation.

Request for CHANGEs

Form (paper or on-line form) is used for the admission of details of a request for modification, which refers to any CI within i' the infrastructure or to with the infrastructure connected procedures or devices.

Forward Schedule OF CHANGE

Schedule, which contains details of the CHANGEs approved for execution and their intended implementation date.

Articles in category "CHANGE management (ITIL)"

We found here 28 articles.

Related Websites

We found here 3 related websites.

• ITIL Change Management
  The relationship of Change Management with other ITIL processes.


• ITIL Change Management www.ITILsurvival.com all your ITIL ITSM ...
  www.ITILsurvival.com all your ITIL ITSM Service Management process documents, books, cds, elearning.


• ITIL World
  The Change Management function consists of four main operational objectives. ... Change Management will manage the implementation of all RFCs that pass ...