artifactDelivery & agility

Sprint Goal

A single objective for a Scrum Sprint that gives selected work coherence while preserving flexibility in how the team achieves it.

Download Markdown (.md)

01What it means

A Sprint Goal is the commitment associated with the Sprint Backlog and the single objective for a Sprint. Created during Sprint Planning, it explains why the work is valuable and allows the team to renegotiate exact scope as learning occurs without abandoning the objective.[1][2]

02Why it matters

A shared goal turns a collection of tickets into a coordinated product step. It supports tradeoffs during the Sprint, focuses inspection on progress toward value, and helps stakeholders understand intent rather than only output.

03When to use it

Use one in every Scrum Sprint when the selected work can support a coherent objective. If work has no meaningful connection, expose that planning problem instead of writing a vague goal that merely restates a list.

04How it works

  1. Review the Product Goal, current evidence, and highest-order backlog items.
  2. Formulate one outcome-oriented objective achievable within the Sprint.
  3. Select work and create a plan that credibly support the objective.
  4. Use the goal to guide daily decisions and scope negotiation.
  5. Inspect the resulting Increment and learning against the goal at the Sprint Review.

05A practical example

Example

Rather than set a goal to ship three checkout tickets, a commerce team chooses “reduce avoidable payment failures for returning buyers.” When one planned UI change proves unnecessary, it replaces it with better error handling that more directly serves the goal.

06Where it breaks

A Sprint Goal cannot make unrelated work coherent or substitute for a Product Goal. Outcomes may not fully materialize within one Sprint, and overly broad or activity-based wording provides little decision value.

Common mistakes

  • Copying a list of backlog items into the goal.
  • Setting several competing goals for one Sprint.
  • Changing the goal casually instead of adapting the plan around it.
  • Writing a goal the team cannot evaluate at the Sprint Review.

07Sources

  1. The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
  2. Introduction to Sprint PlanningScrum.org · Professional learning resourceIntroduction to Sprint Planning
View saved topics

Start typing to search titles, definitions, categories, and frameworks.