Release Management
Planning
It is crucial to establish a general framework for the launch of new versions. This must set out the working methods. This is especially important for small or emergency releases, as in the case of large releases specific plans taking into account the specific features of each case will be drawn up.
In order to plan a new release properly, the following points need to be taken into account:
- How does the new version affect other areas of the IT framework?
- What CIs will be directly or indirectly involved during and after the launch of the new version?
- How should the test environment be built so that it is a faithful reflection of the production environment?
- What back-out plans are necessary?
- How and when should back-out plans be implemented in order to minimise the possible negative impact on the service and the integrity of the IT system?
- What are the human and technical resources necessary to ensure the new release is implemented successfully?
- Who will be directly in charge of the various stages of the process?
- What information and/or training plans need to be developed so that users are kept informed and are able to perceive the new version as an improvement?
- What type of deployment is most appropriate (complete, delta, synchronised at all sites, gradual, etc.)?
- What is the expected average useful life of the new version?
- What impact is the release process likely to have on the quality of service?
- Is it possible to establish precise metrics defining the degree of success of the launch of the new version?
