PMP Choosing Response Options for Scope and Backlog Changes
March 26, 2026
Study PMP Choosing Response Options for Scope and Backlog Changes: key concepts, common traps, and exam decision cues.
On this page
Scope response options matter because the external change itself is rarely the final decision. The project manager still has to recommend what the project should do about it. PMP questions here usually test whether the response options are realistic, balanced, and routed through proper control.
Response Options Should Fit the Type of Impact
Once the project understands the external impact, several options may be possible:
accept the impact and continue
re-sequence work
reduce or defer scope
request more time or budget
redesign a deliverable
split a release
raise a formal change request
The best option depends on which constraint is being pressured and whether the change affects compliance, viability, or benefit realization.
Strong Recommendations Show Tradeoffs
The PMP exam often rewards the answer that recognizes tradeoffs openly. If the team keeps all scope despite an external disruption, schedule or cost may move. If the team protects date and cost, some scope or quality activity may have to change.
Good recommendations show:
what changes
what stays protected
what risk remains
what governance step is required
A weak response offers only one attractive-sounding action without showing its consequence.
Route the Recommendation Through the Right Control Path
Some options can be handled within team-level replanning. Others require sponsor agreement, governance review, or formal change control. The project manager should recommend the option and the approval path together.
For example, deferring lower-value backlog items in an adaptive setting may stay within normal prioritization authority. Altering approved scope on a compliance-sensitive release may require formal change authorization.
Example
A new external reporting requirement adds mandatory work to the release. The project manager might recommend three options: move the release date, defer a lower-value feature, or request additional budget for accelerated compliance work. The strongest recommendation explains the tradeoff and identifies which option can actually be approved within the current governance model.
Common Pitfalls
Presenting only one option when real tradeoffs exist.
Recommending a change without stating what constraint moves.
Treating all scope changes as informal backlog adjustments.
Ignoring benefits when balancing scope, cost, and schedule.
Check Your Understanding
### Which action best matches this task?
- [x] Present realistic response options, clarify tradeoffs, and identify the right approval path
- [ ] Recommend one preferred option without showing consequences
- [ ] Assume every scope change can be handled informally
- [ ] Delay options analysis until stakeholders align on their own
> **Explanation:** Strong recommendations show alternatives, tradeoffs, and control implications.
### Which recommendation is strongest after a new external compliance requirement adds work?
- [ ] Keep everything unchanged and ask the team to work faster
- [x] Offer tradeoff options such as date movement, scope deferral, or additional funding, then route the decision properly
- [ ] Remove compliance work because it was not in the original backlog
- [ ] Hide the impact until the next status meeting
> **Explanation:** The best response acknowledges the new work and makes the tradeoffs visible.
### What is the weakest scope-response habit?
- [ ] Explaining what each option protects or sacrifices
- [ ] Matching the recommendation to governance requirements
- [x] Treating a major approved-scope change as if it were only a task-level update
- [ ] Linking the recommendation to benefits and release viability
> **Explanation:** Major scope implications often require more than informal replanning.
### Why should a response recommendation mention tradeoffs?
- [ ] So the project can avoid making a decision
- [ ] So every stakeholder gets a different answer
- [ ] So the team can skip change control
- [x] So decision makers understand what cost, schedule, scope, or benefit consequence each option creates
> **Explanation:** Tradeoffs make recommendations usable and governable.
Sample Exam Question
Scenario: A project learns that an external supplier restriction will add four weeks to the procurement path for a component needed in the next release. The sponsor wants the launch date protected if possible. The product owner wants all planned features retained. The governance board expects the project manager to return with response options, not just bad news.
Question: What is the best immediate response?
A. Recommend realistic options such as resequencing, feature deferral, or date movement, and explain the tradeoffs and approval path for each
B. Ask the team to absorb the delay without changing any target, scope, or funding assumption
C. Remove scope immediately without consulting governance because the supplier issue came from outside the project
D. Wait until the delay actually occurs before discussing response options
Best answer: A
Explanation:A is strongest because it turns the external impact into governable choices. The project manager should not simply report the disruption. The project manager should show credible options, the constraint tradeoffs each option creates, and which decision path is needed to approve the response.
Why the other options are weaker:
B: This hides the tradeoff instead of managing it.
C: A unilateral major scope reduction may violate governance and stakeholder agreements.
D: Waiting reduces available response room.
Key Terms
Response option: A practical path the project could take after an external impact is understood.
Tradeoff statement: A clear explanation of what each option changes or protects.
Approval path: The governance route needed to authorize a selected response.