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.
Explanation
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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
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.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Part of
Integration Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.