ITIL Service Transition: Difference between revisions
From IT Process Wiki
mNo edit summary |
|||
| Line 1: | Line 1: | ||
<seo metakeywords="service transition, itil service transition, itil transition, itil v3 transition, itil v3 service transition" metadescription=" | <seo metakeywords="service transition, itil service transition, itil transition, itil v3 transition, itil v3 service transition" metadescription="ITIL Service Transition: Definition - Processes - Additional information on Service Transition: ITIL Roles, Checklists, KPIs..." /> | ||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Transition|100px | Image:ITIL-Wiki-de-es.jpg|DE - ES - Service Transition|100px | ||
| Line 8: | Line 8: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
== ITIL Service Transition | == ITIL Service Transition == | ||
''' | The objective of ''ITIL Service Transition'' is to build and deploy IT services. Service Transition also makes sure that changes to services and Service Management processes are carried out in a coordinated way. | ||
'''Part of''': [[ITIL Processes#ITIL Processes according to ITIL Version 3 (ITIL V3)|IT Service Management]] | '''Part of''': [[ITIL Processes#ITIL Processes according to ITIL Version 3 (ITIL V3)|IT Service Management]] | ||
<p> </p> | |||
== Processes | == Processes: ITIL Service Transition == | ||
<imagemap> | <imagemap> | ||
Image:Overview_service_transition_itilv3.jpg||left|ITIL Service Transition - Click on a process for more details| | Image:Overview_service_transition_itilv3.jpg||left|ITIL Service Transition - Click on a process for more details|459px|thumb|alt=ITIL Service Transition | ||
rect | rect 180 102 281 173 [[Project Management - Transition Planning and Support|Project Management (Transition Planning and Support) - Service Transition]] | ||
rect | rect 75 210 173 281 [[Change Management|Change Management - Service Transition]] | ||
rect | rect 282 211 382 279 [[Service Validation and Testing|Service Validation and Testing - Service Transition]] | ||
rect | rect 74 316 175 385 [[Release and Deployment Management|Release and Deployment Management - Service Transition]] | ||
rect | rect 256 316 357 386 [[Application Development and Customization|Application Development and Customization - Service Transition]] | ||
rect | rect 179 440 280 510 [[Service Asset and Configuration Management|Service Asset and Configuration Management - Service Transition]] | ||
rect | rect 180 542 280 613 [[Knowledge Management|Knowledge Management - Service Transition]] | ||
desc bottom-left | desc bottom-left | ||
</imagemap> | </imagemap> | ||
The following processes are part of the ITIL | The following processes are part of the ITIL discipline [[ITIL V3 Service Transition|Service Transition]]: | ||
<p> </p> | |||
;[[Change Management]] | ;[[Change Management]] | ||
: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 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. | ||
;[[ITIL Change Evaluation|Change Evaluation]] | |||
: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. | |||
;[[Project Management - Transition Planning and Support|Project Management (Transition Planning and Support)]] | ;[[Project Management - Transition Planning and Support|Project Management (Transition Planning and Support)]] | ||
:Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates. | :Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates. | ||
;[[Application Development and Customization]] | |||
: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. | |||
;[[Release and Deployment Management]] | ;[[Release and Deployment Management]] | ||
| Line 43: | Line 51: | ||
;[[Service Validation and Testing]] | ;[[Service Validation and Testing]] | ||
: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 ensure that deployed Releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service. | ||
;[[Service Asset and Configuration Management]] | ;[[Service Asset and Configuration Management]] | ||
| Line 51: | Line 56: | ||
;[[Knowledge Management]] | ;[[Knowledge Management]] | ||
:Process Objective: To gather, analyze, store and share knowledge and information within | :Process Objective: To gather, analyze, store and share knowledge and information within the organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge. | ||
<p> </p> | |||
== | == Additional Information on Service Transition == | ||
* [[ITIL KPIs Service Transition|KPIs for Service Transition]] | |||
* [[ITIL-Checklists#Checklists ITIL V3 Service Transition|Checklists for Service Transition]] | |||
* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|ITIL Roles within Service Transition]] | |||
<p> </p> | |||
== Downloads == | |||
== | ==== Overview Service Transition - Downloads ==== | ||
{| | |||
| valign="top" | | |||
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)]'' | |||
| valign="top" | | |||
[[Image:Service-transition.jpg|thumb|175px|left|none|alt=Service Transition ITIL|The ITIL discipline Service Transition at a glance]] | |||
|- | |||
|} | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL | [[Category:ITIL V3]][[Category:ITIL stage]][[Category:ITIL process|3]][[Category:Service Transition|!]] | ||
<!-- --- --> | <!-- --- --> | ||
Revision as of 18:29, 23 October 2011
<seo metakeywords="service transition, itil service transition, itil transition, itil v3 transition, itil v3 service transition" metadescription="ITIL Service Transition: Definition - Processes - Additional information on Service Transition: ITIL Roles, Checklists, KPIs..." />
ITIL Service Transition
The objective of ITIL Service Transition is to build and deploy IT services. Service Transition also makes sure that changes to services and Service Management processes are carried out in a coordinated way.
Part of: IT Service Management
Processes: ITIL Service Transition
The following processes are part of the ITIL discipline Service Transition:
- Change Management
- 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.
- Change Evaluation
- 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.
- Project Management (Transition Planning and Support)
- Process Objective: To plan and coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates.
- Application Development and Customization
- 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.
- Release and Deployment Management
- 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
- 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.
- Service Asset and Configuration Management
- Process Objective: To maintain information about Configuration Items required to deliver an IT service, including their relationships.
- Knowledge Management
- Process Objective: To gather, analyze, store and share knowledge and information within the organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge.
Additional Information on Service Transition
Downloads
Overview Service Transition - Downloads
|
Use the following links to open the process overview of Service Transition showing the most important interfaces: |
 |
