Manage Project Changes
Introduction: Why This Matters
Change is inevitable. Stakeholders refine requirements, regulations evolve, risks materialize, and technology advances. While change itself is not harmful, uncontrolled change threatens scope, cost, schedule, and quality. Effective change management ensures that all modifications are evaluated, approved, documented, and communicated within the project governance framework.
On the PMP exam, change-related scenarios are common. The correct answers emphasize integrated change control. This means structured evaluation, formal approval, and proper updating of baselines, not informal adjustments or unilateral decisions.
Purpose and Objectives
Primary Purpose: Ensure project changes are managed systematically, protecting the integrity of baselines while allowing beneficial adjustments.
Key Objectives:
- Apply integrated change control processes.
- Evaluate change requests for impact on scope, schedule, cost, quality, and risk.
- Facilitate governance approval through the Change Control Board (CCB).
- Update baselines and communicate approved changes.
- Maintain alignment across all subsidiary plans after changes.
Overview
Managing project changes is about applying governance so the project remains controlled, aligned, and realistic as new information emerges.
- Control: No changes are implemented without evaluation and approval.
- Clarity: Decisions are documented and communicated to prevent confusion.
- Consistency: Approved changes update baselines and all impacted plans.
Characteristics
- Structured: Uses a defined process from request through decision and implementation.
- Impact-Based: Requires analysis across scope, schedule, cost, quality, resources, and risk.
- Governed: Uses formal authority and decision-making, often through the CCB.
- Baseline-Protecting: Prevents scope creep by ensuring changes do not bypass approval.
Practical Example
Context: A project implementing a new airport security system receives a stakeholder request for an additional reporting feature.
Activities:
- Logged the request: Documented the change in the change log.
- Analyzed impacts: Found the feature adds two weeks to the schedule and increases cost by $50,000.
- Presented for review: Submitted the request to the Change Control Board.
- Updated the plan: After approval, updated baselines and project documents.
- Communicated: Shared the decision and next steps with stakeholders.
Outcome: The change is integrated systematically, expectations are aligned, and governance is maintained.
Common Pitfalls
- Approving changes informally, leading to scope creep.
- Skipping impact analysis, making uninformed decisions.
- Failing to update baselines, leaving plans inconsistent.
- Not communicating decisions, causing stakeholder confusion.
- Rejecting all changes automatically, missing opportunities for value.
Sensei Tip : In PMP change scenarios, your first move is almost never “do the change.” Your first move is to log it, analyze it, and route it through governance.
Exam Alert : The exam loves traps where a stakeholder asks for a “small change.” If you implement it informally, that is scope creep. Always route changes through integrated change control.
Exam Lens
Patterns on the PMP Exam:
- Correct answers emphasize formal processes and governance.
- Look for impact analysis, documentation, and CCB review.
- Avoid answers that implement changes informally, skip evaluation, or reject without analysis.
Sample Question
Question: A key stakeholder requests a feature addition during project execution. What should the project manager do first?
- Approve the change immediately to maintain stakeholder satisfaction.
- Reject the change to prevent scope creep.
- Document the request, perform an impact analysis, and submit it to the Change Control Board.
- Delay evaluation until project closure.
Correct Answer: C. The project manager must log the change, analyze its impacts, and submit it for formal review. Informal approval, blanket rejection, or delay violates proper change control.
Quick Recap Table
| Concept | Description | Exam Watch Point |
|---|---|---|
| Integrated Change Control | Formal evaluation and approval of changes | Always document and analyze |
| Impact Analysis | Assess effect on scope, cost, schedule, risk, quality | Exam favors structured evaluation |
| CCB | Governance body for decision-making | Do not bypass CCB |
| Configuration vs Change Control | Configuration = deliverables. Change = baselines | Watch for terminology |
| Pitfalls | Informal changes, no analysis, no updates | Avoid shortcuts |
Key Takeaways
- Change is inevitable, but it must be managed through formal integrated change control.
- Impact analysis precedes decision-making.
- Approved changes update baselines and are communicated transparently.
- Exam scenarios reward structured, governance-driven change management.
- In practice, disciplined change control protects scope, cost, schedule, and stakeholder trust.
Next Step
We will now move to Task 11: Plan and Manage Procurement, where you will learn how to acquire and oversee external products and services that support project delivery.
Bibliography
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.