What is the Product Goal
The Product Goal describes a future state of the product. It lives in the Product Backlog. The rest of the Product Backlog emerges to fulfill the Product Goal.
The Scrum Team fulfills or abandons one Product Goal before taking on the next.
Why It Matters
The Product Goal gives the team a clear direction over multiple Sprints. Without it, Sprint Goals can be clear in isolation but disconnected from any larger direction. The product drifts.
A clear Product Goal also sharpens Product Backlog decisions. Items that move toward the Product Goal get prioritized. Items that do not get cut.
How It Works in Scrum
The Product Owner owns the Product Goal. It is part of the Product Backlog.
A useful Product Goal:
- Describes a future state of the product, not a feature list
- Means something to stakeholders
- Gives direction for many Sprints of work
- Can be evaluated for progress
- Can be fulfilled or abandoned, then replaced
The team works against one Product Goal at a time.
Every Sprint Goal should move the product toward the Product Goal. If it does not, either the Sprint Goal or the Product Goal needs to change.
Common Mistakes
- No Product Goal at all. The team has a backlog but no direction.
- A Product Goal that is a feature list. "Ship A, B, C, D" is a roadmap, not a goal.
- Multiple Product Goals at once. Focus is gone.
- A Product Goal that never changes. Either too vague to fulfill or no longer relevant.
- Confusing the Product Goal with the Sprint Goal. The Product Goal spans many Sprints.
Key Takeaways
- The Product Goal is the team's long-term objective.
- It lives in the Product Backlog and shapes everything in it.
- The team works on one Product Goal at a time.
- Every Sprint Goal should move toward the Product Goal.