References:
ISO20000: Section 9.2: Change management
Comments:
There are a number of types of change in any IT Department and it is important that each of them is defined and associated wiith an effective method of dealing with them that does not create ineffective bureaucracy. It is unrealistic to expect a single change team/forum to be able to cope with all possible types of change in the IT Department except in smaller IT Organizations.
The Change Management team exercise strict control over defined changes to the IT operating environment. Each defined change is registered and goes through a controlled process of assessment and approvals during its lifecycle.
Change Management is managed by a tightly controlled Forward Schedule of Change controlled by the Change Team, or the Change Controller in small and medium sized organizations.
Change and Release are two aspects of the same service process. Release Management being the back end of the Change Management process.
In larger organisations once the change is developed the control of its release into the IT Operating Environment is passed to a Release Management Team. In small and medium sized organizations release is typically taken care of by the team managing and developing the change activity.
See Change and Release Management Forum
Supporting PCAP Documents available in the Shop:
1: Change Manager Job Description
2: Change Controller Job Description
3: Change Management Procedure
4: Service Request Management Procedure
Visit the PCAP Store for Freeware and Demo Documents: http://www.pcap.co.uk
Visit the Change Management Shop Area: Click Here
Visit the ISO20000 Shop Area: Click Here
Last edited on Wed May 21st, 2008 08:13 am by bobmckean
|
