ITIL Continual Service Transition

From Minor Miracle Software
Jump to: navigation, search

"The primary objective of Service Transition is the development and improvement of capabilities for transitioning new and modified services into operation." or
Push a change into production without burning the house down.

  • Pick the longest answer.

Four Phases of release and deployment management

  • Planning
  • Build and test
  • Deployment
  • Review and close
  • Service Knowledge Management System (SKMS)
    • Configuration Management System (CMS)
      • Configuration Management Database (CMD)
      • Known Error Database (KEDB)
  • Releases are defined as
    • Minor
    • Major
    • Emergency -
  • Service Asset and Configuration Management (SACM)
    • Ensure releases into controlled environments and operational use are formally authorized.
  • Configuration Item (CI) - A service asset that needs to be managed in order to deliver an IT service.



  • Remediation Planning - Planning the actions to be taken to recover after a failed change or release.
  • Definitive Media Library (DML) - A secure library for authorized versions of software
  • Releases are defined as - Minor, Major and Emergency
  • Emergency Change - The change is intended to repair an error in an IT service that is negatively impacting the business to a high degree.
    • Resolution of a major incident
    • Operational Repair
    • Implementation of a Security Patch


  • NOT responsible for
    • Detailed planning of the build, test and deployment of individual changes or releases.
  • Change Management Scope
    • Processes and Documentation
  • Release Policy - Exit and Entry criteria for the release.
  • Knowledge Management - gather, analyze, store, share, use and maintain knowledge, information and data
  • Difference between standard and normal change.
    • Standard Change is pre-authorized
    • Normal Change is anything that is not a standard or emergency change. Urgently needed, because of poor planning or sudden changes in business requirements.
  • Change with Major risk initiated - Through Service Portfolio Management (SPM) with a change proposal.
  • Park of SKMS - all
  • Change Model - all
  • Only authorized changes are made - SACM
  • Maintain knowledge - Knowledge Management
  • Included in the scope of change management - all
  • Transition objectives - all
  • Urgent change - normal change.
  • Which policy defines the following? - Release Policy
  • Lifecycle Stages


  • Following included in scope of change management? - All of the above
  • Before chartering new anything - Change proposals, not RFCs
  • Critical elements of a standard change? - Defined trigger to initiate change.


  • Change Management NOT
    • knowledge transfer.
  • Short, Medium, Long term - Where do we want to be?


Internal Links

Parent Article: ITIL Foundation Certification