Development Approach & Life Cycle

Lesson 5 of 6

Change Control vs Backlog Reprioritization

Learn the exam's most-tested life-cycle distinction—when to use formal change control versus collaborative backlog moves.

The Distinction That Decides Hundreds of Questions

Predictive environments use integrated change control to protect baselines. Agile environments use transparent backlog prioritization with the product owner and team. Hybrid environments may use both—formal control at release boundaries and adaptive prioritization inside iterations. Choosing the wrong mechanism is one of the most common exam errors.

Change Control vs Backlog Move

Use Formal Change Control When

  • Approved baselines (scope, schedule, cost) are affected.
  • Contract terms or regulatory commitments are impacted.
  • Cross-project dependencies require authorized realignment.
  • Funding or resource allocations must be formally updated.

Use Backlog Reprioritization When

  • The stem describes sprints, iterations, or product backlog.
  • Value ordering is shifting but iteration guardrails apply.
  • The team and product owner can trade work within capacity.
  • Learning from demos drives the next increment focus.

Decision Checklist

  1. 1Identify delivery model cues in the stem first.
  2. 2Ask whether baselines or contracts are implicated.
  3. 3If predictive: document impact and route through change control.
  4. 4If agile: collaborate on prioritization and protect sprint integrity.
  5. 5If hybrid: apply formal control at the boundary, adaptive moves inside.

Wrong-Mechanism Traps

  • CCB submission for a routine backlog refinement in a sprint context.
  • Silent scope addition in a predictive phase without impact analysis.
  • Rebaselining in agile language without stakeholder collaboration.
  • Ignoring contract impact because the team prefers to 'stay agile'.
Exam Scenario

A product owner asks for a high-value feature during sprint week two. In agile, you facilitate impact discussion and prioritization—not a CCB packet. In predictive, the same request during execution likely triggers integrated change control.

PMP Decode Rule

Match the change mechanism to the delivery model in the stem.

Practice this topic

Reinforce this lesson with scenario questions tagged Change Control, Requirements, Stakeholders.

Go to Practice