The 2020 Scrum Guide elevated the sprint goal from a nice-to-have to a commitment. Yet in most organisations, sprint goals are either absent, trivially vague ("complete all planned stories"), or identical to the sprint backlog in prose form. Here is why they matter and how to write ones that actually work.
Why Sprint Goals Matter
A sprint goal answers: "Why are we doing this sprint?" Without a goal, every individual story is equally important — which means when something goes wrong mid-sprint (and something always does), the team has no basis for trade-off decisions. With a clear goal, the team can ask: "Does this impediment threaten the sprint goal? If not, we proceed. If yes, we escalate immediately."
The Sprint Goal Formula
The most effective sprint goals follow this pattern:
We will [deliver/enable/validate/reduce] [specific outcome] [by/for/so that] [business context or user benefit].
Examples:
- "We will enable customers to complete a new direct debit mandate without calling support, reducing inbound call volume by an estimated 15%."
- "We will validate whether users discover the new dashboard feature organically, so we can decide whether to invest in in-app onboarding."
- "We will complete the ISO 20022 message enrichment layer so the payment operations team can begin parallel-run testing in Sprint 12."
- "We will reduce average checkout time from 4 minutes to under 90 seconds for returning customers."
- "We will enable the compliance team to export audit logs in the format required by the FCA's September deadline."
What Makes a Bad Sprint Goal
| Bad sprint goal | Problem | Better version |
|---|---|---|
| "Complete all stories in the sprint" | Not a goal — just a restatement of the plan | "Enable users to filter search results by three criteria" |
| "Work on the payments module" | Too vague — no outcome defined | "Reduce payment failure rate from 3.2% to below 1%" |
| "Finish the API and the dashboard and fix the login bug" | Multiple goals = no goal | Pick one outcome; others become stretch goals |
| "Support the team in delivering sprint 7" | Meaningless — no measurable outcome | "Validate the new onboarding flow with 5 real users before sprint review" |
Sprint Goals in Stakeholder Conversations
A clear sprint goal transforms stakeholder communication. Instead of presenting a list of 14 stories at a status meeting, the SM can say: "This sprint, we are enabling direct debit mandate completion without support calls. We are 70% of the way there with 4 days remaining." This is the language executives understand and value.
Stretch Goals
Once the sprint goal is defined, additional stories can be added to the sprint backlog as stretch goals — items the team will work on if the sprint goal is achieved ahead of schedule. Stretch goals prevent the problem of teams padding estimates or "coasting" in the final days of a sprint. They also give the team permission to deliver more than the goal without creating a commitment to do so.