CAPM Practice: Determine how to plan project iterations
Question 2 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: A fixed-length time box (typically 1-4 weeks) within which a potentially releasable increment is produced
Explanation
A sprint is a fixed-length, time-boxed event (1-4 weeks, typically 2 weeks) during which the team works to complete the sprint backlog and produce a Done increment. Sprints have a fixed start and end date; the sprint ends on schedule regardless of completion. Each sprint is a complete mini-project cycle: plan, execute, review, retrospect.
**Why not A:** A sprint is not a planning session. Sprint planning is an event held at the start of each sprint, but the sprint itself is the full time-boxed container for planning, development, review, and retrospective—and it is not tied to project phases.
**Why not B:** A sprint involves the whole Scrum team working together toward the sprint goal, not a subset of the fastest team members. How fast individuals work has nothing to do with what a sprint is.
**Why not C:** A sprint is not the team's daily or weekly work schedule. It is a fixed-length time box, commonly 1-4 weeks, that ends with an increment; day-to-day coordination happens in the daily scrum within the sprint.
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