Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Posted: Thu Mar 22, 2007 1:33 am Post subject: Defining a Change Management Operating Level Agreement (OLA)
Hi all! I've just passed the Foundation, so I am still in the dark on much of the details of Change Management. However, I've searched the forum and I've not come across any information regarding OLA's.
I want to enlist some advice on defining an Operating Level Agreement for inter-departmental IT (Server side) support.
1. Do you actually define and establish an OLA for Change Management as part of your process?
2. If so, how did you structure your OLA for server side change?
Joined: Sep 16, 2006 Posts: 3590 Location: London, UK
Posted: Thu Mar 22, 2007 1:52 am Post subject:
for whom would you apply the OLA
For example,
if you want to ensure that 'technical approvers' must respond within __ minutes/hours/days for approval
This would be a good OLA between change mgmt and the technical teams - system, network applications
Or a similar one for Business or Customer representative to acknowledge or approve the changes affecting their area - service managers, customer relations managers.
The CM Process should be defined first
then the OLA for the system team in reacting/writing/approving changes should be defined and agreed.
Also, realize that unlike a SLA, the OLA is like a 'gentleman's agreement'
if the team does not comply, they dont get penalized really but you can harass their mgmt with your mgmt _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Thanks for the information John! Based on your response, an OLA would be premature at this time, since I am developing my CM process now.
What is the difference between a CM Policy and a CM OLA? I'm trying to define guidelines that each service owner (technical teams) should adhere to when planning changes to the network infrastructure. Application and Desktop change will come later.
So what are the guidelines when planning a good CM policy?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum