Tags |
|
|
Links |
|
|
Member You - Which ITIL Process Should We Implement First?
In the aeration basin of a typical wastewater treatment plant there are both organic and inorganic matter that can impair the function of fine bubble diffusers. Eventually this requires either additional energy to overcome high membrane headloss, or reducing the oxygen mass transfer to the process.The rate and type of fouling depends on whether the plant is treating industrial or munic
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
Web 2.0 is anything but in the shadows these days. Everyday we are hearing more and more about Facebook, YouTube, and MySpace in traditional media. Sources like The Wall Street Journal and New York Times are keeping up with these colossal new companies that built themselves up in a matter of months and are now looking to be acquired for over a billion dollars.There in lies the problem,
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
IntroductionLast week, I was in Rajasthan (One of the largest state in India), traveling from Jaipur to Jodhpur to Udaipur to Bikaner to Kota. It was not a fun trip but I was adding few more head counts on the roll of the company I am working with. I was in Rajasthan for 8 days, 1800+ people walked-in for interviews; 750 actually interviewed and we extended the offer to 107 people. Whe
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
In order to sell more products and service, you need master customers' mind. Put youself into customers' shoes and think what customers want. You will make more profit by master these skills. 1. Use the word "fast" in your ad. People want fast results, fast delivery, fast ordering, etc. Nowadays, we usually value our time more than our money. 2. Use the word "guaranteed" in y
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
It's amazing how much misinformation there is about business plans. One of the biggest questions people have is about how long and detailed business plans should be. Should they be like big thick books, or are these things generally pretty brief? Truth is, it depends. It depends on how big the company is and how complicated it is. A business plan of a start up busi
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
So you finally managed to get that franchise that you have been dreaming of. You are finally one step closer to having that financial success you have been dreaming of all your life. Take heed however, having that franchise formula does not necessarily ensure that it will be all smooth sailing from this point on. In fact you must be ready to pull your belt one notch tighter and burn the mi
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.
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.memberyou.net/article/23830/memberyou-Which-ITIL-Process-Should-We-Implement-First.html">Which ITIL Process Should We Implement First?</a>
BB link (for phorums):
[url=http://www.memberyou.net/article/23830/memberyou-Which-ITIL-Process-Should-We-Implement-First.html]Which ITIL Process Should We Implement First?[/url]
Related Articles:
Medical Billing - GP0 Record Fields 1 Through 7
Career Vision: Moving Your Life From Stress To Balance
Manage Your Inventory by Using Inventory Management Software
Bookmark it:
|