Change Management in : Assessing and Implementing Changes
PMBOK v8 Definition
Changes are modifications to any formally controlled project deliverable, document, or baseline. The process of assessing and implementing changes involves evaluating impact across scope, schedule, finance, resources, stakeholders, and risk, then executing integrated change control through approved change requests. This occurs within the Monitor and Control Project Performance focus area.
Why It Matters for the Exam
Change management appears in approximately 15-20% of PMI exam questions, typically in scenario-based items where you must determine the correct sequence of actions when a stakeholder requests a modification. Questions test your ability to distinguish between change request types, identify when integrated change control is required, and recognize the role of the change control board (CCB).
Key Points to Remember (for the exam)
- Main Inputs: Approved change requests, work performance reports, enterprise environmental factors, organizational process assets
- Main Outputs: Change requests (corrective action, preventive action, defect repair, updates), project management plan updates, project document updates, change log
- Key Tool: Integrated change control, change control tools, data analysis (alternative analysis, cost-benefit analysis), decision-making (voting, autocratic, multicriteria)
- Four Change Request Types: Corrective Action (brings performance back in line), Preventive Action (avoids future deviation), Defect Repair (fixes nonconforming product), Update (modifies baselines or documents)
- Change Request Statuses: Approved, Rejected, Deferred, or More Information Needed
- CCB Role: May be involved when applicable; approves or rejects changes after impact analysis
- Predictive vs Adaptive: In predictive approaches, changes are not formally controlled until baselines are established
Typical PMI Exam Example
During project execution, a key stakeholder requests adding a new feature to the product scope. The project manager must first assess the impact on scope, schedule, budget, and risks, then submit a formal change request to the CCB. If approved, the change is implemented and documented in the change log.
PMI Exam Traps
-
Trap: Confusing "Corrective Action" with "Preventive Action"
- Reality: Corrective Action fixes an existing deviation; Preventive Action avoids a potential future deviation
-
Trap: Thinking all change requests must go through the CCB
- Reality: Only changes affecting baselines require CCB approval; minor changes may be approved by the project manager
-
Trap: Implementing a change before formal approval
- Reality: Changes must be assessed, submitted, approved, then implemented—never implement before approval
-
Trap: Confusing "Change Request" as an output vs. input
- Reality: Change requests are both outputs (from Assess and Implement Changes) and inputs (to other processes)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Change Control Board (CCB) | Authority body | CCB approves/rejects changes; project manager submits requests |
| Change Log | Output document | Records all change requests, decisions, and status |
| Integrated Change Control | Key tool | Ensures changes are evaluated across all project constraints |
| Baselines (Scope, Schedule, Cost) | Affected by changes | Changes to baselines require formal CCB approval |
Quick Review Questions
- What are the four types of change requests in PMBOK v8?
- When should a change request be submitted to the CCB versus approved by the project manager?
- What is the difference between corrective action and preventive action?
- Which document records all change requests and their disposition?
- In predictive approaches, when are changes formally controlled?
PMBOK v8 Reference
Section 2.1.6.8 - Assess and Implement Changes (pages 28-30, 114-117, 151)