ITIL Service Transition: Difference between revisions

From IT Process Wiki
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
<meta property="og:image:width" content="558" />
<meta property="og:image:width" content="558" />
<meta property="og:image:height" content="888" />
<meta property="og:image:height" content="888" />
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@itprocessmaps">
<meta name="twitter:creator" content="@itprocessmaps">
<meta name="twitter:title" content="ITIL Service Transition | IT Process Wiki">
<meta name="twitter:description" content="The objective of ITIL Service Transition is to build and deploy IT services. This lifecycle stage also makes sure that changes to services and service management processes are carried out in a coordinated way.">
<meta name="twitter:image" content="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg">
<meta name="twitter:image:alt" content="Overview of the processes in ITIL Service Transition: Change Management, Change Evaluation, Project Management (Transition Planning and Support), Application Development, Release and Deployment Management, Service Validation and Testing, Service Asset and Configuration Management and Knowledge Management.">
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-share.jpg|right|share this page|141px
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Service Transition|163px
rect 55 0 99 36 [https://www.linkedin.com/shareArticle?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FITIL_Service_Transition&hl=en_US&source=IT%20Process%20Wiki share this page on LinkedIn]
rect 97 0 141 36 [https://twitter.com/intent/tweet?url=https%3A%2F%2Fwiki.en.it-processmaps.com%2Findex.php%2FITIL_Service_Transition&text=%23ITILwiki%20%7C%20ITIL%20Service%20Transition%20-%20Process%20description%0A%E2%96%BA&lang=en&via=itprocessmaps share this page on Twitter]
desc none
</imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Transition|163px
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Transition_-_Serviceüberführung diese Seite auf Deutsch]
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Transition_-_Serviceüberführung diese Seite auf Deutsch]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Transici%C3%B3n_del_Servicio esta página en español]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Transici%C3%B3n_del_Servicio esta página en español]
Line 47: Line 34:
Service Transition builds and deploys new or modified services.
Service Transition builds and deploys new or modified services.


