New DORA Extension Measures Delivery Consistency Across Multi-Platform Teams
DORA metrics miss cadence irregularity—new DC metric fixes that with real-world data.
The DORA framework is the gold standard for measuring engineering team performance, but its metrics—like Deployment Frequency—only capture averages, hiding whether releases occur on a steady metronomic cadence or in erratic bursts. To address this, researchers Luiz Parente and James C. Davis introduce Delivery Consistency (DC), a bounded second-moment measure based on the coefficient of variation of inter-release intervals. In a pilot on 120 weeks of data from a four-platform software delivery group using Jira, GitHub, and Firebase, DC revealed that platforms with identical DORA tier placements had markedly different cadence regularity—a blind spot in traditional DORA analysis.
DC is integrated into the Delivery Health Matrix, an eight-archetype diagnostic that maps joint readings to differentiated interventions. This allows teams to move beyond simple traffic-light assessments (green/yellow/red) and pinpoint whether irregular delivery stems from organizational constraints, procedural bottlenecks, or tooling issues. The paper demonstrates that even teams with the same Deployment Frequency or Lead Time can have vastly different predictability, impacting planning, incident response, and developer morale. By adding DC, engineering leaders gain a more nuanced tool for process improvement without abandoning the widely adopted DORA framework.
- DC is derived from the coefficient of variation of inter-release intervals, capturing cadence regularity that standard DORA metrics miss.
- Tested on 120 weeks of data across 4 platforms (Jira, GitHub, Firebase) with real-world multi-platform release teams.
- The Delivery Health Matrix maps 8 archetypes to differentiated interventions, moving beyond simple red/yellow/green labels.
Why It Matters
Engineering teams can now identify erratic release patterns masked by averages, enabling targeted process fixes.