Understand your team's lead time for change

Learn how to navigate your organization's Lead Time for Change data and how you can take action to mitigate risk

Trend

Learn about your organization by analyzing your Lead Time for Changes trend over time. With this view, you can easily see where delays happen and take action. Each line represents a stage in the process. The 2023 State of Devops Report states that about 18% of teams typically deploy changes to production in less than 1 day, and 31% of teams between 1 day and 1 week. 

💡Tip: encourage your developers to submit smaller PRs more often. This will keep everyone in the practice of merging frequently and will take less time to review. 

Median Time by Phase

See exactly how much time is allocated to each phase for the most recent week of the period. Compare this to your trends over time to see how you're tracking. 

Breakdown Table

Drill down further by using the breakdown table. This view lets you dig in further to understand which teams or working areas might need support by pivoting on various people properties like Report Group or Role, or by Repository.  A "null" value means that team didn't have any PRs for that time period. 
This table provides helpful context to understand the Lead Time for Changes Trends, like Delayed PRs (% of PRs that took longer than expected from opened to merged based on complexity), and Complex PRs (% of PRs that are estimated to be complex to review).