Integration Frequency
How often developers integrate code changes to the trunk. A leading indicator of CI maturity and small batch delivery.
Metrics
Detailed definitions for key delivery metrics. Understand what to measure and why.
less than a minute
These metrics help you assess your current delivery performance and track improvement over time. Start with the metrics most relevant to your current phase.
Key Metrics
| Metric | What It Measures |
|---|---|
| Integration Frequency | How often code is integrated to trunk |
| Build Duration | Time from commit to artifact creation |
| Development Cycle Time | Time from starting work to delivery |
| Lead Time | Time from request to delivery |
| Change Fail Rate | Percentage of changes requiring remediation |
| Mean Time to Repair | Time to restore service after failure |
| Release Frequency | How often releases reach production |
| Work in Progress | Amount of started but unfinished work |
Content contributed by Dojo Consortium, licensed under CC BY 4.0.
Build Duration
Time from code commit to a deployable artifact. A critical constraint on feedback speed and mean time to repair.
Development Cycle Time
Average time from when work starts until it is running in production. A key flow metric for identifying delivery bottlenecks.
Lead Time
Total time from when a change is committed until it is running in production. A DORA key metric for delivery throughput.
Change Fail Rate
Percentage of production deployments that cause a failure or require remediation. A DORA key metric for delivery stability.
Mean Time to Repair
Average time from when a production incident is detected until service is restored. A DORA key metric for recovery capability.
Release Frequency
How often changes are deployed to production. A DORA key metric for delivery throughput and team capability.
Work in Progress
Number of work items started but not yet completed. A leading indicator of flow problems, context switching, and delivery delays.