Lead Time Calculator
Lead time is a core DevOps and Kanban metric measuring the end-to-end elapsed time from a work request to delivered value. Unlike cycle time (which only measures active work time), lead time includes the waiting period in the backlog before work starts. Reducing lead time is a direct measure of your team's responsiveness to customer and business needs. Enter total lead times and work start times (to calculate wait time) for your recent work items to get average, median, and 85th percentile lead time, plus the ratio of wait time to active work time, which reveals where the most improvement opportunity lies.
Lead time formula
lead_time = delivery_date - request_date (days)
wait_time = work_start_date - request_date (days)
cycle_time = delivery_date - work_start_date (days)
flow_efficiency = cycle_time / lead_time * 100%
Typical knowledge worker flow efficiency is 5-15%. World-class Lean organizations achieve 30-50%.
Lead time improvement strategies
- Reduce queue size: limit WIP and keep the backlog small and prioritized.
- Improve replenishment: fill the queue only when team capacity is available, not in large batches.
- Automate deployment and testing to shrink active cycle time.
- Track wait time separately from cycle time to identify whether the bottleneck is in the queue or the work itself.
- Set and communicate Service Level Expectations so stakeholders know realistic delivery windows.
Frequently asked questions
What is lead time in software development?
Lead time is the elapsed time from when a work item is requested (a ticket is created or a feature is added to the backlog) to when it is delivered to the customer. It includes both the time waiting in a queue before work starts (wait time) and the time actively worked on (cycle time). Lead time = wait time + cycle time.
How is lead time for changes defined in DORA metrics?
DORA's Lead Time for Changes (LTFC) specifically measures the time from code committed to that code successfully running in production. It is one of the four key DORA metrics. Elite DevOps performers achieve LTFC of less than 1 hour; high performers achieve less than 1 day; medium performers take 1-7 days; low performers take more than a week.
How do I reduce lead time?
Reduce queue size (limit WIP), improve flow through the system (reduce wait times between stages), break work into smaller batches, automate manual gates (testing, deployment), and remove blockers quickly. Lead time reduction follows the same principles as lean manufacturing's flow efficiency improvement.
What is the difference between lead time and cycle time in Kanban?
In Kanban, cycle time typically measures from when a card enters 'In Progress' to when it reaches 'Done'. Lead time measures from when the card was created (arrived in the 'To Do' column) to 'Done'. The difference is the wait time: how long the item sat in the backlog before anyone started working on it.
What is a Service Level Agreement (SLA) in the context of lead time?
An SLA or Service Level Expectation (SLE) for lead time is a commitment about how quickly work requests will be fulfilled. For example, an SLE might state that 85% of bug fix requests will be resolved within 5 business days. Teams use historical lead time percentiles to set achievable SLEs and communicate them to stakeholders.
Official sources
- DORA: DORA Research Program - State of DevOps Reports.
- PMI: PMBOK Guide - Project Management Body of Knowledge.
Reviewed by the CalculatorHub team, edited by James Graham, 14 June 2026. See our methodology.