Posted in Scrum Events

Sprint Planning

“The work to be performed in the Sprint is planned at the Sprint Planning” (1)


Definition: Sprint Planning is a meeting involving the entire Scrum Team to collaboratively decide what work will be taken up for the Sprint and how the work will be done (2, pg 27)

Length: Maximum of 8 hours for a one-month Sprint

Input: Product Backlog, Definition of Done, Retrospective Improvements, Team Capacity Planning, Impediments, Product Increment

Outcome: Sprint Goal (The What) and Sprint Backlog (The Why)

People: Product Owner, Scrum Master, Development Team

By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment. (1)

What can be done this Sprint?

Product Backlog Items

  • The Development Team forecasts the functionality that will be developed during the Sprint for the Product Owner’s objective
  • The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. 

The Sprint Goal

Definition: The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment (1)

  • During Sprint Planning the Scrum Team also crafts a Sprint Goal
  • The Sprint Goal is one coherent function
  • The Sprint Goal means all the Development Team work together rather than on separates objectives
  • The Sprint Backlog items can be negotiated with the Product Owner whilst the Sprint Goal

How will the chosen work get done?

  • The Development team decides how it will deliver the selected Product Backlog Items for the Sprint
  • The Development Team designs the system and the work needed to convert the Product Backlog Items into an Increment
    • Just enough to forecast what it can do in the Sprint
    • Work for the first few days of the Sprint is broken down more
    • Work may be of varying size, or estimated effort
  • The Product Owner helps to clarify and negotiate the selected Product Backlog items
  • The Development Team may also invite people with specific expertise to support them

Sprint Backlog

Product Backlog Items + Plan = Sprint Backlog


Sprint Planning Facilitation Technique (3, page 128)



  1. The Scrum Guide
  2. Scrum Insights for Practitioners by Hiren Doshi
  3. Fixing Your Scrum by Ryan Ripley and Todd Miller

Explore Other Scrum Events

SprintDaily ScrumSprint ReviewSprint Retrospective

2 thoughts on “Sprint Planning

  1. Pingback: Scrum Theory

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s