Change Control: The Formal Process for Managing Modifications

PMBOK v8 Definition

Change control is a process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected. A change is defined as a modification to any formally controlled deliverable, project management plan component, or project document. The change control board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions.

Why It Matters for the Exam

Change control appears frequently in PMI exam questions because it is a critical governance mechanism that protects project baselines from unauthorized modifications. Expect questions testing your understanding of the CCB's authority, the difference between change control and configuration control, and the proper sequence of the change control process in scenario-based questions.

Key Points to Remember (for the exam)

• Main Input: Change requests (formal proposals to modify a document, deliverable, or baseline)
• Main Output: Change log updates (disposition of all change requests is recorded here)
• Key Plan: Change management plan (component of the project management plan that establishes the CCB and documents its authority)
• Key Entity: Change control board (CCB) – formally chartered group for reviewing, evaluating, approving, delaying, or rejecting changes
• Common Confusion: Change control vs. configuration control – configuration control focuses on specifying deliverables and processes, while change control focuses on identifying, documenting, and approving/rejecting changes to documents, deliverables, or baselines
• Key Distinction: Change requests may be initiated internally OR externally to the project
• Critical Output: The disposition of all change requests (approved, rejected, or delayed) is recorded in the change log

Typical PMI Exam Example

A project manager receives a request from a key stakeholder to add a new feature to the project deliverable. The feature would require modifying the scope baseline. The project manager should first submit a formal change request to the change control board for evaluation and disposition, not implement the change directly.

PMI Exam Traps

• Trap: Thinking the project manager can approve all changes

• Reality: Only the CCB has authority to approve changes that affect baselines; the project manager may approve changes within defined thresholds

• Trap: Confusing change control with change management

• Reality: Change control is the process for reviewing and approving/rejecting changes to project documents and baselines; change management is a comprehensive, cyclic approach for transitioning people from current to future state

• Trap: Assuming all change requests are approved

• Reality: Change requests can be approved, rejected, or delayed; all dispositions are recorded in the change log

• Trap: Implementing changes before formal approval

• Reality: No modification to formally controlled deliverables, plans, or documents should occur without proper change control process and CCB approval

Important PMI Connections

Quick Review Questions

1. What is the difference between a change and a change request according to PMBOK v8?

2. Who is responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project?

3. Where is the disposition of all change requests recorded?

4. What document establishes the change control board and documents its authority?

5. Can change requests be initiated by parties external to the project?

PMBOK v8 Reference

Section 4.6 – Change Control (from PMBOK v8 Glossary and related process descriptions)