See what's new on Keypup!  📢

Lead Time for Changes - Pull Requests (DORA Metrics)

Connect your Git repository to automatically calculate the time elapsed from open to merge at a pull request level.

Use LTC Metric

Automate Lead Time for Change (LTC) Calculation from Your Git Pull Requests

with the

Lead Time for Changes - Pull Requests (DORA Metrics)

Connect your Git repository to automatically calculate the time elapsed from open to merge at a pull request level.

Use LTC Metric
Lead Time for Changes - Pull Requests (DORA Metrics)Lead Time for Changes - Pull Requests (DORA Metrics)Lead Time for Changes - Pull Requests (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 Lead Time for Change Metric Template 

The LTC metric template provides the average time it takes for a pull request to be merged over the past twelve months.

What Good Looks Like for Lead Time for Change (LTC)

Elite performers observe an LTC below 1H according to the DORA metrics scale. High performers have an LTC below 1 week, while medium performers can see an LTC of up to 6 months. Low performers reach over 6 months for this metric.

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

  • Ensure issues are relatively consistent in size: This allows for easier comparison between pull requests and improves metric reporting accuracy.
  • Make sure issues are properly scoped: Clear instructions about the expected logic, the visuals, and the objectives help engineers design the right solution from the start. 
  • Provide developers with immediate PR feedback on low-level issues through automated code review tools, such as linters and code analysis tools. This will decrease the reliance on senior reviewers for small issues and increase their willingness to complete reviews in a timely manner.
  • Peer review bottlenecks are typically caused by senior and mid-level developers being overburdened. If you feel this will help unlock bottlenecks, give your senior staff more time to review pull requests or hire more senior-level personnel.
  • Allow your developers to work with your product team while they're developing, not just when the pull request is ready for review. This will prevent back-and-forth development.
Use LTC Metric