Change management (ITSM)

Change managementis anIT service managementdiscipline. The objective of change management in this context is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to controlIT infrastructure,in order to minimize the number and 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 improved efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives.

Change management can ensure standardized methods, processes and procedures which 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. Change management within ITSM (as opposed tosoftware engineeringorproject management) is often associated withITIL,but the origins of change as an IT management process predate ITIL considerably, at least according to the IBM publicationA Management System for the Information Business.[1]For example, the IBM "Yellow Book" conception of change control (as a subset of resource control) was strictly concerned with the transfer of deliverables from projects into production.[2]Similarly, Schiesser inIT Systems Managementdefines Change Management as "a process to control and coordinate all changes to an IT production environment."[3]

See also

edit

References

edit
  1. ^IBM Global Services (2003)."IBM and the IT Infrastructure Library"(PDF).Retrieved2007-12-10.
  2. ^IBM (1980).A Management System for the Information Business.White Plains, New York: IBM.
  3. ^Schiesser, Rick, 2002.IT Systems Management.New Jersey, Prentice Hall.ISBN0-13-087678-X