Putting Evidence-Based Management to Work in an Agile Team
Most teams that adopt Scrum eventually hit the same wall: they can show how busy they are, but not whether anything is getting better. Sprint after sprint ships, velocity charts climb, and yet leadership still asks the uncomfortable question — are we actually delivering more value? Evidence-Based Management (EBM), the framework published by Scrum.org, exists to answer exactly that. It is a deliberately simple way to make decisions using measured outcomes instead of opinions, gut feel, or activity counts.
The timing matters. Through 2021, many organizations were still recovering from the pandemic, running hybrid and fully remote teams, and absorbing supply shocks that made roadmaps fragile. When you can no longer wander over to a colleague's desk, the quality of your measurements is the quality of your alignment. EBM gives a distributed team a shared, honest scoreboard.
The four Key Value Areas
EBM organizes measures into four Key Value Areas. Two look at the value you create; two look at your ability to keep creating it. You do not need dozens of metrics — you need a few in each area that you trust.
Current Value (CV): the value the product delivers to customers and users right now — satisfaction, usage of key features, revenue per customer.
Unrealized Value (UV): the future value still on the table if you served the market more completely — market share gaps, unmet needs, desired-but-missing capabilities.
Time-to-Market (T2M): how quickly you can learn and deliver — lead time, release frequency, time from idea to validated feedback.
Ability to Innovate (A2I): how much of your capacity goes to new value versus fighting your own product — defect trends, time lost to low-value work, technical debt drag.
A practical way to start
Name one real goal. Pick a meaningful strategic goal the product is meant to advance. Without it, every metric is just trivia.
Choose two or three measures per area. Favour outcome measures (a customer renewed, a release reached production) over output measures (story points done). Use what you can actually collect.
Set an intermediate goal. Define a nearer target between today and the strategic goal so progress is visible within a quarter, not a year.
Run experiments, not edicts. Treat each Sprint or two as a probe toward the intermediate goal, then read the measures and adjust. EBM rewards inspection and adaptation, not heroics.
Review the numbers in the open. Bring the four areas to your reviews so stakeholders steer with the same evidence the team sees.
A caution worth repeating: EBM measures are for learning, not for ranking people. The moment a value area becomes a stick to beat a team with, the numbers get gamed and the evidence becomes worthless. Used honestly, EBM helps a team say a hard but useful thing — 'we are shipping faster but customer value is flat' — and then do something about it.
If you want help turning Scrum activity into measurable outcomes across a portfolio of projects, XNM's program & project delivery advisory can help you set the goals, choose the measures, and build the cadence to act on them.