Posted: Fri Jan 11, 2008 6:10 am Post subject: Guidance on how to improve procedures
I'm just out of university and I got a job at this food processing company. I have no experience with Change Management at all (however, I have taken courses that slightly talked about it ). I am now in charge of being the IT Change Manager and I have to review, evaluate and improve the current change management procedures (I have a report due in 2 weeks ).
My question is, where do I start? Do you guys know any good book to look at?
Also, I have been looking at the processes/procedures and they look OK to me. Any suggestion about how I should approach the processes and procedures?
Not entirely sure what you need to report on, i'm guessing on where you can improve? So here's a few things you can do
Evaluate the current process:
Is it well documented?
Is it being followed across the organization?
Interview current users for their perspective
Interview current process owner(if one defined)
What are the current metrics if any?
Where do you want to go:
What parts of the process need to be documented better?
What currently is working for the process?
What currently are the biggest issues with the process?
What is the organizations end vision of the change management process?
What are the gaps of current process and golden(to be) process?
Is there support from management for the process and to improve it?
What metrics do we need?
What are the current metrics telling us needs to be improved?
Should be a few things to help you get started.
Also i'd suggest the Blue book but if you are fresh out of school and haven't had alot of exposure to ITIL yet it may be a bit overwhelming. There are a few ITSM general books out there about 200-300 pages that cover all the disciplines at a high level. That would be good to gain a general understanding. Or if the option is there recommend a Foundations class to really jumpstart a general understanding. _________________ Adam
Practitioner - Release and Control
"Not every change is an improvement, but every improvement requires a change"
I completely agree with Adam, those are the types of things that will help you scope out what you're trying to achieve.
If I can underline one thing which Adam was getting at anyway it's that you need to get the requirements of your boss/customers documented and agreed. This creates a basis for you to articulate clearly your goals for the project and therefore no confusion over expectations when you get to the end.
Oh, and by the way, don't fix it if it ain't broke! In other words changing processes for the sake of change is not beneficial - take what you can from ITIL practices - Process improvement is often an iterative journey so don't turn the office on it's head over night!
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