In 30 seconds
- One sentence that explains why this sprint is worth doing.
- It keeps the team focused and gives flexibility on the details.
- It's the commitment attached to the Sprint Backlog.
Why it matters
Without a goal, a sprint is just a list of tickets. With one, the team can make smart trade-offs: if an item turns out bigger than expected, they can drop or reshape something else as long as the goal is still met.
Good vs weak goals
| Weak | Better |
|---|---|
| Finish tickets 101-114 | New customers can sign up and pay without help from support |
| Work on reporting | Managers can export last month's sales to a spreadsheet |
A good goal names an outcome someone would notice.
How it's used
It's agreed in Sprint Planning, checked in every Daily Scrum, and the Sprint Review looks at whether it was achieved. Officially, it's the commitment for the Sprint Backlog.
Myth vs reality
Myth · The Sprint Goal is the sum of all items.
Reality · It's one objective; some items may not be needed to reach it.
Myth · The Product Owner sets it alone.
Reality · The whole Scrum team crafts it together.
Myth · Missing a goal means the team failed.
Reality · It's a signal to inspect and adapt, not to blame.
FAQ
Can a sprint have two goals?
Scrum asks for one. Two goals usually means the team is split across unrelated work.
What if the goal becomes irrelevant mid-sprint?
The Product Owner may cancel the sprint; this should be rare.
Where should the goal be visible?
Somewhere the team sees daily, such as the top of the board.