How IT Service Transition [ST] can be used by a Startup – by example

The ITIL V3 phases Service Transition [ST] helps the IT services companies to implement their planned and designed services by using its different sub-processes.

In this blog, I am trying to connect to the Service strategy and Service design articles [and kindle book] wrote by me in the past with implementable scenarios for IT Startups.

Those examples are connected in this blog. This blog [in different parts] can give you the ST processes  details with examples and its practices implementation for any startups or who need to follow ITIL V3 practices.

At the same time, the people who are appearing for ITIL V3 ST exam also can simulate them in the similar way. You can refer to my previous blogs: The advantages of ITIL V3 Service design Practices for IT start-up company [].

With reference to the ITIL V3 Service transition, its entry criteria is there should be services with their design completion. Once the service(s) design is completed, the next step is its implementation planning and execution.

Let us consider the previous blogs services examples; if we consider the data migration service as a new service, we might need to do the following: Once the services are accepted by the customer, we need to plan for the below typical activities:

· Resources planning and their deployment in the project.

· The relevant project planning and its execution plan.

· The relevant skills capability building as an ongoing activity.

· Choosing the suitable Project management methodology [PMI or PRINCE2] and its transition to the project resources.

· Seeking the required organizational support.

· Working closely with the stakeholders as per their needs.

· Setting up the required infrastructure.

· Managing the required changes.

· Acquiring the required knowledge for the project and making a knowledge repository for the project resources.

· Developing the required ETL programs. 

· Evaluating the data migration ETL programs.

· Planning for the Data migration for live.

· Releasing and Deploying the data migration on production.

· Certifying the live data for business usage.

You can see my blog on Data migration Best practices [].

If we recollect all the above activities, they can be related to the ITIL V3 Service transition process areas.

Now let us see the ITIL V3 ST processes: Following are the seven key processes used during Service Transition.

I. Transition planning and support.
II. Change management.

III. Service asset and configuration management.

IV. Release and deployment management.

V. Service validation and testing.

VI. Evaluation.

VII. Knowledge management.

The above processes are being denoted in the below chart also:

Further  details on this topic [Part2] can be seen in my future blog please.

You can also visit for my  #Kindle Books:

How ITIL V3 Service Transition [ST] implementation can be done – by example [Part2]

In continuation of my previous blog on ‘How ITIL V3 Service Transition [ST] can be used by a Startup – by example [Part1] []’, the below content is narrated.

As we have seen there are seven key process areas during ST implementation, let us see their usage.

Before going to this part of the blog let us recollect the key process areas through the below chart:

What is Transition planning and support ?:

This process is accountable towards transitioning of the new or modified services to the customer. At the same it can plan and seek for the required support.

Scenario: With reference to the above example, Data migration as a new service is being offered after the Service design completion. As mentioned in the above on this article, there are couple of simple and complex activities have been identified. Those need to be projected under Project Management and risk management. The required support need to be planned under each activity.

At the same time during this phase, the key process areas of Service transition also need to be considered and they need to be amended under project planning. As mentioned in my blog on data migration best practices, some of them might be very useful for risk mitigation and treatment also.

What is Change management ?:

Any designed  services might need some change at any time of their implementation. Due to many technology trends or changes are happening, the change in some of those services are mandatory. We need to assess the required changes and their impact on other services. If there are changes required for other services as dependency of the currently introduced service, it need to be planned for service transition.

If the change is required upto the current service only, then one need to plan for its changes assessment or impact within the service and need to modify the required areas of the planned transition activities.



Let us assume during the data migration service POC, your customer assumed ORCALE older version can be used. But when the data migration impact analysis is done they felt  the latest version should be used. Then as an IT service company you need to do the project assessment and the impact analysis for this new or changed requirement.

You need to train the resources for the source and target versions of the ORACLE data migration. At the same time the relevant data interfaces also need to be assessed on their impact and the modifications. If you are using any open or mainframe systems application interfaces, you need to apply those services changes also.


If your applications are not having any interfaces and it is an independent application data migration, then you can assess the source and target versions of the ORACLE and plan accordingly.

What is Service asset and configuration management ?

We can see each of these items separately.

While using Information technology there are software and hardware resources need be used , if we need to build any software architecture or product. In such case we need to identify the required assets, their category, type of asset and its usage along with their upgrade status.

These items need to be maintained under repository. Their repository process management is known as Configuration management. The configuration management is a mandatory activity.

Apart from managing the above assets management, we also need to manage the IT services configuration management also.

Let us assume there are new services, old services and the retired [removed] services. These services details like an asset need to be maintained in under services asset configuration management.


Let us assume, the data migration services is a new service designed for IT services. It has its own catalog, its start date, the relevant technologies need to be used, the required resources skills and experiences, the capability management, Proof of concept process, etc. are being designed during the services design. It need to be registered under Services asset and configuration management.

In future if this service is modified or terminated it need to have its history as per this key process area of Service transition.

Similarly, we can build the history for all kinds of  IT  services.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s