PMP · Question #36
A company just started managing a project using an agile approach. Due to this change, the general manager is worried about the scope definition process for upcoming projects. What should the project
The correct answer is D. Help sponsors and stakeholders craft the product vision, and bring the team and product owner. To ensure scope clarity in an agile environment, the project manager should help sponsors and stakeholders define the product vision, and engage the team and product owner in iteratively refining the product backlog.
Question
Options
- AMeet with the general manager and convince them to return to using predictive approaches to
- BAsk the general manager to review every requirement to ensure all projects will deliver the
- CAsk for a budget increase to implement a double-check process to ensure every business need is
- DHelp sponsors and stakeholders craft the product vision, and bring the team and product owner
How the community answered
(46 responses)- A2% (1)
- B11% (5)
- C4% (2)
- D83% (38)
Why each option
To ensure scope clarity in an agile environment, the project manager should help sponsors and stakeholders define the product vision, and engage the team and product owner in iteratively refining the product backlog.
Reverting to predictive approaches undermines the company's decision to adopt agile and doesn't address how to manage scope within an agile framework.
Asking the general manager to review every requirement is a micro-managing approach, counterproductive to agile principles, and unsustainable for complex projects.
Requesting a budget increase for a "double-check" process does not align with agile's iterative and continuous feedback mechanisms for scope management.
In agile, scope is not "completely defined" upfront but rather progressively elaborated. The project manager ensures scope clarity by facilitating the creation of a clear product vision with sponsors and stakeholders, and by empowering the product owner and development team to prioritize and refine the product backlog iteratively, which represents the current understanding of the scope.
Concept tested: Agile Scope Management and Product Vision
Source: https://www.pmi.org/agile/agile-guide/agile-practice-guide-introduction#product-vision
Topics
Community Discussion
9
Carlos M.Apr 27, 2026D is the right call. In agile the scope is defined through the product vision and ongoing collaboration, not a giant upfront requirements doc. Getting sponsors and stakeholders aligned on the vision while the team and product owner work the backlog is exactly how scope gets fleshed out iteratively. A, B, and C all drag you back to predictive habits or add useless overhead.
Dervla O.Apr 30, 2026Agree on D but flag that the product vision still needs to be concrete enough to baseline against, or scope creep hides behind the word iterative.
Fatima Z.May 4, 2026D is the answer and I locked it in on my exam last month. Think VISION = V, I, S, I, O, N: Volunteers In Scrum Include Owners Naturally. In agile you do not chase a perfect upfront scope, you build it iteratively through a shared product vision crafted by sponsors, stakeholders, the team, and the product owner. A, B, and C all smell like predictive thinking, so picture a big net catching a fuzzy vision instead of a rigid checklist. Sticky tip: the word craft is your clue, because agile scope is sculpted, not stamped
Carlos M.May 6, 2026Agree on D, and the craft keyword is a solid tell, but on my exam the real trap was C because it mentions stakeholders which sounds agile-friendly, so make sure you read the full option before jumping.
Yuki V.Apr 13, 2026Leaned toward A at first, but agile scope comes from product vision, so D.
Dervla O.Apr 13, 2026D is right, but keep the distinction sharp on exam day: vision sets direction, backlog is the actual scope artifact they will try to trip you on.
Bao N.Apr 9, 2026D confirmed. Vision plus product owner collaboration is how agile scope gets defined.
Carlos M.Apr 9, 2026Agreed on D but the real giveaway in the stem is shared responsibility, not just collaboration, since vision alone is backlog work and scope in agile is negotiated iteratively.
Dervla O.Apr 20, 2026Leaned toward B at first, but D is the agile move: vision drives scope, not sign-offs.