See what's new on Keypup!  📢

Lead Time for Changes - Issues (DORA Metrics)

Connect your Git repository and project management platform to automatically calculate the time elapsed from open to close issue at a pull request and/or ticket level.

Use Issue LTC Metric

Automate Lead Time for Change (LTC) Calculation from Your Issues

with the

Lead Time for Changes - Issues (DORA Metrics)

Connect your Git repository and project management platform to automatically calculate the time elapsed from open to close issue at a pull request and/or ticket level.

Use Issue LTC Metric
Lead Time for Changes - Issues (DORA Metrics)Lead Time for Changes - Issues (DORA Metrics)Lead Time for Changes - Issues (DORA Metrics)

From startups to large enterprises, Keypup serves all the unique complexities related to project size, structure and teams, including:

“Keypup has been instrumental in helping us gain a better perspective on our engineering activities and identifying bottlenecks. Its ease of use combined with its comprehensive features made a difference for us”

Bruno D'Auria

Engineering Director

“Great product with great support!

Keypup is extremely flexible in its reporting. Once you get your raw data connected, there is almost nothing it can't do. There is a wealth of tables, charts and other reports available. As Director of a software development team, I use Keypup to report on our work efficiencies to senior managment. Keypup makes this task very simple to produce each week.”

Brad B.

Director, Software Development

Understand the Issue LTC Metric Template

The issue LTC metric template provides the average issue time from assignment to close.

What Good Looks Like for Issue LTC

According to the DORA metrics scale, elite performers have an Issue LTC below 1H. The LTC of high performers is below 1 week, while the LTC of medium performers can be up to 6 months. This metric reaches over 6 months for low performers.

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

  • Reduce the scope of your issues: Smaller issues mean fewer scoping tasks for your product team and fewer pull requests for your developers, which results in faster reviews, more straightforward testing, and simpler releases.
  • Give developers immediate PR feedback on low-level issues with linters and code analysis tools. By doing this, you will shorten the feedback loop and save your reviewers' time.
  • Add automated end-to-end (E2E) testing so the QA and Product team can focus on progressive testing rather than regression. 
  • Usually, peer review bottlenecks are caused by senior and mid-level staff being overworked. Invest more time in reviewing pull requests by your seniors and/or hire more of them.
  • To avoid back-and-forth development, involve the product team during development.
Use Issue LTC Metric