# Sprint Planning and Backlog

> How Sprint Planning starts each sprint by asking why, what and how. How it makes the Sprint Goal and the Sprint Backlog, and how long it may take.

**Course:** [Agile, Scrum and Kanban](https://learn.benibix.com/learn/business-agile)  
**Time:** 11 min

**After this lesson you can:**

- Name the three topics of Sprint Planning
- Write a Sprint Goal
- Say who owns the Sprint Backlog

## How a sprint is planned

Sprint Planning is the meeting that starts each sprint. The whole Scrum Team answers three questions. Why is this sprint worth doing? What can be done in it? How will the chosen work get done? For a one-month sprint it takes up to 8 hours. Shorter sprints usually need less.

Why comes first, and its answer is the Sprint Goal. It is one aim for the sprint, such as let a reader pay with a card. The Product Owner brings an idea of what would add the most value. The whole team shapes the goal together.

What comes next. The Developers pick items from the top of the Product Backlog that serve the goal. They decide how much fits, using how much they finished in past sprints and how many people are free. Only they can say how much they can do.

How comes last. The Developers break each item into smaller pieces of work, often a day or less each. Nobody tells them how. The goal, the chosen items and this plan together make the Sprint Backlog.

The Sprint Backlog is the plan by the Developers, for the Developers. They own it and change it every day as they learn more. Its commitment is the Sprint Goal. The items can shift during the sprint, but the goal holds.

If the goal stops making sense, say a law changes or a client drops out, only the Product Owner can cancel the sprint. That is rare. Most surprises are handled by changing the plan, not by throwing the sprint away.

The common mistake is a sprint with no real goal, just a list of unrelated items. Then the team cannot tell which item to drop when time runs short. A clear goal makes that choice easy: keep what serves it.

## The three topics of Sprint Planning

1. **Why.** Agree why this sprint is worth doing, and write it as the Sprint Goal.
2. **What.** The Developers pick items from the top of the list that help reach the goal.
3. **How.** The Developers break each item into small pieces of work they can track.

![Three boxes in a row, titled each artifact carries a commitment. Product Backlog, with product goal written above it. Sprint Backlog, with sprint goal above it, plus the plan. Increment, with definition of done above it, every block passed the list.](https://learn.benibix.com/diagrams/agile-scrum-artifacts.svg)

### Example: Jack's team plans a two-week sprint

Jack's team of 6 plans a 2-week sprint in 3 hours. Their goal is that shoppers can save a basket and come back to it later.

They finished about 22 items' worth in each of the last 3 sprints, and one person is away, so they pick 18. Then they split those into 64 small tasks on the board.

**Words in this lesson:** [Sprint Planning](https://learn.benibix.com/term/business/sprint-planning), [Sprint Goal](https://learn.benibix.com/term/business/sprint-goal), [Sprint Backlog](https://learn.benibix.com/term/business/sprint-backlog)

**Question:** Who decides how much work fits into a sprint?

**Answer:** The Developers. The Product Owner says what matters most, but only the Developers can say how much they can finish. They pick the items and make the plan.

---

Source: https://learn.benibix.com/learn/business-agile/sprint-planning-and-backlog
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
