💙 Everything here is free  —  here are the ways you can help keep it that way, and most of them cost nothing    See how →
✨ Registered readers browse ad-free. Always free. Create your free account →
✨ Registered readers browse ad-free. Always free.Create your free account →

Sprint Planning answers three questions — why, what and how. The Sprint Goal is the part most teams skip, and the part that makes the rest work.

Sprint Planning opens the Sprint. The Scrum Guide gives it a timebox of eight hours
for a one-month Sprint, usually shorter for shorter Sprints — and, more usefully, it
gives it three questions.

The three questions

1. Why is this Sprint valuable?

This produces the Sprint Goal: a single sentence describing the value the
Sprint delivers. It is the commitment attached to the Sprint Backlog, and it is not the
list of items — it is the reason behind them.

The test for a Sprint Goal: if half the selected items turned out to be impossible, could the team still meet the Goal a different way? If not, you have written a list, not a goal.

2. What can be Done this Sprint?

The Developers select items from the Product Backlog. Nobody assigns them: selecting
is the team’s job, informed by past performance, capacity and the Definition of Done.

3. How will the chosen work get done?

Enough decomposition to start — often into tasks of a day or less. The Guide does not
prescribe how far you go, and it explicitly leaves it to the Developers.

Capacity, not optimism

The single most common failure of Planning is committing to what you wish you could
do. The antidote is boring and it works: look at what you actually finished last
Sprint
. That number, not your enthusiasm, is your capacity.

First Sprint, you have no number. Guess low. A Sprint that finishes early teaches you
your capacity; one that finishes at 40% teaches you nothing except that Planning was
fiction.

Beware the Sprint that is 100% full. Real weeks contain interruptions. A plan with no slack does not fail gracefully — it fails at the end, all at once, on the items you left for Thursday.

What comes out

  • A Sprint Goal — one sentence
  • A Sprint Backlog — the selected items, plus the plan for delivering them
  • A shared understanding of what “done” means for each of them

In Agile Together

Step 6 of the menu hands you a prompt containing the real titles from your Product Backlog and, from Sprint 2 on, the capacity you actually delivered. The AI proposes a Sprint Goal and a selection; you paste its answer into the “0. Inbox” card and run the step again.

⚠️ The step refuses an item that does not exist on your board rather than creating an invented one — the failure mode where an AI hallucinates a plausible backlog item and the plan quietly drifts from the work.

Next

The next lesson is the artefact Planning produces: the Sprint Backlog.

Agile Together is a free course. The package — scripts plus a portable Python — is a single download: get the course package. You install nothing.

Project Together

Track your progress through PMBOK 8

Create your free account to save your reading progress, earn points on every quiz, and unlock certificates as you master each domain.

Create Free Account →

Free forever • No credit card required

Facebook
WhatsApp
Twitter
LinkedIn
Pinterest

Leave a Reply