Change Management Image File history File links Broom_icon. ...

The goal of Change Management is to ensure that standardized methods and procedures are used for efficient handling of all changes, in order to minimize the impact of change-related incidents and to improve day-to-day operations.

 Main article: Change Management (ITSM) 

A change is “an event that results in a new status of one or more configuration items (CI's)” approved by management, cost effective, enhances business process changes (fixes) - with a minimum risk to IT infrastructure.

The main aims of Change Management are:

• Minimal disruption of services
• Reduction in back-out activities
• Economic utilization of resources involved in the change

Change Control is a formal process used to ensure a product, service or process is only modified in line with the identified necessary change. It is part of ITIL It is particularly related to software development as during the early development of this engineering process it was found that many changes were introduced to software that had no obvious requirement other than the whim of the software writer. Quite often these unnecessary changes introduced faults (bugs) Later it became a fundamental process in quality control. A change "freeze point" was introduced to suspend any further changes until after the completion of the initial project. Change Control is also formally used where the impact of a change could have severe risk and/or financial consequence. Typical examples from the computer and network environments are the upgrade of operating systems, network routing tables or the electrical power systems supporting such infrastructure, not forgetting changes to the contract itself. Atil, also spelled Itil (Turkic for Big River), was a name of the Volga River and of the capital of Khazaria from the middle of the 8th century until towards the end of the 10th century. ... Computer software (or simply software) refers to one or more computer programs and data held in the storage of a computer for some purpose. ... A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working as intended, or produces an incorrect result. ... For the Jurassic 5 album, see Quality Control (album) In engineering and manufacturing, quality control and quality engineering are involved in developing systems to ensure products or services are designed and produced to meet or exceed customer requirements. ... Lets talk about risk control strategies, anyone with more information and willing to share, please do so. ... The NASA Columbia Supercomputer. ... “Computer Networks” redirects here. ... It has been suggested that Maintenance OS be merged into this article or section. ... It has been suggested that Routing protocol be merged into this article or section. ... Transmission lines in Lund, Sweden Electric power, often known as power or electricity, involves the production and delivery of electrical energy in sufficient quantities to operate domestic appliances, office equipment, industrial machinery and provide sufficient energy for both domestic and commercial lighting, heating, cooking and industrial processes. ...

The process

There is considerable overlap and confusion between change management, configuration management and change control. The definition below is not yet integrated with definitions of the others.

Change Control today is seen to be a set of six steps. Each step may have another process associated with it. These start with the receipt of the Request for Change or RFC, or a Request for Service (RFS):

1. Record / Classify
2. Assess
3. Plan
4. Build / Test
5. Implement
6. Close / Gain Acceptance.

A formal request is received for something (usually in the Client's [contract]) to be changed, known as the "Change Initiation". Someone then RECORDS and classifies or categorizes that request. Part of the classification would be to assign a Category to the change, i.e. is the change a "MAJOR BUSINESS CHANGE", "NORMAL BUSINESS CHANGE" or "MINOR BUSINESS CHANGE". The first category would be immediately liable to a CAB(see below for references to CAB's). Then it would be necessary to assign a priority to the change, i.e. "EMERGENCY CHANGE", "EXPEDITED CHANGE" or "NORMAL CHANGE". The first would be already completed in reality with the change being done retrospectively (An Emergency CAB may have been involved too). The second implies that it needs doing within the SLA (Service Level Agreement) times. The last is business as usual. Finally either here or at consolidation, the Impact Level needs to be decided, i.e. is this change going to have a "MAJOR", "NORMAL" or "MINOR" "IMPACT" on the business. The first should go to a CAB. The classifier then decides upon who or whom should be invited to make an IMPACT ASSESSMENT. The IMPACT ASSESSOR or ASSESSORS then make their risk analysis typically by answering a set of questions concerning risk, both to the business and to the IT estate, and follow this by making a judgment on who or whom should carry out the Change, typically known as an SDU team (Service Delivery Unit). If more than one Assessment has been carried out, it should be the job of the Change Manager or Change Administrator to consolidate or summarize these, as at this point they may decide or have it decided by policy to have the first CAB, or Change Advisory Board meeting to ascertain that there is a business justification for the change. Afterwards the decision on the technical justification can be carried out. The change is then sent to the new Change Owner or CO. This will be an SDU team who have been identified or pre/identified as having a major role in carrying out this particular type of change. The SDU's first job is to PLAN their change in detail, and also construct a regression plan, if it all goes wrong. If their plan is agreed (this could be another CAB, then they will BUILD their solution, which will then be TESTED. They will then seek approval and request a time and date to carry out the implementation phase. They may do this by raising a flag called a Request to Implement flag (RTI). This is then answered by the Change Manager when this is approved (by another CAB)with an Authority to Implement flag (ATI), the Change can then be IMPLEMENTED but only at the time and date agreed. Following Implementation, it is usual to carry out a Post Implementation Review (PIR) which would take place at another CAB meeting. When the client agrees all is OK, the change can be CLOSED. The various CAB meetings would of course be one meeting charged with looking at all changes in their various phases and agreeing that they may proceed or not, as the case may be. The information for the CAB's would be obtained by interrogating the Forward Schedule of Change (a database of the changes).

Roles of involved people

The following roles have been identified in the Change Control process:

• Change Initiator (CI) - The Person who initiates the request and who ultimately will confirm its completion.

• Change Sponsor (CS) - The Person who gives business approval for a change.

• Change Administrator (CA) - One or more Change Administrators carry out initial categorization and assessment, monitor progress of the change requests through the change Owners and ensure acceptance.

• Impact Assessors (IA) - Relevant people who assess the impact of the change

• Change Owner (CO) - Typically the person who is allocated to a change and who manages it through to acceptance and closure

• Change Manager (CM) - The Change Manager manages the overall change process, acts as a point of escalation for COs, exercises judgment in assessing requests and escalates to a Change Board. The CM also acts with authority delegated by the Change Board to drive emergency changes or expedited changes through the system

• Task Owners (TO) - Task Owners are assigned specific tasks by the Change Owner and own them through to completion. The system supports supervision of assigned tasks

• Change Advisory Board (CAB) - An appropriate management Board used to review the change process and specific changes where required. Typically comprising Service Delivery Manager, Customer representative & Change Manager

External links

• Change control minimizes outages
• McCabe CM - TRUEchange McCabe CM - TRUEchange introduces end-to-end configuration management, from idea to implementation and on to release. Unlike most configuration management tools, TRUEchange manages projects rather than files, and physical change objects rather than individual deltas. TRUEchange maintains the implementation of each development task as a complete and atomic object, referred to as a change-set.