If you’ve ever seen a team “hit the metric” while the work still feels chaotic… You already know the problem.
A lot of agile measurement turns into
performance theatre:
- Velocity targets that encourage point inflation
- Utilization goals that punish collaboration
- Dashboards that look great while the cycle time quietly gets worse
This post is about the opposite:
metrics that are hard to game and easy to discuss, the kind that actually support an ROI conversation.
If you want the full ROI framing (inputs + a simple example + the Starter Kit), start here:
https://berriaultandassociates.com/resources/agile-transformation-roi/What “good metrics” do (and what they don’t)
Good metrics don’t “prove agile.” They help leaders make better decisions.
A useful metric should:
- Be connected to a real outcome (time-to-value, predictability, quality, sustainability)
- Be hard to game
- Show a trend over time (not a single number)
- Be discussable without a 30-minute glossary
Bad metrics usually do one of two things:
- They reward the wrong behaviour
- They create fear, so people hide problems
The 5 metrics I’d start with (if you want ROI clarity)
If you only track five things, track these. They show flow, constraints, and whether improvement is sticking.
1) Cycle time (time-to-value)
What it tells you: how long it takes to turn an idea into something usable.
Why it matters for ROI: shorter cycle time usually means faster learning, faster revenue, and less time spent “waiting to find out.”
How to use it:- Track the trend (median is often more useful than average)
- Look for stability, not hero weeks
2) Work in progress (WIP)
What it tells you: how much work you’re trying to do at once.
Why it matters for ROI: high WIP creates context switching, delays, and rework. Lower WIP usually improves throughput and predictability.
How to use it:- Track WIP by stage (not just total)
- Treat it like a leading indicator (it moves before outcomes do)
3) Work item age
What it tells you: How long the current work has been “alive.”
Why it matters for ROI: Aging work is a signal of hidden blockers, decision latency, or too much WIP.
How to use it:- Set a simple “aging threshold” (e.g., anything older than X days gets reviewed)
- Use it to trigger conversations, not blame
4) Rework/defects (the hidden work)
What it tells you: How much effort is going into fixing, redoing, or cleaning up.
Why it matters for ROI: Rework is a direct source of capacity leakage. Reduce it and you “recover” time without hiring.
How to use it:- Track rework as a category (even if it’s a rough estimate)
- Watch the trend and the causes (handoffs, unclear “done,” rushed decisions)
5) Sustainability signals (burnout risk)
What it tells you: Whether the system is sustainable.
Why it matters for ROI: Burnout shows up as delivery volatility, turnover, sick time, and quality issues.
How to use it (simple options):- Short pulse check (1–2 questions weekly)
- Overtime trend
- Unplanned work trend
A simple 30/60/90 measurement plan
You don’t need a measurement program. You need a cadence.
First 30 days: leading indicators
Pick 2–3:
- WIP trend
- Work item age trend
- Decision latency (if you can track it)
- Priority clarity (can people repeat the top 3?)
Goal: prove you’re changing the system, not just talking about it.
Days 60–90: outcomes
Pick 2–3:
- Cycle time trend
- Throughput stability
- Rework/defect trend
- Predictability (commitment hit rate)
Goal: Show that the leading indicators are translating into outcomes.
Metrics to be careful with (because they get gamed)
These aren’t “bad” in every context. They’re just risky if used as targets.
- Velocity as a performance target (it will get inflated)
- Utilization as a blunt instrument (it kills slack, learning, and improvement)
- Individual productivity metrics (they punish collaboration)
- Story points as a proxy for value (points aren’t outcomes)
If a metric makes people hide problems, it’s not helping.
How does this connect to a business case
If you’re building a business case, these metrics become your credibility layer:
- “Here’s what’s happening now” (baseline)
- “Here’s what we’re changing first” (leading indicators)
- “Here’s how we’ll know it’s working” (outcomes)
That’s how you avoid the “trust us” trap.
Next step
If you want a plug-and-play worksheet to pick metrics, set ranges (low/likely/high), and build a simple ROI view, grab the ROI Starter Kit here:
https://berriaultandassociates.com/resources/agile-transformation-roi/ And if you want the “how we work” version of this (behaviour-first, not framework-first), it’s here:
https://berriaultandassociates.com/about-us/why-we-work-this-way/
