ITIL Service Transition Processes

Service Transition phase aims to build, test and deploy the service in production in cost-effective manner:

Key Processes of Service Transition are :

 

Transition Planning and Support:

 

It coordinates and manages the resources that are involved in transitioning the service from one phase to another. By doing so, it ensures that all the requirements that are identified in service strategy phase are achieved and designed in service design phase. It identifies and manages the risks that can lead to discontinuity of the services. 

 

A well designed transition plan increases an organization’s capability to successfully handle more number of changes, releases and deployments with less work, time and risk. Once the change is deployed, the transition should regularly monitor the change and amend the transition plan if required. 

 

Change Management:

 

Change – an addition, enhancement or removal of any service can be either reactive or proactive. A reactive change is made to resolve immediate errors. A proactive change is made to streamline the organization process for the cost reduction benefit. 

 

The primary objective of change management is to follow the standardized process to efficiently and promptly handle the change with minimum impact to the existing functionality of the system. 

 

The details of the change are recorded in RFC – Request for change document. For any change to be deployed in production, it has to be approved at all the appropriate levels of business.  

 

Service Asset and Configuration Management (SACM):

 

This process ensures that the assets involved in service delivery are properly measured and the integrity of configuration items (CIs) is maintained.   SCAM regularly monitors and reports the status of the assets and CIs. It gathers information regarding how assets are related to each other so that a detailed impact and risk analysis can take place.  The management supports all the service assets and processes – change, incident and release. 

 

Release and Deployment Management (RDM):

 

Changes are moved into production under a release. The objective of release and deployment management is to plan, schedule and control the movement of release in the live environment while protecting the integrity of the existing services.

 

By developing a balanced technique of managing the releases and deployments, it enhances the service provider to deliver a change faster and at optimum cost.   

Service Validation and Testing (SVT)

 

The process involves the validation and testing of the new or modified IT service. It ensures that the service matches the technical design specification and generates expected business results.

 

Change Evaluation:

 

It ensures that the change is authorized to be deployed in production. It does a thorough assessment of the new or changed service to ensure that the actual expectation and performance is as per the desired expectation and performance. It also ensures whether the change will provide enough return to guaranteed budget.

 

Knowledge Management (KM):

 

The process focuses on sharing the ideas and experiences to improve the decision making quality of management so that more reliable and secure data is delivered to the business.