What is Cycle Time?
Cycle Time shows how fast features or fixes are delivered. Lower Cycle Time is usually a sign of effective and adaptive teams. Increasing Cycle Time is a red flag for inefficiencies or technical debt. Good engineering teams often have Cycle Time under 72 hours.
Cycle Time Breakdown
What is Cycle Time Breakdown?
Cycle Time Breakdown is a segmented view of the overall Cycle Time, where Cycle Time is broken into the 4 universal categories of Development, Response, Review and Integration Time. You can click on any of these boxes to drill-down further.
What does Cycle Time Breakdown do?
Overall, Cycle Time Breakdown gives you an idea of where bottlenecks originate from within your cycles. If any of the 4 sections are too high, this is the metric to find where there might be a problem.
Why use Cycle Time Breakdown?
Cycle Time Breakdown is one of the fastest ways to find bottlenecks in your projects and is an easy way to find the area that should be drilled-down into.
Distribution of Cycle Time
What is Distribution of Cycle Time?
The Distribution of Cycle Time metric compares the number of Pull Requests (PRs) per Cycle to the amount of Time it took to complete said Cycle.
What does Distribution of Cycle Time do?
Distribution of Cycle Time shows where the team may have overloaded themselves with too many PRs indicated by a high PR and Cycle Time amount or where PRs may not have been completed thoroughly, indicated by a high PR but very low Cycle Time count.
Why use Distribution of Cycle Time?
The Distribution of Cycle Time metric is a good way to find how often the team is overloading itself by checking how many Cycles are outliers.
Please note that the Industry Benchmark for Cycle Time is 72 Hours.