CAPM Practice: Determine how to plan project iterations

Sprint planning results in two key outputs: (1) a sprint goal (what value the sprint will deliver) and (2) the sprint backlog (which product backlog items the team will work on and how). The team decides how much they can take on based on their velocity and capacity. Sprint planning sets the direction and commitment for the upcoming time box.

**Why not A:** Assigning individual tasks to team members is antithetical to Scrum's self-organizing team principle — the Scrum Master facilitates the process but does not direct individual work. In Scrum, the team collectively decides who will pick up which tasks during the sprint, often on a pull basis from the sprint backlog. Top-down task assignment by a Scrum Master would undermine team autonomy and accountability.

**Why not C:** Sprint planning addresses only the upcoming sprint, not a multi-month release horizon. Long-range planning occurs in release planning sessions or through product roadmap discussions, not within the time-boxed sprint planning ceremony. Conflating sprint planning with release planning would produce unworkable meetings and unclear outputs.

**Why not D:** Reviewing completed work with stakeholders is the purpose of the Sprint Review, not sprint planning. These are two distinct Scrum events with separate purposes — sprint planning looks forward while the sprint review looks backward at the work just completed. Combining them would eliminate the retrospective accountability that the sprint review provides.