Evidence-Based Management for Agility: The Mistakes Teams Make and How to Avoid Them

Evidence-Based Management (EBM) is a framework published by Scrum.org for helping organisations improve their ability to deliver value to customers. It provides a set of Key Value Areas (KVAs) and associated metrics that help organisations understand their current performance, set improvement targets, and track progress toward better outcomes. The four Key Value Areas are: Current Value, Unrealised Value, Ability to Innovate, and Time to Market.

EBM is more commonly misapplied than correctly applied. Here are the most frequent mistakes.

Mistake 1: Using Activity Metrics as Outcome Metrics

EBM is specifically designed to shift organisational focus from activity and output metrics (velocity, story points, features shipped) to outcome and value metrics (customer satisfaction, usage, revenue, cost avoidance). Teams that adopt the EBM vocabulary but fill it with activity metrics have not made the shift -- they have added new labels to the old measurements. An 'Ability to Innovate' metric that measures the number of features in the backlog, rather than the team's actual ability to release new value quickly, is an activity metric in outcome clothing.

Mistake 2: Measuring Everything Instead of the Right Things

EBM provides a rich catalogue of possible metrics. Teams that try to track all of them simultaneously produce measurement overhead without insight. The right approach is to identify the one or two metrics in each Key Value Area that most accurately reflect the organisation's current performance gap and focus measurement effort there. Start with the area where performance is worst, measure it rigorously, and improve it before expanding the measurement scope.

Mistake 3: Not Connecting Metrics to Decisions

A metric that nobody uses to make a decision is a vanity metric. For each EBM metric in the dashboard, ask: who looks at this, on what cadence, and what decision does it inform? If the answer is 'nobody, never, and nothing,' remove the metric. EBM metrics should be reviewed in Sprint Reviews and used to inform Product Backlog prioritisation -- the Customer Satisfaction Gap metric, for example, should directly influence which items the Product Owner prioritises.

Mistake 4: Comparing Metrics Across Teams

EBM metrics are diagnostic tools for a single organisation or product, not benchmarks for comparing teams. Using EBM metrics to rank teams, set comparative performance targets, or justify resource allocation decisions between teams defeats the purpose of the framework and creates gaming behaviour. Each team's metrics are relative to their own baseline and improvement trajectory, not to another team's numbers.

XNM supports public-sector organisations in building outcome-measurement capability and agile delivery frameworks. Reach out to XNM's program & project delivery advisory team to discuss evidence-based management and agile metrics for your organisation.