Get Configuration, Change And Release Management Policies And .

Release Management is a category of Change Management that ensures that the Configuration Management Database (CMDB) is kept up to date, that changes are appropriately managed, and that all new software and hardware is stored in the Definitive Software Library (DSL) and Definitive Hardware Store (DHS).

While they both seek to ensure consistency of systems, they do so in different ways. In change management you are keeping track of changes to software and hardware, while configuration management focuses on everything else around the application or system.

CCM is a continuous process of controlling and approving changes to information or technology assets or related infrastructure that support the critical services of an organization. This process includes the addition of new assets, changes to assets, and the elimination of assets.

The Difference Between Change Management and Configuration Management Systems. The main difference between the change management and configuration management systems is that change management deals with process, plans, and baselines, while configuration management deals with product specifications.

Release and Deployment Management includes three release types: Emergency, Major, and Minor.

If Change Management is a governance process, Release Management is an action process. Under the authority of Change, Release builds, tests and releases new or updated services into the production environment. Every release is comprised of a single change or package of changes.

Change works with release management, where release management is concerned with "Implementation", unlike change management which focusses on "Risk" and "Business Justification". In practice change and release management function as a single lifecycle to execute a change into production environment.