In terms of what needs to implemented first, this should all really depend on the requirements of the business you're supporting as well establishing where quick-wins can be used to re-affirm the commitment of ITIL adoption. It also depends on how you implement ITIL e.g. phased multi-process approach, single process approach or 'big-bang' (personally I wouldn't recommend this as ITIL is essentially an organisational Change programme - and organisations don't tend to like this, seeing ITIL as something which is imposed rather than adopted and adapted!).
Finally, there is also the question of what your vision of ITIL is and also the current assessment of the support Infrastructure - the demands of both will help 'guide the way'.
There are some slight variations to this rule in that certain processes become less effective without the presence of others e.g. Problem Management cannot be implemented without an Incident Management input. Configuration Management can be introduced but the CI's and CMDB become outdated without sufficient Change Management processes to reflect Changes within the Infrastructure.
Hi! i have been involved in BS15K implementation in my org. Came across your request and thought it ideal to share my thoughts...
According to my experience the best way to start ITIL/BS15K implementation is by "Defining your IT Servies". IT services will be form the basis of implementation of everything else. This effectively means that the first place to start is Service Level Management. Once this process is implemented you can then implement Configuration Mgmt (Can be done simulataneously too) and then proceed towards Incident, Problem, Change & Release Mgmt. Infact, lot of whitepapers suggest that IT Support is the right place to start with in ITIL implementation and i tend to agree on this.
Also, my personal suggestion is to go step-by-step and not to take the big-bang approach.
Hope this is useful.
The goal is to implement Service Management - not individual processes. This is a big mistake that most IT people make. It is recommended that all 10 (plus Service Desk/Security) be done at the same time.
The ITIL Book - Planning To Implement Service Management - page 15 first paragraph 2nd sentence states this directly. By implementing one process at a time (or several processes at a time) you end up doing rework down the road and missing on many benefits. There are dependencies across all processes with each other, although some may have more from others than most.
There should be a Service management Visioning effort done at the start - one of the outcomes is to determine which of the 10 processes you will spend more time going in depth with than others. This determination will be done along with and aligned to the business need. Many people make a second mistake of letting IT pick which processes they will prioritize.
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