The Sprint Goal is the Sprint Backlog's commitment. It answers, in one sentence,
why this Sprint is worth running, and because it is a single sentence, it forces
the team to decide what the Sprint is actually about rather than treating it as a
container for whatever was next on the list.
Commitment and flexibility, together
The Guide pairs those two words deliberately. The Developers commit to the
objective, not to a fixed list of Product Backlog items. That is what allows a
team to discover mid-Sprint that an item is unnecessary, drop it, and still have
kept its promise. Treating the Sprint Backlog as a fixed contract removes that flexibility.
Who crafts it
Sprint Planning has three topics, covering why this Sprint is valuable, what can be Done, and how the work will get done. The Sprint Goal comes out of the first, and the
whole Scrum Team crafts it. Scenario questions frequently offer an option in which the Product Owner or
Scrum Master announces the Sprint Goal; the Guide places it with the whole team.
When it can change
It cannot. Scope can be renegotiated; the Sprint Goal is fixed for the Sprint. If
it genuinely becomes obsolete, because the market moved or the assumption
collapsed, the Sprint may be cancelled, and only the Product Owner has that
authority.
Common misconceptions
“The Product Owner sets the Sprint Goal and hands it to the Developers.”
The Sprint Goal is crafted by the whole Scrum Team during Sprint Planning. The Product Owner brings the why and proposes how the Sprint could increase value; the objective itself is agreed together.
“Once a Sprint starts, nothing about the Sprint may change.”
Scope may be clarified and renegotiated with the Product Owner as more is learned. What must not change is the Sprint Goal. If the Sprint Goal becomes obsolete, the Sprint may be cancelled, and only the Product Owner can do that.
“A Sprint with several unrelated pieces of work simply has several Sprint Goals.”
There is one Sprint Goal. A Sprint whose work cannot be described by a single objective is usually a symptom of a backlog ordered by stakeholder rather than by strategy.
4 questions test this concept
Midway through a Sprint the Developers find that two of the five selected items are far larger than expected. Dropping them would still allow the Sprint Goal to be met. What does the framework permit?
AScope may be clarified and renegotiated with the product owner as more is learned, provided the Sprint Goal is not put at risk.
BNothing may change during a Sprint, so the team works overtime to finish all five.
CThe Sprint Goal is changed to match what can now be delivered.
Essential Scrum, On Sprint Planning and what a Sprint commits to.
Template
Backlog refinement agenda, A ninety-minute structure covering the current Product Goal, what changed since the last session, and the items nearest the top that are not yet ready for selection.