Skip to content
PMPCAPM

Sprint Planning

Sprint Planning is the Scrum event that initiates each Sprint by defining the Sprint Goal, selecting Product Backlog items to work on, and creating an actionable plan for delivering the Increment.

Explanation

Sprint Planning addresses three topics: why the Sprint is valuable (the Sprint Goal), what can be done during the Sprint (selecting backlog items), and how the chosen work will get done (creating a plan). The entire Scrum Team collaborates in Sprint Planning, and the Product Owner ensures the most important items are ready for discussion.

The Sprint Goal is crafted during Sprint Planning and gives the team a coherent objective. The Developers then select items from the Product Backlog that they forecast they can complete. This selection is based on past performance (velocity), current capacity, and the Definition of Done. The Developers decompose the selected items into tasks and create the Sprint Backlog.

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The quality of Sprint Planning directly impacts the team's ability to deliver a valuable Increment.

Key Points

  • Addresses why (Sprint Goal), what (selected items), and how (plan for delivery)
  • Timeboxed to eight hours maximum for a one-month Sprint
  • The entire Scrum Team participates
  • Results in the Sprint Backlog with a clear Sprint Goal

Exam Tip

Sprint Planning produces three outputs: the Sprint Goal, the set of selected Product Backlog items, and the plan for delivering them. Know all three.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.