The moment of truth has arrived, the distribution of the new version, or rollout.
There are several types of rollout:
- Complete and synchronised: a complete rollout takes place simultaneously on all sites.
- Fragmented: either in space or time. For example, the new version is released to different work groups or the functionality offered is progressively increased.
The rollout procedure must be carefully documented so that all the parties are aware of their specific tasks and responsibilities. In particular, end users must be informed of the release schedule in advance and told how it might affect their day-to-day activities.
It is essential to clearly define:
- The CIs that should be deleted and installed, and the order in which this process should take place.
- When this process should be carried out in the case of different work groups and/or geographical locations.
- What metrics determine the implementation of back-out plans and whether these should be complete or partial.
After distributing the new release, Release Management must ensure that:
- A copy of the version is included in the DSL.
- The DHS includes the functional responses of the new CIs.
- The CMDB is properly updated.
- Users are properly informed about new functionality and have been given the training they need in order to be able to make best use of it.
After the release, Release Management must be informed in a timely way by the Service Desk of any comments, complaints, incidents, etc. that the new version may have produced. All this information must be analysed to ensure that future versions incorporate the suggestions received and that the necessary corrective measures are taken to minimise the negative impact that future changes might have.