ASP Metrics
Metrics give the delivery system visibility into its own behavior. Like BI gives business intelligence about business operations, delivery metrics give delivery intelligence — continuous feedback about how work flows, where it stalls, and whether the system is performing as expected. This feedback is what makes empirical, systems-based governance possible.
Design Principles
Measure the system, not the people. Flow metrics describe how work moves through the delivery system. They are not performance ratings for individuals or teams.
Outcome metrics complement flow metrics. Flow metrics tell you how the system is performing. Outcome metrics tell you whether it is delivering the right things. Both are necessary.
Thresholds are context-dependent. The interpretation guidance here is a starting point. Each organization needs to establish its own baselines before setting targets.
What we do not measure matters too. Each framework is explicit about what is out of scope and why.
Metrics Frameworks
| Framework | Level | What it covers |
|---|---|---|
| Portfolio Flow Metrics | Portfolio | Initiative flow, economic performance, and predictability through Portfolio Kanban |
| DVS Flow Metrics | DVS | Feature flow, WIP age, and predictability through DVS Feature Kanban |
| Team Flow Metrics | Team | Story cycle time, sprint velocity, WIP, and sprint predictability |
| DORA Metrics | DVS / Team | Technical delivery pipeline performance — deployment frequency, lead time, change failure rate, MTTR |
Related
- Principle: Measurement and Feedback — the reasoning behind systematic measurement
- Portfolio Kanban Flow — the flow stages that Portfolio Flow Metrics are measured against
- DVS Kanban Flow — the flow stages that DVS Flow Metrics are measured against
- Team Kanban Flow — the flow stages that Team Flow Metrics are measured against