ITIL Service Transition – Defining and Implementing a Formal Policy for Service Transition

ITIL Service Transition plays a pivotal role in making the demands of Service Design a reality.

Service Transition, as a systematic process, needs a stable groundwork of policies to mark the start of a seamless operation.

All participants should create a detailed and formal set of policies that states the agreement and the services required from each party, as to avoid confusion when the actual process of service transition takes place. The formal sign off should be handed and notarized by each of the decision makers and management owners.


Policies should be clearly stated

To achieve a smooth progression of a service transition, policies for the project should be clearly stated before the start of the project. If and when a party decides to deviate from the agreed plan, an immediate plan of action should be reinstated.


Align the polices with the overall framework

The service transition policies should be in conjunction with the overall framework and objectives of the organization. These policies should also be adept to the principles of the Service Management polices.


Sponsors and decision makers should show their commitment in adopting these policies

After reading and agreeing on the proposed principles set for the Service Transition, all of the participants involved, including the sponsors and the decision makers should adhere to the policies. This is made possible by adhering and efficiently implementing the policies in the Service Transition process, even in the off chance that they might encounter inevitable road blocks in the service lifecycle.


Use processes that integrate teams

The Service Transition operation should aim to use processes that would promote team building. By doing this, it would create a more harmonious and productive team effort, all the while keeping a clear vision of their accountabilities and responsibilities.


Deliver changes in releases

As Service Transition takes place in the service lifecyle, positive and efficient changes are imperative once a release takes place.


Address deployment early in the release design

It is essential that deployment of changes within the service transition process should be duly noted and relayed to all of the parties involved as early in the release design and the release planning stages of the service lifecycle.
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce.