Adding Value
Adding Value tests whether you can define, prioritize, and measure value rather than output. EXIN Agile Scrum questions often contrast story points, velocity, and delivered features with outcomes such as revenue, risk reduction, and customer behavior.
What value means
- Value is an outcome for the customer and the organization: revenue, cost reduction, risk reduction, compliance, learning, or satisfaction.
- Value is not output: features, story points, and hours worked are not value in themselves.
- The Product Owner orders by expected value and risk; cost of delay helps compare delivering something early versus late.
Metrics that help and mislead
- Velocity is a planning and forecasting aid. Using it to compare teams or pressure teams destroys its meaning.
- Burn-down and cumulative flow show progress and bottlenecks, not value delivered.
- Outcome metrics such as adoption, conversion, retention, support tickets, and revenue test whether the increment mattered.
- Avoid vanity metrics that always rise and never inform a decision.
Release and feedback
- Release early and often to realize value and reduce risk; an increment that is never released has no customer value.
- A minimum viable product is the smallest release that tests a value hypothesis, not the smallest pile of features.
- Use Sprint Review to inspect the product with stakeholders and adapt the backlog; feedback becomes an ordering input.
Worked example
A Product Owner must choose between a large reporting feature with high revenue, high effort, and a long delay, and a small onboarding fix with moderate revenue, low effort, and immediate release. Using cost of delay and effort, the Product Owner orders the onboarding fix first because it delivers value sooner and frees capacity to learn. The reporting feature is split so demand can be tested earlier. Reasoning: value is time-sensitive; early feedback reduces the risk of building the wrong report.
Traps that cost marks
- More story points means more value: points estimate size, not value.
- Velocity should be maximized: sustainable pace and outcomes matter more.
- Value is only money: risk, compliance, and learning count.
- Release at the end to maximize scope: that delays feedback and value.
- The Product Owner decides value alone: stakeholders and customers inform it, but the Product Owner orders.
- A bigger release is automatically more valuable: value depends on outcomes and timing, not batch size.