ITIL Introduction in Stages: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
< | <itpmch><title>ITIL Introduction in Stages | IT Process Wiki</title> | ||
<meta name="keywords" content="itil stages, itil introduction" /> | |||
<meta name="description" content="ITIL Introduction in Stages. Rather than introducing the full set of ITIL recommendations at once, most organizations start with a ..." /> | |||
</itpmch> | |||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL Introduction in Stages|100px | Image:ITIL-Wiki-de-es.jpg|DE - ES - ITIL Introduction in Stages|100px | ||
| Line 16: | Line 19: | ||
<p> </p> | <p> </p> | ||
==Step One: Taking Care of Incidents and Problems== | |||
In order to realize this, an ITIL introduction frequently begins with the "[[Incident Management|Incident Management]]" process, supported by "[[Problem Management|Problem Management]]", to take care of deeper-running problems. If possible, "[[Service Asset and Configuration Management|Configuration Management]]" should be included, because reliable data on the IT infrastructure will significantly improve the effectiveness of Incident and Problem Management. | In order to realize this, an ITIL introduction frequently begins with the "[[Incident Management|Incident Management]]" process, supported by "[[Problem Management|Problem Management]]", to take care of deeper-running problems. If possible, "[[Service Asset and Configuration Management|Configuration Management]]" should be included, because reliable data on the IT infrastructure will significantly improve the effectiveness of Incident and Problem Management. | ||
| Line 22: | Line 25: | ||
<p> </p> | <p> </p> | ||
==Change and Release Management as a Second Step== | |||
The enterprise as a whole depends on an up-to-date, reliable and secure IT infrastructure in order to support its business processes. | The enterprise as a whole depends on an up-to-date, reliable and secure IT infrastructure in order to support its business processes. | ||
| Line 32: | Line 35: | ||
<p> </p> | <p> </p> | ||
==Third Step: Focus on the Client== | |||
In a third step, the conditions are created for agreeing and monitoring service levels. This will mainly require a "[[Service Level Management]]" process, but also "[[Capacity Management]]", "[[Availability Management]]" and "[[IT Service Continuity Management]]" to make sure that the relevant service level targets are actively managed. | In a third step, the conditions are created for agreeing and monitoring service levels. This will mainly require a "[[Service Level Management]]" process, but also "[[Capacity Management]]", "[[Availability Management]]" and "[[IT Service Continuity Management]]" to make sure that the relevant service level targets are actively managed. | ||
| Line 38: | Line 41: | ||
<p> </p> | <p> </p> | ||
==Modular ISO Certification== | |||
In the same way as ITIL processes can be introduced as subsets, a certification according to [[ISO 20000]] is also possible for parts of the entire scope. | In the same way as ITIL processes can be introduced as subsets, a certification according to [[ISO 20000]] is also possible for parts of the entire scope. | ||
| Line 47: | Line 50: | ||
<p> </p> | <p> </p> | ||
<html><a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL implementation]][[Category:ITIL process]] | [[Category:ITIL implementation]][[Category:ITIL process]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 14:30, 5 August 2013
Rather than introducing the full set of ITIL recommendations at once, most organizations start with a subset of ITIL processes.
The prevailing motivation for the introduction of ITIL is often a desire to be able to deal with Incidents more professionally. This requires the availability of a central point-of-contact for the user (known in ITIL as the “Service Desk”), where calls are received and the necessary steps for the correction of the error taken.
Step One: Taking Care of Incidents and Problems
In order to realize this, an ITIL introduction frequently begins with the "Incident Management" process, supported by "Problem Management", to take care of deeper-running problems. If possible, "Configuration Management" should be included, because reliable data on the IT infrastructure will significantly improve the effectiveness of Incident and Problem Management.
Change and Release Management as a Second Step
The enterprise as a whole depends on an up-to-date, reliable and secure IT infrastructure in order to support its business processes.
The effects caused by unauthorized or uncoordinated changes to this infrastructure are often not only undesired, but can also lead to business disruptions.
For this reason it is of particular importance to many businesses, that changes to the IT infrastructure only take place in a coordinated way. The second phase of an ITIL introduction therefore often seeks to establish the "Change Management" and "Release Management" processes.
Third Step: Focus on the Client
In a third step, the conditions are created for agreeing and monitoring service levels. This will mainly require a "Service Level Management" process, but also "Capacity Management", "Availability Management" and "IT Service Continuity Management" to make sure that the relevant service level targets are actively managed.
Modular ISO Certification
In the same way as ITIL processes can be introduced as subsets, a certification according to ISO 20000 is also possible for parts of the entire scope.
Back to: → ITIL Implementation - ITIL Implementation in 10 Steps
