# Lead Time vs Cycle Time in Software Development | LinearB Blog

> Which of these two key metrics is the best way to measure the productivity of dev teams? And more importantly, how do you start improving them?

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._

[Blog](https://linearb.io/blog)

/

Lead Time vs Cycle Time in Software Development

# Lead Time vs Cycle Time in Software Development

![Photo of Briana Johnson](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Briana_Johnson_19a1d53fce?_a=BAVMn6ID0)

By [Briana Johnson](https://linearb.io/blog/lead-time-vs-cycle-time#briana-johnson)

|

August 17, 2022

![lead_time_vs_cycle_time_2eb314b5dc](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/lead_time_vs_cycle_time_2eb314b5dc?_a=BAVMn6ID0)

Lead time vs cycle time—two seemingly similar metrics, but they can mean different things to different people. 

Lead time and cycle time are metrics that originated in manufacturing. They have been adapted for use in agile software development. 

However, using them to measure your dev team’s efficiency may not always lead to your desired results. And it can be difficult to track them without automation. 

So which of these two key metrics is the best way to measure the productivity of dev teams? And more importantly, how do you start improving them?

## **Table of Contents**

* [What Is Lead Time?](#lead-time)
* [What Is Cycle Time?](#cycle-time)
* [What Do They Measure?](#measure)
* [Cycle Time vs Lead Time](#versus)
* [How to Improve Lead Time & Cycle Time](#improve)
* [The Best Way to Measure Engineering Efficiency ](#best-way)

## What Is Lead Time?

Lead time measures the time from when a user story is ready to implement to when that story is ready for delivery. Lead time includes the time used to discuss the user story, the time the request spent waiting in the backlog, and the time someone starts working on the story to when it’s released. 

## What Is Cycle Time?

[Cycle time](https://linearb.io/blog/cycle-time/) is the time from a developer’s first commit to when the code is deployed to production. It is one of the [4 key DORA metrics](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance) and a subset of lead time. 

Cycle time (or lead time for changes) can also be broken into four phases:

* Coding Time (aka fun time): We calculate coding time from first commit to when a pull request or merge request is created.
* Pickup Time: We calculate pickup time from when the PR is created to when the review begins.
* Review Time: We calculate review time from the start of the review to when the code is merged.
* Deploy Time (release time): We calculate deploy time from when the code is merged to when it is released.

---

Want to learn how to implement custom dev workflow automation to cut code review time by up to 40%? [Watch this hands-on workshop](https://linearb.io/event/202303-gitstream-workshop/) to set up the free gitStream tool to automatically:

![:white_check_mark:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/2705.png) Classify and route pull requests  
 Add estimated review time to PRs  
 Apply custom rules

![gitStream Workshop: Getting started with workflow automation](https://assets.linearb.io/uploads/LinearB-Youtube-Card_-Ofer-Guy-Gitstream-Workshop_-Getting-Started-With-Workflow-Automation-2-1024x576.png)

gitStream product lead, Ofer Afias, will take you through a live demo of the three core functions when getting started with gitStream workflow automation to scale your team efficiently and improve your developer experience.

---

## What Do They Measure?

Cycle time and lead time are both measurements of engineering efficiency. However, you shouldn’t treat both metrics the same way. 

If your team is like every other dev team, you likely have a massive backlog of tickets that you’re never going to work on. Just because someone has a feature idea doesn’t mean it’s important to work on right away…or ever. You don’t want to include those tickets to inaccurately bloat your lead time. And this is why it’s difficult to calculate lead time and standardize it.

However, cycle time can be automatically calculated by correlating data from your Git activity with your issue tracker. Using tools like LinearB, you can even look at it in various ways: at the organization level, by team, by iteration, and even as deeply as a specific branch. 

## Cycle Time vs. Lead Time

If your goal is a more efficient engineering team, accurately planning iterations and delivering on promises is impossible if your dev team’s cycle time is too long. So, if we had to choose one metric to measure a team’s effectiveness, it would be cycle time vs lead time. 

![cycle time benchmarks](https://assets.linearb.io/uploads/cycle-time-benchmarks-1024x819.png)

You need to unblock your developers, and it’s not managing the items in the backlog slowing them down this sprint. Inspecting cycle time can show you exactly what’s holding up work in progress this week. And measuring cycle time in four phases takes your understanding of your development pipeline another layer deeper.

That’s not to say that measuring lead time isn’t valuable. It becomes a more useful metric once you’ve ensured your cycle time is low. If you know and can show that your developers are working quickly and agilely but you’re still running into delivery issues, you may have a capacity problem and it’s time to ask for more headcount or revisit priorities.

## How to Improve Lead Time & Cycle Time

Since cycle time is a subset of lead time, if you reduce your cycle time, you’re also reducing your lead time, at least a pretty large chunk of it. 

LinearB can help you reduce cycle time by showing you which part of the process needs immediate attention. Using our one-click context into cycle time, you can drill down into which stages take the longest or where work is getting bottlenecked. 

[![Cycle time breakdown. Dive into your data.](https://assets.linearb.io/uploads/cycle-time-deep-dive.png)](https://linearb.io/get-started/)Get context around cycle time bottlenecks in one click. Diving into your data has never been this easy. [Get started with our free-forever account today!](https://linearb.io/get-started)

Based on these insights, you can set team goals for improving the leading indicators that impact cycle time and ultimately lead time. Then tools like LinearB’s developer bot, WorkerB, can automate the improvement within your dev team.

**Breaking News! The most effective way to shorten your cycle time is to decrease the average PR size.** 

The most common reason devs spend too much time coding on one task is that they bit off more than they can chew. It is better to have many smaller PRs that are precisely scoped than a large one that contains many changes. 

Not only do small PRs get picked up faster, but they can be reviewed faster and they’ve been linked to higher quality code. Smaller PRs are less likely to create bugs, so developers are happy to merge them quickly. 

WorkerB bot can reinforce positive behaviors from your dev team using agreed up on Team Goals around PR size, high-risk work, review depth, pickup time and review time. Your devs can even approve PRs shorter than 5 lines right from Slack or MS Teams.

## The Best Way to Measure Engineering Efficiency 

Lead time and cycle time are common [DevOps metrics](https://linearb.io/blog/devops-metrics-and-kpis/) to measure engineering efficiency. However, lead time falls short when it comes to unblocking developers and optimizing workflow. That’s why expert tools like LinearB use cycle time as a more accurate measure of a team’s productivity.

But we encourage teams to go beyond measuring indicators of productivity like lead time and cycle time and actually start improving cycle time as well as other DORA metrics. 

By using our Engineering Benchmarks, Team Goals, and WorkerB bot, you can automate a developer workflow so your team members can deliver features faster and improve the overall quality of their output.

[](https://linearb.io/engineering-efficiency/)We know that improving engineering efficiency is important. Learn more about [our four-step recipe for improvement](https://linearb.io/engineering-efficiency/).

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

## Your next read

[![Cover image for AI ROI comes from measuring engineering outcomes on day one](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_ROI_comes_from_measuring_engineering_software_security_2400x1256_2c5eae0862?_a=BAVMn6ID0)](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Eng. Metrics

[AI ROI comes from measuring engineering outcomes on day one](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Kraken Engineering Operations Lead Nik Sudan details how to establish day-one data infrastructure to accurately measure AI ROI. Discover why raw token adoption...

[![Cover image for AI is rebuilding software delivery from SDLC to ADLC](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_rebuilding_software_delivery_2400x1256_3fd5887e75?_a=BAVMn6ID0)](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Eng. Metrics

[AI is rebuilding software delivery from SDLC to ADLC](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Discover how engineering organizations are transitioning from the traditional SDLC to an Agentic Development Lifecycle (ADLC). Learn why rising token costs...

[![Cover image for 8 million pull requests reveal where engineering productivity breaks down](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_8_million_pull_requests_2400x1256_03724bfbb2?_a=BAVMn6ID0)](https://linearb.io/blog/8-million-prs-engineering-productivity)

Eng. Metrics

[8 million pull requests reveal where engineering productivity breaks down](https://linearb.io/blog/8-million-prs-engineering-productivity)

8.1M pull requests reveal the gap between AI adoption and engineering impact, and why code review is the bottleneck blocking real productivity gains.

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Lead Time vs Cycle Time in Software Development",
  "url": "https://linearb.io/blog/lead-time-vs-cycle-time",
  "author": {
    "@type": "Person",
    "name": "Briana Johnson"
  },
  "datePublished": "2022-08-17T13:00:00.000Z",
  "dateModified": "2022-08-17T13:00:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1720000000/lead_time_vs_cycle_time_2eb314b5dc.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Which of these two key metrics is the best way to measure the productivity of dev teams? And more importantly, how do you start improving them?\n"
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)