Product Goal and Sprint Goal: How to Write Them (With Examples)
The 2020 Scrum Guide introduced something many teams had been missing: each of the three artifacts now has a commitment that gives it focus. The Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal and the Increment has the Definition of Done. This lesson covers the first two, shows what makes a goal good, and gives you examples and templates you can adapt. For Definition of Done, see Definition of Ready vs Definition of Done.
The Product Goal
The Product Goal describes a future state of the product that can serve as a target for the Scrum Team to plan against. It lives in the Product Backlog; the rest of the backlog emerges to define "what" will fulfil it. A Product Goal is the long-term objective: the Scrum Team must fulfil (or abandon) one objective before taking on the next. The Product Owner is accountable for creating and clearly communicating it.
What a good Product Goal looks like
- Outcome-focused, describing a change for users or the business rather than a list of features.
- Time-aware but not a deadline, usually spanning several Sprints, often a quarter or two.
- Measurable or at least observable, so the team can tell whether it is being achieved.
- Single and focused. One goal at a time prevents a scattered backlog.
Examples
| Weak | Stronger |
|---|---|
| Build the new mobile app | New customers can open an account and make their first payment from their phone in under five minutes |
| Improve the website | Reduce checkout abandonment from 70% to 50% |
| Migrate to the cloud | Run the booking platform on the new cloud infrastructure with no customer-visible downtime and 30% lower hosting cost |
| Add reports | Managers can answer weekly staffing questions without asking an analyst |
A simple template
"By [timeframe], [user group] will be able to [new capability or outcome], measured by [indicator]."
The Sprint Goal
The Sprint Goal is the single objective for the Sprint. Although it is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. It also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. The Sprint Goal is created during Sprint Planning and added to the Sprint Backlog. If the work turns out to be different from what the Developers expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog without affecting the Sprint Goal.
The Product Goal is the long-term target; each Sprint Goal is a step toward it.
Characteristics of a useful Sprint Goal
- One sentence, one idea. If it needs "and" three times, it is a list of tasks.
- Explains why, not only what: the value or learning the Sprint will create.
- Testable at the Sprint Review. Stakeholders should be able to see whether it was achieved.
- Flexible in how. It leaves room for the Developers to adapt the plan.
- Realistic and challenging. Based on the team's actual capacity.
Weak versus strong Sprint Goals
| Weak | Why it is weak | Stronger version |
|---|---|---|
| Complete stories 41, 42, 45 and 51 | A list of tickets, no purpose | Enable returning customers to log in with a saved payment method |
| Work on performance | Vague and unmeasurable | Cut average search response time below two seconds for the top 100 queries |
| Fix bugs and add features | No focus; everything qualifies | Make the registration flow reliable enough to turn on for all new users |
| Deliver 30 story points | Output, not outcome | Allow a manager to approve leave requests from the mobile app |
Sprint Goal templates
- Capability: "Enable [user] to [do something new]."
- Learning: "Find out whether [assumption] holds by [experiment]."
- Risk reduction: "Prove that [technical approach] can handle [load or constraint]."
- Quality: "Bring [area] to a standard where we can release it with confidence."
How to Craft a Sprint Goal in Sprint Planning
- Start with the Product Owner's proposal. The PO explains how the product could increase its value and utility in this Sprint and why.
- Look at the top of the Product Backlog and find the natural theme linking a few items.
- Draft a goal collaboratively. The Developers have to believe they can achieve it.
- Check that it is one coherent aim, not a collection of unrelated tickets.
- Select the work that is necessary to meet the goal, plus possibly some secondary items, and write the goal on the board.
If you cannot articulate a goal, that is a signal: the backlog might lack ordering, or the team may be spreading across too many initiatives. See Sprint Planning Explained.
Using the Goal During the Sprint
- Daily Scrum: The Developers inspect progress toward the Sprint Goal. Read the goal aloud at the start.
- Mid-Sprint changes: When a new request appears, ask whether it supports the goal. If not, it goes in the backlog.
- When work is going badly: Renegotiate scope with the Product Owner while protecting the goal, rather than abandoning it.
- Sprint Review: Begin with the goal and state plainly whether it was met.
If the goal becomes obsolete, only the Product Owner has the authority to cancel the Sprint. This is rare and should lead to a thoughtful discussion about why.
Common Problems
- No goal at all. The Sprint becomes a to-do list.
- The goal as a deadline. Pressure to hit the goal at any cost leads to compromises in quality and breaks the Definition of Done.
- Constantly missing it. Investigate planning, capacity, dependencies and story size rather than blame. See Sprint Goal Problems.
- Multiple goals. Choose the most important one. A Sprint with five goals has none.
Connecting Goals Upward: A Simple Hierarchy
Teams that struggle with direction often find that their goals are disconnected. Try this chain: organisational objective (such as an OKR) leads to the Product Goal, which leads to a series of Sprint Goals, each of which leads to specific Product Backlog items. When the Product Owner can explain how a backlog item serves a Sprint Goal, which serves the Product Goal, which serves the company's priorities, the team understands why their work matters.
- The Product Goal is the long-term objective in the Product Backlog; the Sprint Goal is the Sprint's single focus.
- Good goals are outcome-oriented, clear, and testable.
- Write the Sprint Goal collaboratively in Sprint Planning and use it daily.
- Protect the goal; flex the scope.