What is a sprint goal?
A sprint goal is one sentence that explains why the sprint matters. It's the thread that ties the sprint backlog tickets together and gives the team something to align decisions against when things change mid-sprint.
What a good sprint goal looks like
A good sprint goal is:
- Specific — names a user-facing outcome, not an internal artifact.
- Observable — you can demo it to a stakeholder.
- Bounded by the sprint — finishable in the timebox.
- Robust to ticket churn — even if 1-2 tickets get descoped, the goal is still achievable.
Examples
- "Ship the new onboarding flow to 10% of signups."
- "Cut p95 API latency below 200ms on the dashboard endpoints."
- "Get the billing import to feature-complete and behind a feature flag."
"Improve performance" is not a sprint goal. "Cut p95 below 200ms on /dashboard" is.
Why the sprint goal matters
When something goes wrong mid-sprint — a ticket blows up, a hotfix lands, an estimate was off — the goal tells you which tickets to drop first. Without a goal, every ticket feels equally important and the team makes worse trade-offs under pressure.
Common sprint-goal mistakes
- No goal — most common failure. Planning becomes "pick the top 10 tickets."
- Goal restated as ticket list — "complete tickets X, Y, Z" isn't a goal, it's a checklist.
- Goal written after planning — write it first, then pick tickets that serve it.