Goal oF Release Management
Many service providers and suppliers may be involved in the Release of Hardware and software in a distributed environment. Good resources planning and management are essential to package and distribute a Release successful to the Customer. Release Management takes a holistic view of a change to an IT service and should ensure that all aspect of a release, both technical and non-technical, are considered together.
The goals of Release Management are:
The focus of Release Management is the protection of the live environment and its services through the use of formal procedures and checks. Release Management works closely with the Change Management and Configuration Management processes to ensure that the shared CMDB is kept up-to-date following changes implemented by new Releases and that the content of those releases is stored in the DSL. Hardware specifications, assembly instructions and network configurations are also stored in the DSL/CMDB. Release Management is often funded from major projects rather than being included in the cost of the normal service to Customers. Although there are costs associated with implementing Release Management, these are far less than the potential costs of not adequately planning, managing and controlling software and hardware Releases.
The 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 too many Customers and locations.
Release Management activities include:
The main components to be controlled are:
All deliverable’s 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:
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 the 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 authorized in advance via the Change Management process.