ITIL Service Transition – Plan Release and Deployment Packages

ITIL Service Transition aims to function at the best of its ability, and seeing that changes would be permanent and would greatly affect the overall standing of a business, it is but wiser to vigorously plan the details of a release and deployment of change in a service operation.


All updates are recorded in the Configuration Management System

Service Transition should always relay their progress and send their updates in the network's Configuration Management System. By doing this, the stakeholders can easily track the progress of a service change.


Releases are planned well in advance

A release should be properly planned, as it involves an intricate interplay of figuring how the company's budget, the time of the release and the reaction of the users and the effect of the change within the company would take place.


Resource utilization is optimized across Service Transition activities to reduce costs

Service Transition requires careful planning, as to have a clear overview of the costs involved in the proposed release and deployment changes. By following a detailed plan, costs would be easier to manage within the process.


Resources are coordinated during release and deployment

Changes can be made more easily and effectively, if the resources available within the Service Transition process are coordinated during the release and deployment of a service change.


Release and distribution mechanisms are planned to ensure the integrity of components during installation, handling, packaging and delivery is maintained

For effective delivery of a service change, it is necessary for Service Transition to check and re check the progress of a release and deployment of a service. This would make or break the company's standing in the market, that's why careful scrutiny is given on each step.


Emergency releases are managed in line with the emergency change procedure

If there is an instance where an emergency release is necessary, Service Transition should aim to manage it in line with the emergency change procedure.


The risks of backing out or remediating a failed release are assesed and managed

Given that projects and proposed changes doesn't always work out the way it was planned, the Service Transition team should first assess if the company would benefit more if the release of a service change is pulled out, or re processed to be tweaked and improved.
ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce.