Configuration Management (CFM) 

Summary 

Level 2 – Singular 

CFM 2.1 – Identify configuration items and the associated configuration and change management system 

CFM 2.2 – Establish and maintain a configuration management system 

CFM 2.3 – Manage versions, baselines and releases 

Level 3 – Shared 

CFM 3.1 – Established and maintain rules for integrated configuration management 

  

Detail 

Level 2 – Singular 

CFM 2.1 – Identify configuration items and the associated configuration and change management system 

Specify which items are to be put under configuration management. For example, all company documents are to be stored in SharePoint services. All software is to be managed through GitHub

CFM 2.2 – Establish and maintain a configuration management system 

Establish and maintain the configuration management tools and structure. Deploy and maintain the versions of the software. Establish configuration management standards, such as naming standards, versioning standards and repository structures standards. Establish the processes for making changes to the configuration items. 

CFM 2.3 – Establish versions, baselines and releases and manage changes to it 

Create the configuration management version, baselines and releases according to the configuration management standards. 

Level 3 – Shared 

CFM 3.1 – Established and maintain rules for integrated configuration management 

Establish the business rules for the alignment of the configuration management system, for example, alignment between SharePoint and GitHub. What information may be stored in SharePoint versus GitHub and vice versa. How to baseline and release across the two systems. 

CFM 3.2 – Manage changes across configurations 

Manage changes to configuration items, baselines and release that may impact other configuration management items, baselines and releases. For example project 1 releases software that may impact project 2. For example, establish a Change Control Board (CCB) across the projects or configuration management systems to manage changes that impact each. 

Version 1 

Design Maturity 

Design maturity