Plans
Roles
Support
Customers
The complete Software Engineering Intelligence platform
Get the full suite of Plandek intelligence tools for actionable delivery insights at every level
Book Demo
PRODUCT OVERVIEW
USEFUL PAGES
Data-driven insights for engineering leaders
2025 Software Delivery Benchmark Report
Download Now
PRICING
ABOUT
ACADEMY
Solutions
Platform
Pricing
About
Academy
Your voice matters: Join the GenAI adoption conversation - contribute to our industry research.
Written by
Code Cycle Time is a key software delivery metric as it tracks the efficiency of the Pull Request process – which itself is a critical element of the end-to-end software delivery process.
More specifically, Code Cycle Time analyses all completed Pull Requests (PRs) (e.g. closed, merged, declined, etc.) within the specified time range and shows the average hours to complete from when the PR was opened.
Not only that, but Code Cycle Time provides full insight into the different stages that a PR goes through. These stages are defined as:
The method of calculation of Code Cycle Time is shown below:
Example Code Cycle Time chart – Plandek DevOps metrics dashboard
Example Code Cycle Time chart – Plandek DevOps metrics Dashboard
Delivery metrics dashboards like Plandek enable you to analyse delivery and engineering metrics at the team level in a number of different ways.
Below is a selection of the options available to analyse Code Cycle Time:
Example Code Cycle Time drill-down chart – Plandek DevOps metrics dashboard
Code Cycle Time is one of many delivery and DevOps metrics. As such it is often used as part of a ‘balanced scorecard’ of software delivery metrics surfaced in real-time at team and programme level.
Other such software delivery metrics and DevOps metrics include:
Code Cycle Time is a very useful DevOps metric to help teams reduce their Lead Time and increase the velocity of software delivery. The Pull Request process can become a key blocker in the overall delivery process as the code awaits peer review. This may be because teams rely on a few key engineers to action the majority of Pull Requests, and hence bottlenecks quickly develop.
Empirical data shows that Code Cycle Time typically accounts for circa 30% of Cycle Time – so the PR process is very often a key source of ‘hidden’ delay.
Code Cycle Time is particularly important for organisations looking to increase delivery velocity (reduce Lead Time) -e.g.:
Reducing Code Cycle Time will reduce overall Lead Time and increase software delivery velocity. Empirical evidence shows that it is not uncommon to reduce Lead Time by 5-10% through tracking and effective management of Code Cycle Time.
Detailed analysis will also reveal the engineers responsible for actioning the majority of PRs and can help Team Leads reduce the pressure on these key individuals – thereby reducing pressure on the individuals themselves and, at the same time, reducing the ‘key-person’ risk within the software delivery capability.
Plandek works by mining data from toolsets used by delivery teams (such as Jira, Git, CI/CD tools and Slack) to provide end-to-end delivery metrics/analytics to optimise software delivery predictability, risk management and process improvement.
Plandek is a global leader in this fast-growing field, recognised by Gartner as a top nine global vendor in their DevOps Value Stream Management Market Guide (published in Sept 2020).Plandek is based in London and works with clients globally to apply predictive data analytics and machine learning to deliver software more effectively.
Free managed POC available.