Product Goal
A future state that gives a product team a shared objective and context for ordering work.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-goal/
01What it means
A Product Goal is the longer-term objective for a product in Scrum, describing a future state toward which the team works. It provides focus for the Product Backlog and is distinct from a feature list, a Sprint Goal, or a broad vision with no inspectable direction.[1][2]
02Why it matters
A clear goal helps teams evaluate backlog work against a coherent product direction and inspect progress toward a valuable future state.
03When to use it
Use it in Scrum where the Product Backlog needs a commitment and focus. Keep the goal meaningful but revisable as learning changes the product direction.
04How it works
- Describe the valuable future state.
- Make it visible with the product backlog.
- Order and refine work in relation to it.
- Inspect increments for progress toward the goal.
- Adapt or replace it when evidence or strategy changes.
05A practical example
A team’s Product Goal is enabling small businesses to complete their first payroll run confidently; backlog choices are evaluated against that state rather than against isolated feature requests.
06Where it breaks
A goal does not specify the solution or guarantee value; multiple teams may need additional coordination and measures to understand progress.
Common mistakes
- Writing a list of outputs as the goal.
- Confusing it with a Sprint Goal or product vision.
- Keeping it unchanged after evidence invalidates the direction.
07Sources
- The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
- Scrum Guide RevisionsScrum Guides · Official framework explanationScrum Guide Revisions