HKSM
Sprint Planning Meeting
A planning session held at the start of each Sprint to update the Sprint Backlog. For a month-long Sprint it is capped at eight hours and is split into two parts: first to agree on the Sprint Objective, then to break work into tasks and estimate them.
Key Points
- Occurs at the start of the Sprint and results in a clear Sprint Goal and an updated Sprint Backlog.
- Time-boxed to 8 hours for a one-month Sprint, scaling proportionally for shorter Sprints.
- Two segments: define the Sprint Objective, then decompose selected items into tasks with estimates.
- Product Owner clarifies priorities, Developers select and plan work, Scrum Master facilitates the event.
Example
At the beginning of a two-week Sprint, the team meets for about four hours. They select the highest-value backlog items, agree on a Sprint Goal to enable one-click checkout, and then break those items into tasks with hour estimates, updating the Sprint Backlog accordingly.
PMP Example Question
Which activity best describes what should happen during the Sprint Planning Meeting?
- Create a detailed release roadmap for the next three months.
- Agree on the Sprint Goal and decompose selected backlog items into estimated tasks.
- Review and approve the Definition of Done for the entire product.
- Conduct a full retrospective on the previous Sprint.
Correct Answer: B — Agree on the Sprint Goal and plan tasks for selected backlog items
Explanation: Sprint Planning focuses on defining the Sprint Objective and updating the Sprint Backlog by breaking selected work into estimated tasks within a fixed timebox.
