Tools: Configuration Control vs. Change Control for Deliverables

PMBOK v8 Definition

Configuration control focuses on specifying both deliverables and processes, while change control is concerned with identifying, documenting, and approving or rejecting changes to project documents, deliverables, or baselines. Both manual and automated tools can be utilized to facilitate configuration and change management, with tool selection based on the needs of project stakeholders, considering organizational and environmental constraints.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your ability to distinguish between configuration management activities (specifying and verifying deliverables) and change management activities (approving/rejecting changes). Expect scenario-based questions where you must identify which tool or activity applies to a specific project situation, particularly in the Monitoring and Controlling Process Group.

Key Points to Remember (for the exam)

• Configuration Control Focus: Specifying both deliverables and processes, identifying configuration items, recording and reporting their status, and performing configuration item verification and audits
• Change Control Focus: Identifying and selecting change items, documenting changes into proper change requests, and deciding on changes by reviewing, approving, rejecting, or deferring them
• Common Confusion: Configuration control ensures the product definition is correct and verified; change control manages the decision process for proposed modifications
• Key Activities Supported: Configuration management includes verification and audits; change management includes tracking that changes are registered, assessed, approved, and communicated to stakeholders
• Tool Selection Criteria: Based on stakeholder needs, considering organizational and environmental constraints
• Integrated Change Control: Ensures changes are managed in a coordinated and controlled manner by evaluating change requests, conducting impact analyses, making informed decisions, and documenting and communicating changes

Typical PMI Exam Example

A project manager receives a stakeholder request to modify a deliverable's specifications. The project manager first uses configuration control tools to verify the current product configuration, then uses change control tools to document the request, assess its impact, and obtain approval before implementing the change. This demonstrates the coordinated use of both tool types.

PMI Exam Traps

• Trap: Confusing configuration control with change control

• Reality: Configuration control specifies and verifies deliverables/processes; change control manages the approval/rejection of changes

• Trap: Thinking manual tools are outdated and only automated tools are acceptable

• Reality: PMBOK v8 explicitly states both manual and automated tools can be utilized

• Trap: Assuming configuration management only applies to product deliverables

• Reality: Configuration control focuses on both deliverables AND processes

• Trap: Believing change control tools only handle approval decisions

• Reality: Change control tools also track that changes are registered, assessed, approved, AND communicated to stakeholders

Important PMI Connections

Quick Review Questions

1. What is the primary difference between configuration control and change control in PMBOK v8?

2. Which specific activities are supported by change control tools according to PMBOK v8?

3. A project team needs to verify that a deliverable matches its approved specifications. Which type of tool should they use?

4. What factors should guide the selection of change control tools for a project?

5. How does integrated change control ensure changes maintain alignment with project objectives?

PMBOK v8 Reference

Section 2.6 - Manage Project Execution Inputs, Tools and Techniques, and Outputs (Change control tools subsection)