Understand the Bug Lead Time for Change (LTC) Metric Template

The Bug LTC metric template provides the average time it takes for a bug to be solved over the past twelve months.

‍

What Good Looks Like for Bug Lead LTC

According to the DORA metrics scale, elite performers observe a bug LTC below 1H. The LTC for high performers is usually less than 1 week, while the LTC for medium performers can be as much as 6 months. For this metric, low performers reach over 6 months.

How to Improve Your Bug Lead Time for Change (LTC) Metric

• Make sure your Support and Product teams provide detailed steps on how to reproduce bugs. It will assist developers in investigating root causes and fixing problems more quickly.
• Automate the code review process to shorten the feedback loop and save your reviewers' time.
• Automated end-to-end testing (E2E) allows your QA and Product teams to spend more time on progressive testing rather than regression testing.
• Increasing the seniority of your team will help alleviate peer review bottlenecks, which usually arise from senior and mid-level staff being overburdened. 
• Allow your developers to work with the people who originally reported the issue during development to prevent back-and-forth development.