Release Policy planning (Part 2)

By Laurent Duenas, March 15th 2013 

 

A difficult concept to implement

 

Release policy is a deliverable which requires the mixing of several planning constraints.

The “end-to-end” vision of an IT Service implies mixing the evolution roadmaps of different components (application software, infrastructure software and sometimes equipment) on the same schedule.

In order to stay agile while preserving IT Service stability during Release (see following impacts), the reflection exercise about this unified schedule becomes very complex. Companies are actually left to themselves and field achievements are rare.


That is why many companies still prefer to enjoy comfort without any regulation or planning constraint rather than to indulge in a reflection considered as an uncertain undertaking.


A day-to-day operating mode limits IT Service availability to stabilize

In a day to day operating mode, the unavailability risk of an IT Service is strongly increased. Unavailability causes are proportional to the number of changes made (let's not forget that 80% of incidents result from changes).


The chart below lists all possible changes carried out in an uncoordinated way, i.e. outside any Release Unit or Release policy concept. It shows what could be the impacts on a vital IT Service, in a typical company, incurred by stakeholders as follows:



Other articles

►  No link


External links

►  No link


Related products

►  Change & Release ...

Copyright © 2014 - PRACT Publishing