CAPM Practice: Determine how to plan project iterations
Question 21 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: Prioritize the product backlog by business value so the highest-value features are delivered in early sprints
Explanation
Value-first prioritization ensures that even if the project must end early (time runs out, budget exhausted, scope cut), the product contains its most valuable features. If a 6-sprint plan produces only 5 sprints of work, the product still delivers at least 5/6 of the planned value (more, in practice, since the lost sprint held the lowest-value features) — rather than 0/1 (all-or-nothing at project end, which predictive completion models risk).
**Why not A:** Completing lower-value features first inverts value-first prioritization. If time runs out, the features left undelivered would be the most critical ones — exactly the outcome the team wants to avoid.
**Why not C:** Technical dependencies should inform sequencing, but ordering purely by technical considerations does not ensure the most critical features arrive first. If the release is cut short, high-value features scheduled late for technical convenience would be lost.
**Why not D:** Spreading features evenly across sprints says nothing about which features come first. Without value-based ordering, an early stop could leave critical features unfinished while lower-value ones have already been built.
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