Tags |
|
|
Links |
|
|
Other Added - Which ITIL Process Should We Implement First?
Delegation -- one of the critical determining factors for everyone who wants to be an effective leader or manager. And for those of us control freaks, lack of delegating skill can be a real show stopper.Because the harder you try to hold on to things, the faster they can get away from you, and if you want to extend your reach beyond your ability to do everything at onc
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
Your business card can be your most powerful advertising and marketing tool. Get your card into the hands of people who can do business with you and profit is sure to follow.The little card is often taken for granted and not given the thought it deserves. Since it plays such a big role in the impression you make, it, and you, should not make mistakes.Here are some common busines
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 p
Autologica presents part four in a series of articles that address some of the common problems and situations that arise in family-owned businesses. The articles are based on an interview between Al McClymont, CEO of Autologica Dealer Management Systems, and J.C. Aimetta, an expert and coach who specializes in family-owned businesses and who has ample experience consulting for this type of co
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
(For full, ironic effect, the title of this article should actually be sung to the tune that begins, “Have yourself a merry, little Christmas...”)****************************************************************The Oracle of Delphi is credited with having made the famous admonition to all seekers of wisdom, “Know thyself!”It’s still great advice. Of course, when it comes t
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
I can hear the jokes already and most of them are not politically correct. Let me throw out a word that we often don't attach to work and yet I think it is a word of redemption, of contribution, of achievement, of community, and ultimately, of legacy.Here it is: LOVE.Kahil Gibran proclaimed, "Work is love made visible". I would further clarify his position by insisting that a j
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
A job search can be hard and sometimes frustrating. In case you are considering changing your job you should consider using an online search. This will help you expand your horizons and your search for your next job can become world wide and not restricted to any one area.1. If you are keen in continuing in your present line of work with say a better location or opportunities. Then exp
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.
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.otheradded.com/article/23830/otheradded-Which-ITIL-Process-Should-We-Implement-First.html">Which ITIL Process Should We Implement First?</a>
BB link (for phorums):
[url=http://www.otheradded.com/article/23830/otheradded-Which-ITIL-Process-Should-We-Implement-First.html]Which ITIL Process Should We Implement First?[/url]
Related Articles:
Some of the Many Uses of Bulletproof and Bullet Resistant Glass
Service Buyers and Product Buyers Don't Seek the Same Yellow Page Information
Bookmark it:
|