Service Transition

Term/Theory

Definition/Point

Input

  • Transitioning new/changed IT services to operation
  • Internal service (move from what’s required) to concept of how it’s implemented
  • Organizational level: Develops capabilities and resources to allow IT to transition to reality

Service level:

  • Resources/capabilities convert DS requirements into portfolio
  • Require good set of processes to implement in operations
  • Provides control; allow you to speed up/slow down

Purpose

Ensure that new, modified or retired services meet the expectations of the business

Objectives

Primary: delivery service vision in a relevant, timely, quality and cost‐effective manner.

Tertiary:

  • Plan/manage res to establish service
  • Ensure minimal impact on production
  • Increase stakeholder satisfaction
  • Increase proper use of services

Scope

  • The development and improvement of capabilities including release planning, building, testing, evaluation and deployment
  • Introducing, Retiring, or Transferring new or changed services

Value to Business

  • Enable projects to estimate the cost, timing, resource requirement and risks more accurately
  • Result in higher volumes of successful change

Resources and Capabilities

Service Transition must test against resources and capabilities.

Key aspects of SDP required by ST team

 

Journey from as is → required.

  • Applicable services packages
  • Service specs/models
  • Arch design required to deliver
  • Definition/design of each release
  • Detailed design of how service components will be assembled
  • Release/deployment plans
Conclusion SDP completed