Release management is an important step in the ITIL Service Transition stage. This process is covered in detail in ITIL foundation training. It is important to understand what a release unit means in order to fully appreciate why it is so crucial. A well-defined release policy is essential for effective release management, as you will learn in an ITIL course. This article will discuss release units and release policy.
What is release management?
A release unit is a collection of components that make up an IT Service and are usually released together. Services, components, applications etc. They are only useful if they work together for the benefit and satisfaction of customers. If the service is not successful, it will not create value for the customer. With all its components, assets, and services, a release unit provides value to customers.
Release Management: Examples for release units
One release unit could include hardware, software, documentation, and licenses. An operating system is required for each end user. A desktop PC cannot be used by itself. A PC cannot be used to create text without a text editor. Without antivirus software, a computer is vulnerable to viruses and other threats. Software, hardware, licenses, documentation, and other components of a PC make up a release unit that delivers value to customers. Release management ensures that each component of a release unit is properly accounted for. Release management also ensures that the right release units are distributed.
Complexity of Release Units: Release Management
Sometimes, release management involves a complex rollout of release units. This table lists two examples of release units used in release management. The first is Homepage, which is an IT service. This service allows for the replacement of pages, i.e. Only changes to the text and no addition of links. This change will be simple and requires little effort. A homepage that has been modified is usable with its text, pictures, navigation links, etc. According to the release management process, it is a release unit. The second IT service is Geographical Information System, which is a high-complexity change according to release management. This could include the entire application, including manuals.
Release management: Criteria for a release policy
We know that policies are the guidelines and to-dos for a process. The release policy is part of the management process. A release policy is a document that aims to support transition planning and support. A release policy must meet several criteria.
Unique identification, numbering, and naming conventions
The release policy should include unique identification, numbering, and naming conventions. An IT service provider will offer many services, components, and applications. Proper identification, numbering, and naming conventions are required to properly refer each asset and each version. A simple example of a convention to identify services in a bank is services beginning with one digit belong to core banking, while services beginning with two belong to internet banking. Services starting with three belongs the ATM channel.
Roles and responsibilities
Release management is a process that requires clear roles and responsibilities. The release policy must clearly outline the roles and responsibilities for each phase. Release management roles and responsibilities could include the person who builds the release, tests it, and the dep