9.8 Relations to other processes

Release Management should use the controlling processes of Configuration Management and Change Management.

9.8.1 Configuration Management

Whenever new versions of software are added to the DSL, its details should be simultaneously included in the CMDB. Similarly, whenever new or changed hardware is rolled out, the CMDB should be updated. The CMDB should always contain the current status information on all authorised software and hardware and is used to ensure that only the correct components are included in a Release.

Release Management may use various services of Configuration Management during the implementation of a Release (e.g. configuration audit to ensure that the target environment is as expected). It is possible to combine these two functions with or without Change Management to form one organisational unit.

9.8.2 Change Management

The CAB, as defined in the Change Management process, with advice from Release Management, is responsible for recommending the content and scheduling of Releases. Release Management is then responsible for implementing the agreed Releases. Release Management is normally represented on the CAB and is involved in establishing the organisation's Release policy.

Although Release Management oversees the details of the roll out of a Change, it is under the control and authority of Change Management.

9.8.3 Software from Developers and suppliers

When software is accepted from developers or suppliers, it is placed into the DSL and registered in the CMDB. Release Management is responsible for building Releases from the DSL into the controlled test environment. When testing has successfully concluded, Release Management should distribute the Release into the live environment.

9.8.4 Problem Management and the Service Desk

At the end of the successful distribution and installation of a new Release, various records in the Problem Management system need updating as follows:

• any related Problems or enhancement requests should be closed
• any known Problems introduced by the new Release should be added to the database to allow Service Desk staff to support the new Release
• Problem Management and Service Desk staff should be informed of the new Release so that they can support its use in the live environment. Such staff should receive training in any new or revised support procedures.

Problem Management staff are also often involved in identifying faults that will lead to Requests for Change (RFCs) and so eventually lead to new Releases.

9.8.5 Project Management and PRINCE2

For software developed under the control of a PRINCE2 project, Release authorisation requires Operations Acceptance and User Acceptance letters.

Release Management should assist project management in planning and implementing a Release, but it does not take control.