Configuration Management
Configuration management is the collection of procedures used to track project artifacts and monitor and control changes to these artifacts, ensuring that the description and functional characteristics of deliverables remain accurate and complete.
Know it well enough for the exam? Questions on Configuration Management are scenario-based, not definitional.
Practice it freeExplanation
Configuration management ensures that the project's deliverables, documents, and other artifacts are consistently identified, controlled, and tracked throughout the project lifecycle. It is described in the configuration management plan, which is a component of the project management plan. Configuration management activities include identification (labeling and describing configuration items), status accounting (recording and reporting the status of each item), verification and audit (ensuring items match their documented descriptions), and change control (ensuring modifications follow the approved process).
In practice, configuration management answers the question: "What is the current approved version of this deliverable, and how did it get to this state?" This is essential for projects with many interconnected components where an untracked change to one component could cause failures in another. Version control systems, document management systems, and configuration management databases are common tools.
Configuration management works hand-in-hand with change control. While change control governs the process for evaluating and approving changes, configuration management ensures that once a change is approved and implemented, the deliverable's description and version are updated accordingly. Together, they maintain the integrity and traceability of all project artifacts.
Key Points
- •Tracks the state and version of all project artifacts and deliverables
- •Includes identification, status accounting, verification/audit, and change control activities
- •Described in the configuration management plan within the project management plan
- •Works alongside change control to maintain deliverable integrity and traceability
Exam Tip
Configuration management focuses on the "what" — the state of deliverables and artifacts. Change control focuses on the "how" — the process for reviewing and approving changes. The exam tests this distinction.
Frequently Asked Questions
Related Topics
Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests, approving or rejecting changes, managing changes to deliverables, project documents, and the project management plan, and communicating the decisions.
Change Log
A change log is a comprehensive list of all change requests submitted during the project, along with their current status (approved, rejected, or deferred) and key details.
Project Management Plan
The project management plan is the document that describes how the project will be executed, monitored and controlled, and closed.
Project Artifacts
Project artifacts are any templates, documents, outputs, or deliverables produced during the project. They encompass all tangible and documented items created through project activities.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Part of
Integration Management
Practice Configuration Management
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.