What is Configuration Management?

When we refer to the configuration of a system, we mean the technical description of a system and how its component parts inter-connect.
So, what is Configuration Management?

We define Configuration Management in our free PM Glossary: ‘Be on the Inside. Decode the Jargon of Project Management’, as:

'Defining, controlling, releasing, changing, documenting, and reporting the configuration items in a system.'

We can think of that system as, for example, a technology solution we are implementing, or as the project itself. In the latter case, configuration management concerns itself with the project scope, quality management, and change control.

However, most often, we are concerned with the configuration of a solution we are building or adapting within our project. Therefore, configuration management is an important DevOps process - DevOps is a set of practices that combines software development and IT operations.

The purpose of configuration management is to ensure that we can properly track how a system is configured through its whole life, from development to retirement.

Without proper configuration management, we cannot build, test, install, accept, operate, maintain or support the system.

A big part of it is tracking changes, so we need to collect and structure a lot of data, such as:
• Date
• Version number
• Status
• Product owner
• Features
• Components
• Connections and interfaces
• Relationships with other products

It is beyond our scope to look at the methodologies and how we carry out configuration management. However, I will list the five principal components:
• Configuration Management Planning to create your CM plan document
• Configuration Identification – establishing and maintaining a baseline configuration against which changes can e tracked and recorded
• Configuration Control – like Project Change Control, this is the process of evaluating and accepting or rejecting changes to the configuration
• Configuration Status Accounting – recording and reporting on the configuration, as it changes
• Configuration Verification and Audit – independent (or quasi-independent) review of processes, artifacts, and compliance

As you might expect, there is a big choice of software tools to support configuration management

For us, as project managers, we need to ensure that our Project Plans include any configuration management plan. It will be part of your scope management process.

Recommended Videos
Carefully curated video recommendations for you:

A while back, I asked Project Managers in a couple of forums what material things you need to have, to do your job as a Project Manager. They responded magnificently. I compiled their answers into a Kit list.
Note that the links are affiliated.

#Project #ProjectManagement #ConfigurationManagement

[IsraelOlorunpomi]

The CM presentation by you is fantastic, so simple, broken down into bits that can be easily assimilated; if only there were more videos dedicated to CM instead than as part of PM, that would be fantastic.only CM as a subject. Many thanks.

[dw]

Thanks for the video. You explained it clear, concisely, and well. I have an interview for a configuration analyst position in a few days!

[iifyrjy]

Hi Sir! this is the great summary of configuration management. Especially, the way you build foundational understanding of concepts is really appreciative.

[chairulhalim]

Great CM definition and explanation for newbie !!!

[taramnl]

Thank you for the explanation...I will attend na iso9001 audit and was confuse with cm audit checklist..thank you for enlightening me.

[tqcqdhv]

Hi Mike this is a great summary of Config Management - In Aero looking after CMADS so would be great to touch base when you have a moment

[Margaret_fvn]

All of them expected nothing less than instant death; but to their surprise the wooden creatures flew into the air with them and bore them far away, over miles and miles of wooden country, until they came to a wooden city.

[dagwould]

I know that the PMBoK uses the terms, but I find 'quality' and 'scope' management, and the use of other abstractions in the PM triad unhelpful, indeed, unhelpfully static. So, rather than quality, I use 'performance'. Acceptance of a product must be due to it providing the function/capability by its meeting the stated performance requirements. Concrete but situationally dynamic language is fare more helpful, IMO. So, my project triad is about producing out-turn Value in terms of Investment, Performance and Delivery. Configuration issues feed into both performance and investment, and obviously can have an effect on delivery. Delivery of course one can manage; time no one 'manages'.

[ssevideos]

Very nice explanation (menuda piñata maikel)

[Thomas_yp]

Relax, it's just important refund info

[Onlinepmcourses]

The link to Be on the Inside: Decode the Jargon of Project Management is in the description.

[resulcelik]

Your videos are very useful, but when you speak, you are emphasizing every word and it is very tiring. If you change your narrative style, you can have much better videos.