Skip to content
PMPEasy

PMP Practice: Break down scope (e.g., WBS, backlog)

Question 2 of 5 in Plan and Manage Scope

Cedar Petersen is developing an automated warehouse system using a hybrid approach. The first three sprints will focus on core navigation software using adaptive methods, while the physical robot assembly follows a predictive schedule. The product owner from the operations team has submitted a list of 47 requirements ranging from 'robots must avoid obstacles' to 'dashboard should display battery levels in purple.' The development team is confused about which requirements to address first, and several requirements conflict with each other. The project manager needs to ensure the team focuses on the most valuable work. Which approach would be MOST effective for determining and prioritizing these requirements?
Show answer & explanation

Correct answer: Facilitate a collaborative workshop with the product owner, development team, and key operations stakeholders to review requirements, clarify priorities using value-versus-effort analysis, and create a prioritized backlog

Explanation

In a hybrid environment where requirements need to be prioritized for adaptive delivery, collaborative prioritization workshops are most effective. This approach brings together the product owner who owns priority decisions, the development team who understands technical feasibility and effort, and key stakeholders who can clarify business value and resolve conflicts. Value-versus-effort analysis helps the group make informed tradeoff decisions and ensures everyone understands why certain requirements are prioritized. The resulting prioritized backlog gives the team clear direction while maintaining the flexibility needed for adaptive work. This collaborative approach prevents misunderstandings, surfaces hidden dependencies, and builds shared commitment to the priorities.

**Why not B:** While the product owner should own prioritization decisions, asking them to rank 47 items in isolation without team input on effort or technical dependencies will likely result in unrealistic priorities that don't account for implementation complexity or conflicting requirements.

**Why not C:** Individual stakeholder meetings and a requirements traceability matrix are more appropriate for predictive environments with stable requirements. This approach is time-consuming, doesn't resolve the conflicts mentioned in the scenario, and misses the collaborative prioritization essential for adaptive delivery.

**Why not D:** While safety-critical requirements are important, having the project manager unilaterally direct implementation priorities bypasses the product owner's role and ignores the team's input on feasibility. The scenario indicates requirements conflict with each other, which this approach doesn't address.

Key Concept

This question covers Break down scope (e.g., WBS, backlog) under Plan and Manage Scope (Process).

Share:

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