ITIL Introduction in Stages: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| 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| | Image:ITIL-Wiki-de-es.jpg|right|DE - ES - ITIL Introduction in Stages|163px | ||
rect 0 | rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/Schrittweise_ITIL-Einf%C3%BChrung diese Seite auf Deutsch] | ||
rect | rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/Introducci%C3%B3n_de_ITIL_por_etapas esta página en español] | ||
desc none | desc none | ||
</imagemap> | </imagemap> | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
Rather than introducing the full set of ITIL recommendations at once, most organizations start with a subset of ITIL processes. | Rather than introducing the full set of ITIL recommendations at once, most organizations start with a subset of ITIL processes. | ||
| Line 14: | Line 15: | ||
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. | 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 1: 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. | ||
==Step 2: Change and Release Management== | |||
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 30: | Line 27: | ||
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 and Deployment Management|Release Management]]" processes. | 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 and Deployment Management|Release Management]]" processes. | ||
==Step 3: 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 33: | ||
<p> </p> | <p> </p> | ||
''' Back to: ''' → '''[[ITIL Implementation|ITIL Implementation - ITIL Implementation in 10 Steps]]''' | |||
<html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | |||
<p> </p> | <p> </p> | ||
<small> | |||
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Introduction_in_Stages#Step_1:_Taking_Care_of_Incidents_and_Problems" > <span itemprop="name">Step 1: Taking Care of Incidents and Problems</span></a><meta itemprop="position" content="1" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Introduction_in_Stages#Step_2:_Change_and_Release_Management" > <span itemprop="name">Step 2: Change and Release Management</span></a><meta itemprop="position" content="2" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Introduction_in_Stages#Step_3:_Focus_on_the_Client" > <span itemprop="name">Step 3: Focus on the Client</span></a><meta itemprop="position" content="3" /></span> | |||
</span> | |||
</small></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]] | ||
<!-- --- --> | <!-- --- --> | ||
Latest revision as of 11:49, 30 March 2019
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 1: 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.
Step 2: Change and Release Management
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.
Step 3: 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.
Back to: → ITIL Implementation - ITIL Implementation in 10 Steps
By: Stefan Kempter 
, IT Process Maps.
Step 1: Taking Care of Incidents and Problems › Step 2: Change and Release Management › Step 3: Focus on the Client
