7.1 Product and Value
Key Takeaways
- The 2020 Scrum Guide defines a product as a vehicle to deliver value, with a clear boundary, known stakeholders, and well-defined users or customers
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team
- Value accountability is a single-person accountability; the Product Owner may delegate work but remains accountable
- Scrum names no specific value metric — choosing how to measure value is professional product practice, not a Scrum Guide rule
- Scrum's short Sprints exist to test value assumptions empirically and adapt quickly toward outcomes, not outputs
Why This Topic Matters
The "Managing Products with Agility" focus area is roughly 20% of the Professional Scrum Master I (PSM I) assessment, and it is where well-prepared candidates most often lose points. The reason is consistent: people over-extend the Scrum Guide. They assume Scrum prescribes value metrics, estimation units, roadmap formats, or release procedures. It does none of these things. org expects a competent Scrum Master to reason about but never to confuse with the Guide itself.
Quick Answer: Scrum exists to deliver value through a product. The 2020 Scrum Guide defines a product as a vehicle to deliver value with a clear boundary, known stakeholders, and well-defined users or customers. The Product Owner is accountable for maximizing that value.
This distinction — rule versus practice — is the single most reliable tie-breaker on product questions. When two answer options both sound reasonable, the correct one is usually the answer that respects empiricism, keeps value accountability with the Product Owner, and refuses to invent a rule the Guide does not state.
What "Product" Means (2020 Scrum Guide)
The 2020 Scrum Guide is deliberate about the word product, which it formally defined for the first time in the November 2020 revision. It states that a product is a vehicle to deliver value. A product has:
- A clear boundary — what is inside and outside of it is understood, so the Scrum Team and stakeholders share one mental model of scope.
- Known stakeholders — people with a legitimate interest in the outcomes the product produces.
- Well-defined users or customers — the people who actually receive and experience the value.
Crucially, a product can be a service, a physical good, or something more abstract. The Scrum Guide keeps this definition broad on purpose so that Scrum applies far beyond software. On the exam, beware answers that secretly narrow "product" to mean "a software application" or "a release package" — the Guide's framing is intentionally wider.
Value Focus and the Outcomes-vs-Outputs Distinction
Scrum is built on empiricism — its three pillars are transparency, inspection, and adaptation — and on Lean thinking, which means reducing waste and focusing on the essentials. The reason the framework iterates in short Sprints is to test value assumptions quickly and adjust before too much is invested in the wrong thing. Value is not a side effect of doing Scrum well; value is the entire point.
A recurring PSM theme is outcomes versus outputs. An output is what the team produces — features shipped, story points completed, lines of code, a number of releases. An outcome is the change in customer or business reality that the output causes — a problem solved, a behavior changed, money earned or saved. A team can be highly productive (high output) and still deliver little value (poor outcomes). Scrum's short feedback loops and the Sprint Review exist precisely so the Scrum Team can inspect outcomes, not merely celebrate outputs.
On the exam, the more value-literate answer almost always favors outcomes over volume of delivery.
Hard Scrum Guide rule
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is a single-person accountability — it cannot be held by a committee. The Product Owner may delegate the underlying work to others, but the accountability for value remains theirs and cannot be diluted.
Supporting professional practice (not a Scrum rule)
How you measure value — revenue, retention, customer satisfaction, time-to-market, cost reduction, adoption — is a professional product decision. The Scrum Guide names no value metric and mandates none. Treat value metrics as practice that supports Scrum, never as Scrum law.
| Concept | Source / status |
|---|---|
| Product = vehicle to deliver value | 2020 Scrum Guide (hard rule) |
| Product Owner accountable for maximizing value | 2020 Scrum Guide (hard rule) |
| Value accountability is single-person | 2020 Scrum Guide (hard rule) |
| Specific value KPIs (NPS, MRR, retention) | Professional practice, not Scrum |
| Outcomes prioritized over outputs | Lean/empirical mindset Scrum embodies |
| Empiricism and Lean thinking | 2020 Scrum Guide (foundational) |
Who Does What with Value — and Worked Scenarios
Value work is shared across the Scrum Team but accountability is not. The Product Owner decides what maximizes value and orders the Product Backlog accordingly; the Developers decide how to build it and are accountable for a quality, Done Increment; the Scrum Master is accountable for the Scrum Team's effectiveness, coaching everyone — including stakeholders and the wider organization — to focus on value and empiricism. A frequent distractor presents the Scrum Master as the value owner or the value-metric decider; that is wrong.
Likewise, the Developers do not get to overrule the Product Owner's ordering, and stakeholders do not get to set the metric by fiat.
Consider three exam-style scenarios:
- "We shipped 40 story points this Sprint — great value!" This conflates output with outcome. Points completed say nothing about whether users are better off. The value-literate response inspects the outcome of the Increment with stakeholders at the Sprint Review.
- "Our product has no clear users, but we keep adding features." The 2020 definition requires well-defined users or customers. Without them, there is no way to know whether features deliver value; the team is producing output into a void. The fix is to clarify users and stakeholders, then reorder around their needs.
- "Finance mandates that value = cost saved, full stop." No single stakeholder owns the metric. The Product Owner, who is accountable for maximizing value, leads the choice of measures — typically a blend of value dimensions — informed by stakeholders, not dictated by one of them.
Key distinctions to memorize
- Value is the purpose; the product is the vehicle. Confusing the two (treating the artifact, the release, or the codebase as the value) is a classic trap.
- Maximizing value is single-person accountability (Product Owner), even though everyone contributes to it.
- Outputs are easy to count; outcomes are what matter. Empiricism and the Sprint Review exist to keep the team honest about outcomes.
- No metric is mandated. Any answer that says "Scrum requires [specific KPI]" is wrong by construction.
According to the 2020 Scrum Guide, which description best completes the sentence: "A product is a vehicle to deliver ___; it has a clear boundary, known stakeholders, and well-defined users or customers."
An executive insists that the Scrum Team report value strictly as quarterly Net Revenue and nothing else, citing "the Scrum Guide." Which response is most accurate?
Per the 2020 Scrum Guide's definition of a product, which characteristics are explicitly part of that definition? (Select all that apply.)
Select all that apply
Single word: Which Scrum accountability is accountable for maximizing the value of the product resulting from the work of the Scrum Team? (Answer with the role, two words.)
Type your answer below