Configuration Management (CM)

The process of systematically handling changes to a system in a way that maintains integrity over time. CM involves identifying, controlling, and tracking all versions of code, documentation, and hardware components.

CM Lifecycle

The Configuration Management lifecycle consists of five key phases:

1. Planning and Management

   Establish CM policies, procedures, and standards. Define the scope of CM activities and identify resources needed.

2. Identification

   Identify and document the characteristics of each Configuration Item (CI) and their relationships to other CIs.

3. Control

   Manage changes to CIs through a formal change control process. This includes evaluating proposed changes, approving or rejecting them, and implementing approved changes.

4. Status Accounting

   Record and report on the status of CIs throughout their lifecycle. This involves tracking version histories, change histories, and current configurations.

5. Verification and Audit

   Regularly review and verify the accuracy of configuration documentation against the actual system configuration. Conduct audits to ensure compliance with CM policies and procedures.

The CM lifecycle is iterative, with each phase feeding into the next and the cycle repeating as systems evolve and change over time. Effective implementation of this lifecycle ensures that an organization maintains control over its systems and can manage changes efficiently and reliably.

Methodology specific dictionaries / glossaries

• View the Agile Dictionary
• Managing Successful Programmes (MSP) Dictionary
• Prince 2 glossary of terms
• Full ITIL glossary of terms
• See also Risk Management Dictionary.