Explanation: The steps involved in the Release Management process is:
Policy and Planning - A document, called the Release Policy, is developed by the Release Manager and defines how and when releases are configured. Prior to planning a release, information must be gathered about various aspects of the release, such as product life cycle, description of relevant IT service and service levels, authorization for relative RFCs, etc. Planning the release involves coordination, scheduling, drawing up a communication plan, defining roles and responsibilities, constructing back-out and quality plans, and more.
Design, Building and Configuration - Standard and reusable procedures and documentation should be used for designing, building and configuring releases. Configuration items within the release may come from internal or external bodies. In
either case, laboratory-based development testing along with appropriate operational documentation should be prerequisites before a release is considered available for implementation.
Testing and Acceptance - Lack of testing is the most common cause for unsuccessful changes and releases. Releases should undergo functional, operational, performance and
integration testing by the appropriate personnel. Testing should include back-out plans. Acceptance should be performed for each step of the release process and be submitted to
Change Management for approval. Once approved, the release can be rolled out and the relevant configuration changes can be integrated within the CMDB (see Configuration Management).
Rollout Planning - Includes a detailed timetable of release events including staff responsibilities and action items, documentation, and purchasing plans for required
hardware and software.
Communication - Personnel, typically the Service Desk or Customer Relations, communicate the planned changes to users and the expected service impact. Training
sessions may be required to aid users with the release.
Distribution and Installation - Involves the distribution of software and supporting hardware identified and approved in the previous activities.