<imagemap>
[[Image:Overview_service_transition_itilv3.jpg|right|thumb|459px|alt=ITIL Service Transition|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_service_transition_itilv3.jpg|Fig. 1: [[#Processes:_ITIL_Service_Transition|ITIL Service Transition]]]]
Image:Overview_service_transition_itilv3.jpg||right|Fig. 1: [[#Processes:_ITIL_Service_Transition|ITIL Service Transition]]|459px|thumb|alt=ITIL Service Transition
rect 220 124 342 210 [[Project Management - Transition Planning and Support|Project Management (Transition Planning and Support) - Service Transition]]
rect 71 277 194 363 [[Change Management|Change Management - Service Transition]]
rect 247 277 371 361 [[ITIL Change Evaluation|Change Evaluation - Service Transition]]
rect 152 411 273 494 [[Release and Deployment Management|Release and Deployment Management - Service Transition]]
rect 352 411 473 495 [[Application Development and Customization|Application Development - Service Transition]]
rect 267 545 389 631 [[Service Validation and Testing|Service Validation and Testing - Service Transition]]
rect 221 664 341 748 [[Service Asset and Configuration Management|Service Asset and Configuration Management - Service Transition]]
rect 221 783 342 869 [[Knowledge Management|Knowledge Management - Service Transition]]
desc bottom-left
</imagemap>


<html><div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition#Processes:_ITIL_Service_Transition" itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<html><div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition#Processes:_ITIL_Service_Transition" itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
Line 64: Line 40:
<p><span itemprop="name" content="Service Transition main processes">The ITIL service lifecycle stage of <strong class="selflink">Service Transition</strong> (<a href="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" title="ITIL Service Transition">see fig. 1</a>) includes the following <strong>main processes</strong></span></span>:
<p><span itemprop="name" content="Service Transition main processes">The ITIL service lifecycle stage of <strong class="selflink">Service Transition</strong> (<a href="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" title="ITIL Service Transition">see fig. 1</a>) includes the following <strong>main processes</strong></span></span>:
</p>
</p>
<p>&#160;</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Change_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Change_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="1" />
<meta itemprop="position" content="1" />
Line 71: Line 45:
</dt><dd itemprop="description">Process Objective: To control the lifecycle of all Changes. The primary objective of Change Management is to enable beneficial Changes to be made, with minimum disruption to IT services.
</dt><dd itemprop="description">Process Objective: To control the lifecycle of all Changes. The primary objective of Change Management is to enable beneficial Changes to be made, with minimum disruption to IT services.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="2" />
<meta itemprop="position" content="2" />
Line 79: Line 50:
</dt><dd itemprop="description">Process Objective: To assess major Changes, like the introduction of a new service or a substantial change to an existing service, before those Changes are allowed to proceed to the next phase in their lifecycle.
</dt><dd itemprop="description">Process Objective: To assess major Changes, like the introduction of a new service or a substantial change to an existing service, before those Changes are allowed to proceed to the next phase in their lifecycle.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="3" />
<meta itemprop="position" content="3" />
Line 87: Line 55:
</dt><dd itemprop="description">Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates.
</dt><dd itemprop="description">Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Application_Development_and_Customization" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Application_Development_and_Customization" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="4" />
<meta itemprop="position" content="4" />
Line 95: Line 60:
</dt><dd itemprop="description">Process Objective: To make available applications and systems which provide the required functionality for IT services. This process includes the development and maintenance of custom applications as well as the customization of products from software vendors.
</dt><dd itemprop="description">Process Objective: To make available applications and systems which provide the required functionality for IT services. This process includes the development and maintenance of custom applications as well as the customization of products from software vendors.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="5" />
<meta itemprop="position" content="5" />
Line 103: Line 65:
</dt><dd itemprop="description">Process Objective: To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
</dt><dd itemprop="description">Process Objective: To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="6" />
<meta itemprop="position" content="6" />
Line 111: Line 70:
</dt><dd itemprop="description">Process Objective: To ensure that deployed Releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
</dt><dd itemprop="description">Process Objective: To ensure that deployed Releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="7" />
<meta itemprop="position" content="7" />
Line 119: Line 75:
</dt><dd itemprop="description">Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships.
</dt><dd itemprop="description">Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships.
</dd></dl></div>
</dd></dl></div>
<p><br />
</p>
<div itemid="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<div itemid="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management" itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem" >
<meta itemprop="position" content="8" />
<meta itemprop="position" content="8" />
Line 128: Line 81:
</dd></dl></div>
</dd></dl></div>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>
 
==ITIL 4 Service Transition==
 
The [[#Processes:_ITIL_Service_Transition|Service Transition processes described here]] ([[Media:Overview_service_transition_itilv3.jpg|fig. 1]]) follow the specifications of ITIL V3, where Service Transition is the third stage in the Service Lifecycle.
 
ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the [[ITIL_4#Four_dimensions_model|Four Dimensions Model]] and the [[ITIL_4#Service_value_system|Service Value System (SVS)]].
 
Instead of processes, [[ITIL_4#ITIL_4_management_practices|ITIL 4 describes 34 'practices']], and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices. For example, ITIL V4 refers to Change Management and Configuration Management as practices (Change Management has been renamed to "Change Enablement").
 
The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Transition processes.
 
<html>Since the processes specified in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to define their Service Transition processes can still use the processes specified in ITIL V3 as templates.</p>
 
<p style="border: 8px solid #cef6e3; padding: 0.5em 1em;"><i><u>Note</u>:</i><br /> In our <i>YaSM Service Management Wiki</i> we describe a <a class="external" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes" title="Service management processes">leaner set of 19 service management processes</a> that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".<br /><br /> The YaSM service management model includes a <a class="external" href="https://yasm.com/wiki/en/index.php/LP3:_Build_new_or_changed_services" title="YaSM service implementation process">Service Transition / Service Implementation process</a> that is a good starting point for organizations that wish to adopt ITIL 4.</html>


==<span id="Additional_Information_on_Service_Transition">KPIs | Templates | Roles</span>==
==<span id="Additional_Information_on_Service_Transition">KPIs | Templates | Roles</span>==
Line 135: Line 101:
* [[ITIL-Checklists#ITIL Service Transition Templates|Service Transition templates and checklists]]
* [[ITIL-Checklists#ITIL Service Transition Templates|Service Transition templates and checklists]]
* [[ITIL Roles#ITIL roles and boards - Service Transition|ITIL roles within Service Transition]]
* [[ITIL Roles#ITIL roles and boards - Service Transition|ITIL roles within Service Transition]]
<p>&nbsp;</p>


==Downloads==
==Downloads==


{|
[[Image:Service-transition.jpg|thumb|320px|right|none|alt=Service Transition ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Service-transition.jpg|The ITIL discipline Service Transition at a glance]]
|style="vertical-align:top" |
Use the following links to open the process overview of Service Transition showing the most important interfaces:
Use the following links to open the process overview of Service Transition showing the most important interfaces:
* [[Media:Service-transition.jpg|Service Transition (.JPG)]]
* [[Media:Service-transition.jpg|Service Transition (.JPG)]]
* [https://wiki.en.it-processmaps.com/images/pdf/service-transition-itil-v3.pdf Service Transition (.PDF)]''
* [https://wiki.en.it-processmaps.com/images/pdf/service-transition-itil-v3.pdf Service Transition (.PDF)]
|style="vertical-align:top" |
<br style="clear:both;"/>
[[Image:Service-transition.jpg|thumb|175px|left|none|alt=Service Transition ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Service-transition.jpg|The ITIL discipline Service Transition at a glance]]
|-
|}
 
<p>&nbsp;</p>


==Notes==
==Notes==


<html>By:&#160;&#160;Stefan Kempter&#160;<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>
<html>By:&#160;&#160;Stefan Kempter&#160;<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>&nbsp;</p>
<p>&nbsp;</p>


<p><small>
<p><small>
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<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_Service_Transition#ITIL_4_Service_Transition">
<span itemprop="name">ITIL 4 Service Transition</span></a>
<meta itemprop="position" content="1"></span>  ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Change_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Change_Management">
<span itemprop="name">Change Management</span></a>
<span itemprop="name">Change Management</span></a>
<meta itemprop="position" content="1"></span>  › [...] ›  
<meta itemprop="position" content="2"></span>  › [...] ›  
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management">
<span itemprop="name">Release Mgmt.</span></a>
<span itemprop="name">Release Mgmt.</span></a>
<meta itemprop="position" content="2"></span> ›
<meta itemprop="position" content="3"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing">
<span itemprop="name">Service Validation</span></a>
<span itemprop="name">Service Validation</span></a>
<meta itemprop="position" content="3"></span> ›
<meta itemprop="position" content="4"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management">
<span itemprop="name">Configuration Mgmt.</span></a>
<span itemprop="name">Configuration Mgmt.</span></a>
<meta itemprop="position" content="4"></span> ›
<meta itemprop="position" content="5"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management">
<span itemprop="name">Knowledge Mgmt.</span></a>
<span itemprop="name">Knowledge Mgmt.</span></a>
<meta itemprop="position" content="5"></span>
<meta itemprop="position" content="6"></span>
</span>
</span>
</small></p>
</small></p>
Line 199: Line 159:
   <meta itemprop="keywords" content="Service Transition" />
   <meta itemprop="keywords" content="Service Transition" />
   </span>
   </span>
  <meta itemprop="mentions" content="https://yasm.com/wiki/en/index.php/LP3:_Build_new_or_changed_services" />
   <meta itemprop="inLanguage" content="en" />
   <meta itemprop="inLanguage" content="en" />
   <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Transition_-_Service%C3%BCberf%C3%BChrung" />
   <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/ITIL_Service_Transition_-_Service%C3%BCberf%C3%BChrung" />

Latest revision as of 12:49, 31 December 2023

DE - ES - Service Transitiondiese Seite auf Deutschesta página en español
DE - ES - Service Transition


Objective: The objective of ITIL Service Transition is to build and deploy IT services. The Service Transition lifecycle stage also makes sure that changes to services and service management processes are carried out in a coordinated way.

Part of: IT Service Management | ITIL processes

 

Processes: ITIL Service Transition

Service Transition builds and deploys new or modified services.

ITIL Service Transition
Fig. 1: ITIL Service Transition

The ITIL service lifecycle stage of Service Transition (see fig. 1) includes the following main processes:

Process Objective: To control the lifecycle of all Changes. The primary objective of Change Management is to enable beneficial Changes to be made, with minimum disruption to IT services.
Process Objective: To assess major Changes, like the introduction of a new service or a substantial change to an existing service, before those Changes are allowed to proceed to the next phase in their lifecycle.
Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates.
Process Objective: To make available applications and systems which provide the required functionality for IT services. This process includes the development and maintenance of custom applications as well as the customization of products from software vendors.
Process Objective: To plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
Process Objective: To ensure that deployed Releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships.
Process Objective: To gather, analyze, store and share knowledge and information within an organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge.

ITIL 4 Service Transition

The Service Transition processes described here (fig. 1) follow the specifications of ITIL V3, where Service Transition is the third stage in the Service Lifecycle.

ITIL V4 has moved from the Service Lifecycle concept to a more holistic approach that includes key concepts, the Four Dimensions Model and the Service Value System (SVS).

Instead of processes, ITIL 4 describes 34 'practices', and many of the 26 processes specified in ITIL V3 can be found in ITIL 4 as practices. For example, ITIL V4 refers to Change Management and Configuration Management as practices (Change Management has been renamed to "Change Enablement").

The shift from processes to practices means ITIL V4 is no longer prescriptive about processes and gives organizations more freedom to define tailor-made Service Transition processes.

Since the processes specified in ITIL V3 have not been invalidated with the introduction of ITIL V4, organizations that need to define their Service Transition processes can still use the processes specified in ITIL V3 as templates.

Note:
In our YaSM Service Management Wiki we describe a leaner set of 19 service management processes that are more in tune with ITIL 4 and its focus on simplicity and "just enough process".

The YaSM service management model includes a Service Transition / Service Implementation process that is a good starting point for organizations that wish to adopt ITIL 4.

KPIs | Templates | Roles

Downloads

Service Transition ITIL
The ITIL discipline Service Transition at a glance

Use the following links to open the process overview of Service Transition showing the most important interfaces:


Notes

By:  Stefan Kempter , IT Process Maps.

 

ITIL 4 Service Transition  › Change Management  › [...] › Release Mgmt.  › Service Validation  › Configuration Mgmt.  › Knowledge Mgmt.

Retrieved from "https://wiki.en.it-processmaps.com/index.php?title=ITIL_Service_Transition&oldid=9588"