Domain 3 of 3 · Chapter 3 of 8

Managing and Controlling Changes

Unlock the complete study guide + 1,040 practice questions across 16 full exams.

Bundled into the existing Project Management Professional premium course — no separate purchase.

14-day money-back guarantee — no questions asked.

Included in this chapter:

  • The integrated change control pipeline
  • Impact analysis and the board's disposition
  • Logging changes and communicating their status
  • Implementing approved changes and updating baselines
  • Change control in adaptive and hybrid delivery
  • Exam-pattern recognition

Change handling by delivery approach

Change handlingPredictiveAdaptiveHybrid
Routine reprioritizationFormal change request to the CCBProduct owner reorders the product backlogBacklog for adaptive parts; change request for predictive parts
Always needs formal change controlAny change to a scope, schedule, or cost baselineRelease scope, funding, or contract changesPredictive-part baselines plus release, funding, and contract changes
Who decidesChange control boardProduct owner within the release; CCB for release-level changesCCB for baselines; product owner for the backlog
Primary artifact updatedScope, schedule, and cost baselinesProduct backlog, then the release baseline if release scope changesBoth, matched to the component

Decision tree

Reprioritization within a committed adaptive release? Product owner reorders the product backlog Alters a baseline, release scope, funding, or contract? No change request; proceed under the plan CCB approves after impact assessment? Implement; update baselines and documents Record in change log; communicate status Yes No No Yes Yes No

Cheat sheet

  • Assess a change request's full impact before the board dispositions it
  • Only approved changes are implemented and then baselined
  • The change control board dispositions requests against the baselines
  • Every change request's disposition is recorded in the change log
  • Stakeholders are kept informed of pending change decisions
  • In adaptive delivery scope change is handled by reordering the backlog
  • Release, budget, or contract changes still require formal change control
  • Approved changes are reflected across all affected project documents
  • Configuration management keeps document versions controlled and traceable
  • A scope change affecting the schedule is routed through change control, not decided unilaterally
  • Undocumented scope creep is controlled by routing it through the change process

Unlock with Premium — includes all practice exams and the complete study guide.

Also tested in

References

  1. Scope change control Blog
  2. PMP Examination Content Outline (July 2026)
  3. Project Configuration Management
  4. Configuration management: help with controlling changes Blog
  5. The 2020 Scrum Guide Whitepaper