CAPM Practice: Determine how to plan project iterations
Question 59 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: Organizing user stories by user journey to determine logical release slices and iteration sequences
Explanation
Story mapping arranges user stories along two axes — the user's workflow (horizontal) and detail/priority (vertical). This helps teams identify logical minimum viable product (MVP) slices and plan iterations in a way that delivers end-to-end user value.
**Why not A:** Story mapping is not a costing technique. It organizes stories by user workflow and priority; estimating effort or cost is done separately through estimation and budgeting practices.
**Why not C:** Story mapping is a forward-looking planning tool used to decide what to build and in what order, not a way to archive completed stories.
**Why not D:** Story mapping does not assign work to individuals. In agile teams, members self-organize around the work during the iteration rather than having stories pre-assigned by expertise.
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