🛠️ Improved Accuracy for Time to Develop Metric

We’ve rolled out an enhancement to how we calculate Time to Develop—the time between first commit and pull request opened—giving you a more accurate view of your team’s performance.

This update introduces two key improvements:

• Zero Values: for pull requests with a first commit timestamp after the pull request was opened, we had assigned a Time to Develop of zero. These zero values reduced the average for this metric but are no longer counted in the new release, providing for a more accurate metric.
• More Complete Branch Accounting: some commits in development branches were previously excluded from the Time to Develop calculation. Those commits are now included to provide more complete accounting of this metric.

These edge cases were impacting the metrics. The metrics are now more accurate.

What to expect: You may notice a shift in your Time to Develop and overall Lead Time metrics. Our industry benchmarks have also been updated, reflecting a more precise picture of the software development lifecycle.