Change Control
From Wikipedia, the free encyclopedia
 |
This article may require cleanup to meet Wikipedia's quality standards. Please discuss this issue on the talk page or replace this tag with a more specific message. This article has been tagged since April 2006. |
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 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. It 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.
[edit] 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 seven steps. Each step may have another process associated with it. These start with the receipt of the Change Request:
- Record
- Assess
- Plan
- Build
- Test
- Implement
- Close.
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 categorises that request, and decides upon who should make an IMPACT ASSESSMENT. The IMPACT ASSESSOR or ASSESSORS then make their risk analysis and make a judgement on who should carry out the Change, typically known as an SDU team (Service Delivery Unit). 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 then they will BUILD their solution, which will then be TESTED. When this is approved, the Change can be IMPLEMENTED, and when the client agrees all is OK, the job can be CLOSED.
[edit] 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 categorisation 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 judgement 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 Board (CB) - An appropriate management Board used to review the change process and specific changes where required. Typically comprising Service Delivery Manager, Customer representative & Change Manager
