Sprint Goal

What is a Sprint Goal?

A sprint goal is the one objective a Scrum team commits to for a sprint, set during sprint planning and stated as an outcome rather than a list of tickets. Sprint backlog items can change during the sprint, but the goal stays fixed.

Updated November 2026 · 3 min read


A sprint goal is a single, short statement of what a Scrum team intends to achieve in a sprint and why it matters. It is agreed during sprint planning and gives the team one objective to work toward, so that when surprises arrive, the team can change the specific tasks it does while still delivering the outcome it committed to.

A sprint goal is not a list of tickets. "Finish stories 41 through 48" describes work; "New customers can import their contacts from a CSV file" describes an outcome the work should produce. The goal gives the sprint coherence and gives stakeholders something meaningful to inspect at the sprint review.

The sprint goal in the Scrum guide

The Scrum Guide defines the sprint goal as the single objective for the sprint and calls it the commitment for the sprint backlog. During sprint planning, the product owner proposes how the product could increase its value in the sprint, and the whole Scrum team collaborates to define the goal. The goal stays fixed for the sprint, while the sprint backlog can change: if the work turns out different from what was expected, the developers negotiate scope with the product owner without affecting the goal. If the goal becomes obsolete, only the product owner can cancel the sprint.

Characteristics of a good sprint goal

  • One objective. A single focus, not three goals joined by "and."
  • Outcome-oriented. Describes a change for users or the business, not a set of tasks.
  • Achievable in the sprint. Ambitious but realistic for the team's capacity.
  • Testable. Everyone can tell at the sprint review whether it was met.
  • Linked to the product goal. Clearly a step toward the longer-term objective.

Sprint goal examples

WeakStronger
Complete the reporting storiesFinance managers can export the monthly revenue report without asking support
Work on performanceSearch results load in under one second for the 20 largest accounts
Research onboarding and fix bugsLearn whether a guided setup checklist reduces the steps new admins skip
Build API endpointsA partner can create and update orders through the API in the sandbox

How to write a sprint goal

  1. Start from the product goal. The product owner brings the most valuable next step toward it.
  2. Draft the outcome together. The team discusses what it can realistically deliver and phrases it as a result.
  3. Select supporting work. Choose backlog items that serve the goal, plus any unrelated work the team must also do.
  4. Check fit. Confirm the goal is achievable with the team's capacity and that most of the sprint backlog supports it.
  5. Make it visible. Put it at the top of the board and refer to it in every daily standup.

A hypothetical example

Consider a hypothetical CRM company whose sprint goal is "New customers can import their contacts from a CSV file." The sprint backlog has eight stories totaling 30 points, 24 of which support the goal. Midway through, the team discovers that customers' files use inconsistent date formats, which adds work. Instead of extending the sprint or missing the goal, the developers and product owner agree to drop a 5-point story for importing custom fields and limit the first version to standard fields. That frees 5 points for the date handling. The team meets the goal, and custom-field import moves to the next sprint. Without a shared goal, the team might have finished more tickets but left customers with an import that failed on real files.

Common pitfalls

  • A goal that is just the backlog. Restating the ticket list gives no basis for trade-offs.
  • Multiple goals. Several unrelated goals split focus and make success ambiguous.
  • Set by the product owner alone. A goal the developers did not help shape is rarely owned by them.
  • Ignored after planning. If the goal is never mentioned again, it cannot guide decisions.
  • Never missed, never meaningful. Goals so safe that they are always met may not be asking enough of the sprint.

The sprint goal is set during sprint planning, guides the team toward a product increment, and connects the sprint to longer-term product goals.

Frequently asked questions

What is an example of a good sprint goal?

A good example is: new customers can import their contacts from a CSV file. It names one outcome, is testable at the sprint review and leaves room to adjust tasks. Compare a weak sprint goal such as complete the reporting stories, which just restates tickets, with finance managers can export the monthly revenue report without asking support.

Can a sprint goal change during the sprint?

No. Under the Scrum Guide, the sprint goal stays fixed for the sprint while the sprint backlog can change. If the work turns out differently than expected, developers negotiate scope with the product owner without changing the goal. If the goal becomes obsolete, only the product owner can cancel the sprint.

Who writes the sprint goal in Scrum?

The whole Scrum team defines the sprint goal during sprint planning. The product owner proposes how the product could increase its value in the sprint, usually as a step toward the product goal, and the developers help shape what they can realistically deliver. A goal set by the product owner alone is rarely owned by the developers.