For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
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.
Posted: Thu Jun 16, 2005 1:49 am Post subject: ITIL Starting Points...
Greetings!
Does anybody have an example of the worlds smallest ITIL implementation? We need examples of good places to start adoption. A simple ITIL mini implementation could help here. There would be so many more companies using ITIL, if they had a roadmap. So to start the roadmap maybe we can throw in some ideas here.
Posted: Fri Jun 17, 2005 7:07 pm Post subject: If you are looking to implement an ITIL aligned Service Desk
Then you are best looking at just Incident, Problem and Change processes. A lot will depend on how much you already know about your infrastructure and what tools you have avaiable.
ITIL is a best practice only so actually 'implemnting' ITIL can be considered as a change of attitude and philosophy and Incident, Problem and Change can be performed as 'mini ' processes.
I have worked in smaller environments where the reactive side of Incident and Problem Management have been combined, with Problem Management only coming in to play for High Priority Incidents.
This can be done in organisations with as little as two people responsible for the whole infrastructure, as long as they have good links with the business and involve the business in the processes.
Joined: Mar 12, 2005 Posts: 255 Location: Melbourne, Australia
Posted: Sun Jun 19, 2005 3:59 am Post subject:
I was recently at a seminar where a CIO presented a talk on a 'successful' 12 week ITIL implementation.
Believe me every one ear's were well and truely pricked up when he made that claim.
The outcome by which he judged the success? That the board of directors had been convinced that the IT spend was not a 'cost' but a value provider.
The key trick? He instructed everyone involved that they were to define no more than twelve service that covered the entire IT operation, and no more than 30 sub services in total.
Which I though was very interesting... and well worth thinking about for anyone who is looking to successfully scale down ITIL.
Thanks Blackbeard and rjp for the comments. This is exactly the kind of thing I'm looking for.
In summary, two possible ways to start are...
- Look at Incident, Problem and Change processes.
This would seem to be an IT-centric perspective that most IT professionals would be familiar with. Many companies already have these types of processes in place (call center, help desk, 2nd level support, etc.), but, probably don't give them the full treatment ITIL put forth as best practices.
- make IT a value provider by defining no more than twelve service that covered the entire IT operation, and no more than 30 sub services in total
This approach attempts to limit the scope to a manageable set of services. Kind of a keep it simple approach (or maybe simplER).
Does anybody else have other starting points for ITIL.
Joined: Jan 16, 2005 Posts: 37 Location: New Zealand
Posted: Mon Jul 18, 2005 9:00 am Post subject:
I agree with the other posters but if there was a single process of those three that differentiates simple ITIL from non-ITIL would be Problem Management. Most organisations, as you say, already have some kind of Service Desk in place and by default something resembling Incident Management and often Change Management. But Problem Management is when you start to see the difference - it's when you start thinking proactively, i.e. "what do I need to do to try and minimise these faults occurring in the first place"...
Joined: May 27, 2005 Posts: 79 Location: Madrid-Spain
Posted: Mon Jul 18, 2005 6:47 pm Post subject:
I fully agree with blamblam for me what makes a great difference between ITIL and non-ITIL , is a correct Problem management.
Some organisations have which they call as "generic incidents" or "primary incidents" but really they are not dealing with Problem Management proactively.
For e.g. it is quite common to have this categorisation of "primary incidents" when they found a root cause for a sort of incidents, and to establish relationships among this "primary incident" and the other incidents caused by this, but many times is exactly the same people who deals with incidents and problems and also there is a lack of communication between management tools like patrol agents for e.g. and incident or problem management so there is no a proactive detection of problems and incidents before they are reported from users.
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