Which ITIL Process Should We Implement First?



Learn Management Articles on management-info.biz. Which ITIL Process Should We Implement First? article will help answer your questions on Management Articles.We at management-info.biz specialize in Management Articles. Management Articles at management-info.biz provides the most up to date news and articles. If you have questions please do not hesitate to contact us.

The following question is usually debated a lot amongst IT managers. “With which process should we start when implementing ITIL?” Everybody has their own views, but here are my takes on it.

Some consultants sat that one must start with Service Level Management. Theoretically, it would be the perfect option, but how are you going to negotiate SLA's on your MTTR (Mean Time To Repair) if you are not measuring your MTTR through Incident management. This way you will get an idea of your capabilities and of what a realistic MTTR would be for your support teams. It may however be a good idea to start with a Service Catalogue, but that is only one aspect of Service Level Management and not a process.

A lot of people state that one must start with Configuration management. Again, I think that it would be perfect in theory, but in practice it is a different story. How will you keep your CMDB up to date, if you do not have a mature enough Change management process to keep the data up to date? A discovery tool will help, but there is still information that may need manual updates via Change management, e.g. costs, locations, user’s asset tag nr's etc. Configuration management is also one of the most difficult processes in to implement and show immediate benefits for. It is usually better to start with something easier and something that will show immediate benefit with minimum effort.

The best place to start in my opinion is with Change Management. Gartner reports that 80% of infrastructure failures are caused by changes. So, if you can have ALL your changes under control as soon as possible, a lot of these failures will be prevented. That is definitely a quick win and quick wins is what you want to keep the motivation of support teams up and keep upper management committed to your project. It may be a while to realize the benefits of Service Level Management or Configuration Management.

A good one would also be Incident Management, it is a fairly easy process and you should also be able to gain early benefits.

When Change and Incident management are well on their ways you can start to look at the other processes, especially on the Service Support side.

Oh yes and obviously you will need a Service Desk right from the start...

My take on where NOT to start...

Problem Management - Can't have it without Incident Management

Configuration Management - CMDB will be out of date in no time without Change Management.

Service Level Management - Can start certain aspects, but no baseline without Incident and Change Management to negotiate SLA's with the customer.

IT Service Continuity Management - Difficult and expensive, no quick wins, good to have the CMDB first... Don't get me wrong, it IS important, but not my suggested place to start.

Release Management - You preferably need Change Management first.

Available & Capacity management - Possible to start with, but no real quick wins and more difficult...the ITIL books really get theoretical on these processes.

These are only my views and every IT department will have to look at what’s best for them.



Acid-Alkaline Diet Simplified! - Achieve permanent weight loss, experience vibrant health, and reverse the aging process with this complete home study course.
The Ultimate Rotator Cuff Training Guide. - Physical therapist reveals how to fix rotator cuff pain and shoulder stiffness.


Article Index: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81


More Articles:


1. Working with Hearing Impaired Employees - Giving Them a Fair Go By Robin Henry
Hearing impaired people often encounter difficulty at work because their disability isn’t visible. I’d like to relate to you, briefly, the sorry saga of a young man who has recently been dragged through a performance management process, essentially brought about by misunderstanding, frustration on his behalf, and failure by an employer to make a ‘reasonable adjustment’ [Australian law includes the concept of reasonable adjustment which in effect means that employers are required to make reaso…
Multi Profit Websites

2. The Difference Between Managers and Leaders
It is often difficult to understand the difference between managers and leaders. Do managers lead? Do leaders manage? To understand how these two concepts are distinct yet different, here are 7 ways to understand them. 1. Course and Steering. The word 'leadership' comes from the Old English word 'lad' for a 'course'. A 'lode' is a vein that leads or guides to ore; a lodestone is a magnetic stone that guides; the lode-star is the name for the star that guides sailors, the Pole star. The word 'man…

3. Hire Winners: Ask the Right Questions By Marcia Zidle
How do you as a manager, supervisor or team leader hire winners? One very successful interviewing technique is behavioral interviewing---selecting the right person for the right job using a job-related rather than a gut feel approach. A job-related approach is asking for a behavioral example of skills and traits that are required for a position.A behavioral example is a description, by the job applicant, of a specific event that shows in detail how she did something or handled a problem or m…

4. Time to Quit the Rat Race? By John McKee
1. Most leaders die with their mouths open.I recently read an article in Fast Company magazine about the issue of leadership. In it, they quote Ronald Heifetz, the founder of Harvard's Center for Public Leadership, who made the above comment back in 1999. He followed it up by saying, "leaders must know how to listen - and the art of listening is more subtle than most people think it is. But first and just as important, leaders must want to listen."You'd think this is simply basic stuff, right?…