CAPM Practice: Determine how to plan project iterations
Question 25 of 61 in Determine how to plan project iterations
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: The small 'must have' item — high business need + small effort = high priority in any value-based framework
Explanation
Value-based prioritization considers both value delivered and cost (effort) to deliver it. A 'must have' item with 5 story points has an extremely high value-to-effort ratio — it delivers critical value for minimal cost. A 'nice to have' item at 200 points is low value but high cost. Prioritizing by value/effort ratio would place the small 'must have' first and potentially indefinitely defer the large 'nice to have.'
**Why not A:** Placing both items in the same sprint because they 'balance each other' is not a prioritization principle. A 200-point item is unlikely to fit in a single sprint alongside other work, and bundling it with the 'must have' risks delaying the high-value item rather than ordering work by value relative to effort.
**Why not B:** Demonstrating team capability is not a value-based criterion. Backlog ordering aims to maximize business value delivered to stakeholders, not to showcase technical skill — and a 'nice to have' item is, by definition, lower value.
**Why not C:** Story points measure relative effort, not value. A larger point estimate means a higher cost to deliver, which lowers an item's priority in a value-to-effort comparison rather than raising it.
Key Concept
This question covers Determine how to plan project iterations under Determine how to plan project iterations (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free