ITIL Service Transition: Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{|
<itpmch><title>ITIL Service Transition | IT Process Wiki</title>
! align="right" width="80%"|
<meta name="keywords" content="service transition, itil service transition, itil transition, itil v3 transition, itil v3 service transition" />
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/ITIL_V3_Service_Transition_-_Serviceüberführung diese Seite auf Deutsch]
<meta name="description" content="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 V3 processes." />
|}
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition" />
<meta property="og:title" content="ITIL Service Transition | IT Process Wiki" />
<meta property="og:description" content="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 V3 processes." />
<meta property="og:site_name" content="IT Process Wiki - the ITIL&#174; Wiki">
<meta property="og:type" content="article" />
<meta property="article:publisher" content="https://www.facebook.com/itprocessmaps" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" />
<meta property="og:image:width" content="558" />
<meta property="og:image:height" content="888" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|right|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 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Transici%C3%B3n_del_Servicio esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>


'''ITIL Version''': ITIL Version 3 (ITIL V3)
'''<span id="ITIL_Service_Transition_definition">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description">The objective of <i>ITIL Service Transition</i> 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.</span></p>
<p><b>Part of</b>: <a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_V3" title="ITIL Processes">IT Service Management | ITIL processes</a></html>


'''Process Objective''': To build and deploy IT services. It also makes sure that changes to services and [[ITIL Processes#ITIL Processes according to ITIL Version 3 (ITIL V3)|Service Management processes]] are carried out in a coordinated way.
<p>&nbsp;</p>


'''Part of''': [[ITIL Processes#ITIL Processes according to ITIL Version 3 (ITIL V3)|IT Service Management]]
__TOC__


==Processes: ITIL Service Transition==


==Sub-Processes of Service Transition (ITIL V3)==
Service Transition builds and deploys new or modified services.


[[Image:Overview_service_transition_itilv3.jpg|frame|left|Overview of Service Transition (ITIL V3)]]
[[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]]]]


<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 -->
<meta itemprop="itemListOrder" content="Ascending" />
<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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Change_Management" title="Change Management" itemprop="itemListElement">Change Management</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation" title="ITIL Change Evaluation" itemprop="itemListElement">Change Evaluation</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support" title="Project Management - Transition Planning and Support" itemprop="itemListElement">Project Management (Transition Planning and Support)</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Application_Development_and_Customization" title="Application Development and Customization" itemprop="itemListElement">Application Development</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management" title="Release and Deployment Management" itemprop="itemListElement">Release and Deployment Management</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing" title="Service Validation and Testing" itemprop="itemListElement">Service Validation and Testing</a>
</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>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management" title="Service Asset and Configuration Management" itemprop="itemListElement">Service Asset and Configuration Management</a>
</dt><dd itemprop="description">Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships.
</dd></dl></div>
<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" />
<dl><dt itemprop="name"><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management" title="Knowledge Management" itemprop="itemListElement">Knowledge Management</a>
</dt><dd itemprop="description">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.
</dd></dl></div>
</div><!-- end of schema.org/ItemList --><p></html>


;[[Change Management]]
==ITIL 4 Service Transition==
: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.


;[[Project Management - Transition Planning and Support|Project Management (Transition Planning and Support)]]
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.
:Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates.


;[[Release and Deployment Management]]
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)]].
: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.


;[[Service Validation and Testing]]
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").
: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.


;[[Application Development and Customization]]
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.
: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.


;[[Service Asset and Configuration Management]]
<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>
:Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships. This process is also responsible for tracking and reporting the value and ownership of financial assets throughout their Lifecycle.


;[[Knowledge Management]]
<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>
: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.
 
==<span id="Additional_Information_on_Service_Transition">KPIs | Templates | Roles</span>==
 
* [[ITIL KPIs Service Transition|KPIs for Service Transition]]
* [[ITIL-Checklists#ITIL Service Transition Templates|Service Transition templates and checklists]]
* [[ITIL Roles#ITIL roles and boards - Service Transition|ITIL roles within Service Transition]]
 
==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]]
Use the following links to open the process overview of Service Transition showing the most important interfaces:
* [[Media:Service-transition.jpg|Service Transition (.JPG)]]
* [https://wiki.en.it-processmaps.com/images/pdf/service-transition-itil-v3.pdf Service Transition (.PDF)]
<br style="clear:both;"/>
 
==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>
<p>&nbsp;</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_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">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Change_Management">
<span itemprop="name">Change 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/Release_and_Deployment_Management">
<span itemprop="name">Release Mgmt.</span></a>
<meta itemprop="position" content="3"></span> ›
<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">
<span itemprop="name">Service Validation</span></a>
<meta itemprop="position" content="4"></span> ›
<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">
<span itemprop="name">Configuration Mgmt.</span></a>
<meta itemprop="position" content="5"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Knowledge_Management">
<span itemprop="name">Knowledge Mgmt.</span></a>
<meta itemprop="position" content="6"></span>
</span>
</small></p>
 
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description">
  <meta itemprop="name Headline" content="ITIL Service Transition" />
  <meta itemprop="alternativeHeadline" content="Service Transition" />
  <link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition" />
  <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" />
  <span itemid="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="caption" content="ITIL Service Transition main processes.">
  <meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/0/0c/Overview_service_transition_itilv3.jpg" />
  <meta itemprop="width" content="558" />
  <meta itemprop="height" content="888" />
  <meta itemprop="representativeOfPage" content="true"/>
  <meta itemprop="dateCreated" content="2011-11-18" />
  <meta itemprop="dateModified" content="2019-09-21" />
  <meta itemprop="keywords" content="Service Transition" />
  </span>
  <meta itemprop="mentions" content="https://yasm.com/wiki/en/index.php/LP3:_Build_new_or_changed_services" />
  <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.es.it-processmaps.com/index.php/ITIL_Transici%C3%B3n_del_Servicio" />
  <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_V3" />
  <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" />
  <meta itemprop="author" content="Stefan Kempter" />
  <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
</span><p></html>
 
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL stage]][[Category:ITIL process|3]][[Category:Service Transition|!]]
<!-- --- -->

Latest revision as of 11: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"