Sprint Planning Explained: Why, What and How

Sprint Planning is the event that starts a new Sprint. The Scrum Team collaborates to decide why the Sprint is valuable, what can be accomplished, and how the selected work will be done.

Sprint Planning focuses on three questions: Why, What and How.

1. Why Is This Sprint Valuable?

The first topic is to understand why the Sprint is valuable.

The Product Owner proposes how the product could increase its value during the Sprint. The Scrum Team then collaborates to define a Sprint Goal.

Why?

What valuable outcome are we trying to achieve during this Sprint?

2. What Can Be Done This Sprint?

The Developers work with the Product Owner to select Product Backlog items that can contribute toward the Sprint Goal.

The Developers consider factors such as their capacity, previous performance, the Definition of Done and their understanding of the work.

What?

Which Product Backlog items can realistically be completed during the Sprint?

3. How Will the Work Get Done?

The Developers plan the work required to create an Increment that meets the Definition of Done.

The Developers decide how the selected work will be accomplished. The Scrum Master does not assign tasks to individual Developers.

How?

How will we turn the selected work into a usable Increment?

The Sprint Goal

The Sprint Goal is the objective for the Sprint. It gives the Scrum Team a shared purpose and helps guide decisions during the Sprint.

A good Sprint Goal focuses on an outcome rather than simply listing a collection of tasks.

What Is the Sprint Backlog?

The Sprint Backlog consists of:

  • The Sprint Goal
  • The selected Product Backlog items
  • The plan for delivering the Increment

It is the Developers' plan for achieving the Sprint Goal.

Who Participates?

Sprint Planning involves the entire Scrum Team:

  • Product Owner — helps explain product value and the important Product Backlog items.
  • Developers — select the work and plan how it will be accomplished.
  • Scrum Master — helps ensure the event takes place and that participants understand its purpose.

Simple Example

Imagine a team developing an online shopping application.

The Product Owner wants the next Sprint to make checkout easier for customers.

The team may define the Sprint Goal as:

"Improve the checkout experience so customers can complete purchases more easily."

The Developers then select suitable Product Backlog items and create a plan for delivering the Increment.

Scrum Master's Role During Sprint Planning

The Scrum Master should not run the meeting like a traditional project manager.

Instead, the Scrum Master helps the team understand the purpose of Sprint Planning, facilitates useful discussions when needed, and helps keep the event focused.

Remember:

Sprint Planning is not about assigning tasks. It is about creating a shared understanding of Why, What and How for the Sprint.

Timebox

Sprint Planning has a maximum duration of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

What Comes Next?

In the next lesson, we will look at the Daily Scrum and understand how Developers inspect progress toward the Sprint Goal and adapt their plan.

Next Lesson
Daily Scrum Explained