PMP Practice: Break Down Scope
Question 11 of 14 in Develop and Manage Project Scope
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Facilitate a backlog refinement session with Dante and the development team to collaboratively split the stories into smaller increments, prioritize based on client value, and identify which stories deliver the most immediate benefit while deferring complex API work to future sprints
Explanation
In agile projects, scope agreement is achieved through collaborative backlog refinement where the product owner and development team work together to understand new work, break it into manageable pieces, and prioritize based on value and capacity. The scenario reveals that seven stories exceed the team's demonstrated velocity and introduce technical complexity not previously planned. The most effective approach is to facilitate a conversation where Dante and the team jointly decompose the work, identify which stories deliver the highest value to the retail clients, and create a realistic plan that fits the sprint capacity. This collaborative technique ensures everyone understands the tradeoffs, maintains the team's sustainable pace, and focuses on incremental value delivery rather than attempting to absorb all scope at once. The closing fact that the team can only handle four to five stories per sprint makes it clear that some form of prioritization and decomposition is required, and collaborative refinement is the standard agile practice for achieving stakeholder agreement in this situation.
**Why not A:** Asking the product owner for written justification and escalating to the sponsor introduces formal approval processes that are unnecessarily bureaucratic for agile scope discussions. In agile, the product owner has authority to adjust backlog priorities, and the PM should facilitate collaboration between the PO and team rather than adding approval gates.
**Why not C:** Scheduling a meeting directly with retail clients bypasses the product owner's role as the voice of the customer. The product owner is responsible for understanding and representing customer needs. Going around the PO to the clients undermines their authority and creates confusion about who speaks for customer requirements.
**Why not D:** Accepting all seven stories despite exceeding demonstrated velocity of 4-5 stories per sprint would result in overcommitment. Adjusting the sprint goal mid-sprint if velocity issues emerge means the team has already committed to unrealistic work and must abandon commitments later. This reactive approach damages team credibility and stakeholder trust.
Key Concept
This question covers Break Down Scope under Develop and Manage Project Scope (Process).
This is 1 of 100 free PMP questions
Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.
Unlock All Questions