Cycle Time

Boaz Dremer Updated by Boaz Dremer

Cycle Time

Cycle time is one of the most interesting engineering execution metrics. It will show the average time it takes for a single engineering task (usually mapped to a branch) to go through the different phases of the delivery process from 'code' to 'production'. Cycle Time refers to the following subsets:

Coding Time:

The time it takes from the first commit until a pull request is issued. In this widget, it's represented as the time frame between 'First Commit' to 'PR Issued'.

Pickup Time:

The time it takes from when a pull request is issued until a review has started. This part indicates how strong teamwork is and it usually has a big impact on the cycle time as very often is where Pull Requests get stuck. In this widget, it's represented as the time frame between 'PR Issued' to 'PR Reviewed'.

Review Time:

The time it takes to complete a code review and get a Pull Request merged. In this widget, it's represented as the time frame between 'PR Reviewed' to 'PR Merged'.

Deploy Time:

The time it takes to release code to production. LinearB tracks each release tag and knows to map it back to branches and present how much time completed tasks 'waited' to be deployed. In this widget, it's represented as the time frame between 'PR Merged' to 'Release'.

Note: Cycle time refers to all the branches that were being updated during an iteration or a workweek.

For example, if a branch went through the first phase here (Pull Request issued) it will already be taken into account. In oppose to the 'time to merge' delivery metric that will only be calculated for a pull-request that went throughout all the phases until the merge. This is why at times there can be discrepancies between the two.

To learn more about how LinearB uses industry benchmarks

How did we do?

What is "Work Breakdown"?

Contact