Actions

Difference between revisions of "ITIL Service Transition"

Line 2: Line 2:
  
  
[[File:service transition.jpg|400px|ITIL Service Transition]]<br />
+
[[File:service transition.jpg|500px|ITIL Service Transition]]<br />
 
source: [https://www.tutorialspoint.com/itil/service_transition_overview.htm Tutorials Point]
 
source: [https://www.tutorialspoint.com/itil/service_transition_overview.htm Tutorials Point]
 +
 +
 +
== Objective and Scope of ITIL Service Transition<ref>Objective and Scope of ITIL Service Transition [https://purplegriffon.com/blog/service-transition-manager-role Purple Griffon]</ref> ==
 +
 +
''The key objectives of service transition are to:''
 +
*Plan and manage service changes efficiently and effectively
 +
*Manage risks relating to new, changed or retired services
 +
*Successfully deploy service releases into supported environments
 +
*Set correct expectations on the performance and use of new or changed services
 +
*Ensure that service changes create the expected business value
 +
*Provide good-quality knowledge and information about services and service assets.
 +
''In order to achieve these objectives, there are many things that need to happen during the service transition lifecycle stage. These include:''
 +
*Planning and managing the capacity and resources required to manage service transitions
 +
*Implementing a rigorous framework for evaluating service capabilities and risk profiles before new or changed services are deployed
 +
*Establishing and maintaining the integrity of service assets
 +
*Providing efficient repeatable mechanisms for building, testing and deploying services and releases
 +
*Ensuring that services can be managed, operated and supported in accordance with constraints specified during the service design stage of the service lifecycle.
 +
Some activities of all service transition processes may be carried out during the service design stage of the service lifecycle – for example, design of a release package or planning of a service transition.
 +
 +
''The scope of Service Transition includes:''
 +
Managing the complexity associated with changes to services and service management processes
 +
*Allowing for innovation while minimizing the unintended consequences of change
 +
*Introducing new services
 +
*Changes to existing services, e.g. expansion, reduction, change of supplier, acquisition or disposal of sections of user base or suppliers, change of requirements or skills availability
 +
*Decommissioning and discontinuation of services, applications or other service components
 +
*Transferring services to and from other service providers.
 +
''Guidance on transferring the control of services includes transfer in the following circumstances:''
 +
*Out to a new supplier, e.g. outsourcing
 +
*From one supplier to another
 +
*Back in from a supplier, e.g. insourcing
 +
*Moving to a partnership or co-sourcing arrangement (e.g. partial outsourcing of some processes)
 +
*Multiple suppliers, e.g. co-sourcing or multi-sourcing
 +
*Joint venture
 +
*Down-sizing, up-sizing (right-sizing) and off-shoring
 +
*Merger and acquisition
 +
''In reality, circumstances generate a combination of several of the above options at any one time and in any one situation. And if that was not enough, the scope also includes:''
 +
*The transition of changes in the service provider’s service management capabilities that will impact on the ways of working being:
 +
*The organization
 +
**People
 +
**Projects
 +
**Third parties involved in service management

Revision as of 20:33, 11 January 2021

The role of ITIL Service Transition is to move services and service changes into operational use. ITIL Service Transition also introduces the service knowledge management system (SKMS) which has the ability to support organizational learning and assist in increasing the effectiveness and efficiency of all stages of the service life-cycle. This provides benefits to people with the knowledge and experience of others, helps to support decision-making and improve the management of services.[1]


ITIL Service Transition
source: Tutorials Point


Objective and Scope of ITIL Service Transition[2]

The key objectives of service transition are to:

  • Plan and manage service changes efficiently and effectively
  • Manage risks relating to new, changed or retired services
  • Successfully deploy service releases into supported environments
  • Set correct expectations on the performance and use of new or changed services
  • Ensure that service changes create the expected business value
  • Provide good-quality knowledge and information about services and service assets.

In order to achieve these objectives, there are many things that need to happen during the service transition lifecycle stage. These include:

  • Planning and managing the capacity and resources required to manage service transitions
  • Implementing a rigorous framework for evaluating service capabilities and risk profiles before new or changed services are deployed
  • Establishing and maintaining the integrity of service assets
  • Providing efficient repeatable mechanisms for building, testing and deploying services and releases
  • Ensuring that services can be managed, operated and supported in accordance with constraints specified during the service design stage of the service lifecycle.

Some activities of all service transition processes may be carried out during the service design stage of the service lifecycle – for example, design of a release package or planning of a service transition.

The scope of Service Transition includes: Managing the complexity associated with changes to services and service management processes

  • Allowing for innovation while minimizing the unintended consequences of change
  • Introducing new services
  • Changes to existing services, e.g. expansion, reduction, change of supplier, acquisition or disposal of sections of user base or suppliers, change of requirements or skills availability
  • Decommissioning and discontinuation of services, applications or other service components
  • Transferring services to and from other service providers.

Guidance on transferring the control of services includes transfer in the following circumstances:

  • Out to a new supplier, e.g. outsourcing
  • From one supplier to another
  • Back in from a supplier, e.g. insourcing
  • Moving to a partnership or co-sourcing arrangement (e.g. partial outsourcing of some processes)
  • Multiple suppliers, e.g. co-sourcing or multi-sourcing
  • Joint venture
  • Down-sizing, up-sizing (right-sizing) and off-shoring
  • Merger and acquisition

In reality, circumstances generate a combination of several of the above options at any one time and in any one situation. And if that was not enough, the scope also includes:

  • The transition of changes in the service provider’s service management capabilities that will impact on the ways of working being:
  • The organization
    • People
    • Projects
    • Third parties involved in service management
  1. What is ITIL Service Transition? Invensis
  2. Objective and Scope of ITIL Service Transition Purple Griffon