Sprint Planning is a collaborative ceremony in Scrum and Agile frameworks where teams define what work will be accomplished during the upcoming sprint and how that work will be achieved. Held at the beginning of each sprint, this time-boxed event brings together the Product Owner, Scrum Master, and Developers to select items from the product backlog, estimate effort, and create a plan that commits to delivering a potentially shippable increment. The 2020 Scrum Guide expanded Sprint Planning to answer three critical questions: Why is this sprint valuable (Sprint Goal), What can be delivered (Sprint Backlog), and How will the work get done (task breakdown and capacity) — and introduced the Product Goal as the longer-term objective that Sprint Goals contribute toward. Understanding how to conduct effective Sprint Planning prevents overcommitment, surfaces risks early, and creates shared understanding across the team — turning strategic vision into actionable, time-boxed execution.
What This Cheat Sheet Covers
This topic spans 10 focused tables and 80 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Core Concepts
| Concept | Example | Description |
|---|---|---|
4-hour session for a 2-week sprint | • Time-boxed event where the Scrum Team selects work from the product backlog and creates a plan to deliver a potentially shippable increment • maximum 8 hours for a one-month sprint, proportionally shorter for shorter sprints. | |
"Complete user authentication feature" | • Single objective that unifies the team's work during the sprint • created collaboratively during Sprint Planning • provides focus and flexibility — the team can adjust tasks as long as the goal is met. | |
"Become the leading e-commerce platform for handmade goods" | • Long-term objective introduced in the 2020 Scrum Guide • serves as the commitment for the Product Backlog — Sprint Goals are stepping stones toward it. | |
Prioritized list of 50+ user stories | • Ordered list of everything needed for the product • owned and maintained by the Product Owner • source from which Sprint Backlog items are selected during planning. | |
15 user stories + tasks for a 2-week sprint | • Subset of Product Backlog items selected for the current sprint plus a plan for delivering them • owned by Developers • updated daily throughout the sprint. |