Project Management guide · Risk, quality and control
Configuration Management in Project Management Explained
Configuration management is the discipline of identifying the items that make up a project's products and documents, controlling their versions, recording their status and verifying that what exists matches what was approved. It ensures everyone works from the right version.
Key takeaways
- Configuration management ensures everyone uses the right version of every item.
- Its core activities are identification, control, status accounting and audit.
- Baselines provide agreed reference points.
- It works hand in hand with change control.
Why it matters
- Stops people building or testing against out-of-date designs or documents.
- Makes it possible to know exactly what was delivered in each release.
- Lets the team roll back to a known good version.
- Supports audits, regulatory compliance and handover.
- Ensures approved changes from change control are reflected everywhere they should be.
Key terms
| Term | Meaning | Example |
|---|---|---|
| Configuration item (CI) | Any item placed under configuration control | A requirements document, a drawing, a software module, a server build |
| Version | A specific, identified state of a CI | Design spec v2.3 |
| Baseline | An agreed set of CI versions that serves as a reference point | Release 1.0 baseline; see project baseline |
| Release | A set of CIs delivered together | Portal release 1.2 |
| Configuration record | Information held about a CI | Owner, version, status, location |
The four core activities
- Identification: decide which items are CIs, how they are named and numbered, and how they relate.
- Control: make sure CIs change only through an approved process, and that versions are stored securely.
- Status accounting: record and report the current and historical state of each CI.
- Verification and audit: check that CIs match their records and that the delivered product matches the approved baseline.
Many organisations also add a planning step, documented in a configuration management plan.
Configuration register template
| CI ID | Name | Type | Version | Status | Owner | Location | Related CIs |
|---|---|---|---|---|---|---|---|
| CI-012 | Functional specification | Document | 2.3 | Approved | Business analyst | Project SharePoint | CI-020, CI-021 |
| CI-020 | Payments module | Software | 1.4.0 | In test | Dev lead | Git repository | CI-012 |
| CI-031 | Floor plan level 2 | Drawing | C | Issued for construction | Architect | Document control system | CI-030 |
| CI-040 | Test plan | Document | 1.1 | Draft | QA lead | Project SharePoint | CI-012, CI-020 |
Configuration management and change control
Change control decides whether a change happens. Configuration management makes sure the change is applied consistently and recorded. For example, if change request CR-04 adds single sign-on, configuration management identifies every affected CI (requirements, design, code modules, test cases, user guide), tracks their new versions and confirms the next release baseline contains them all.
Tips
- Only put items under control that need it; too many CIs creates bureaucracy.
- Use consistent naming and version numbering rules.
- Use tools that keep history automatically, such as version control systems and document management systems.
- Make baselines at meaningful points, such as design approval or release.
- Run a configuration audit before go-live and at project closure.
Free templates for this topic
Frequently asked questions
What is configuration management in project management?
The process of identifying, controlling, recording and verifying the versions of a project's products and documents.
What is a configuration item in configuration management?
Any component, document or product placed under configuration control, such as a specification, drawing or software module.
What are the four activities of configuration management?
Identification, control, status accounting, and verification and audit.
What is the difference between configuration management and change control?
Change control decides whether to make a change; configuration management tracks versions and ensures the approved change is applied and recorded correctly.
What is a configuration baseline in configuration management?
An agreed, recorded set of configuration item versions used as a reference point for further work.
What is status accounting in configuration management?
Recording and reporting the current and past status of configuration items and changes to them.
What is a configuration audit in configuration management?
A check that configuration items and records match each other and that the product matches its approved baseline.
Is version control the same as configuration management?
Version control is one part of it. Configuration management also covers identification, relationships, status reporting and audits.
Who is responsible for configuration management?
The project manager is accountable, but on larger projects a configuration manager or project support office often runs it.
Does PRINCE2 include configuration management?
Yes. PRINCE2 includes configuration management as part of how it handles change and issues.
Is configuration management only for software?
No. It is used in engineering, construction, defence and many other fields wherever versions of designs and products must be controlled.