9.2 Scope of Release Management

Release Management undertakes the planning, design, build, configuration and testing of hardware and software to create a set of Release components for a live environment. Activities also cover the planning, preparation and scheduling of a Release to many Customers and locations. Release Management activities include:

• Release policy and planning
• Release design, build and configuration
• Release acceptance
• rollout planning
• extensive testing to predefined acceptance criteria
• sign-off of the Release for implementation
• communication, preparation and training
• audits of hardware and software prior to and following the implementation of Changes
• installation of new or upgraded hardware
• storage of controlled software in both centralised and distributed systems
• Release, distribution and the installation of software.

The main components to be controlled are:

• application programs developed in-house
• externally developed software (including standard off-the-shelf software as well as customer-written software)
• utility software
• supplier-provided systems software
• hardware, and hardware specifications
• assembly instructions and documentation, including User manuals.

All deliverables need to be managed effectively, from development or purchasing, through customisation and configuration, through testing and implementation, to operation in the live environment.

Figure 9.1 - Major activities in Release Management

Release Management should be used for:

• large or critical hardware rollouts, especially when there is a dependency on a related software Change in the business systems, i.e. not every single PC that needs to be installed
• major software rollouts, especially initial instances of new applications along with accompanying software distribution and support procedures for subsequent use if required
• bundling or batching related sets of Changes into manageable-sized units.

Figure 9.1 outlines the major activities in Release Management and their position in the life-cycle of a Change. Configuration Management records should be updated during build and Release to ensure that there are trusted Releases that can be reverted to in case of problems. A Release should be under Change Management and the content and timing of a Release should be authorised in advance via the Change Management process.