Lead Time for Changes
The total time (in seconds) it takes for a code change to go from the first commit to being successfully deployed to production. It's like measuring how long it takes for a product idea to go from concept to being available to customers.
Where to find it
- Delivery > DORA Metrics
- Delivery > PR Insights
- Health > Team Insights
Interpretation
- Elite Performance (< 1 hour) - Extremely fast delivery pipeline, highly automated, efficient processes. Typical for mature DevOps teams with excellent automation. Maintain current practices, share best practices.
- High Performance (1 day - 1 week) - Good delivery speed, well-functioning CI/CD pipeline. Typical for most successful development teams. Look for incremental improvements.
- Medium Performance (1 week - 1 month) - Reasonable delivery time, some manual processes, occasional bottlenecks. Typical for growing teams or complex systems. Identify and address bottlenecks.
- Low Performance (> 1 month) - slow delivery pipeline, manual processes, frequent bottlenecks, typical for teams with process issues. Major process improvements needed.
- Low Values (e.g., < 2 hours total) indicates very fast delivery pipeline, highly automated, efficient processes. Typical for mature DevOps teams with excellent automation. Verify quality isn't compromised for speed.
- Medium Values (e.g., 2-24 hours total) is a good balance of speed and quality, common for well-functioning development teams. Indicates reasonable review processes with some automation.
- High Values (e.g., > 24 hours total) - slow delivery pipeline. Potential issues: manual deployment processes, long review cycles, infrastructure bottlenecks, process inefficiencies or team coordination issues.
Custom Dashboards
Don't forget you can anytime include any metric in your Custom Dashboards.
Updated about 1 month ago