What is Lead Time?
The total elapsed time from when a work item is first requested until it is delivered to the customer, spanning both queue time and active development.
Lead Time in Agile product development measures the total elapsed time from when a work item is first requested or entered into the backlog until it is delivered to the customer. Lead Time encompasses both the time work spends waiting in a queue (before active development begins) and the active development time (Cycle Time). Reducing Lead Time is a strategic goal because it directly correlates with faster feedback loops, faster response to customer needs, and competitive advantage.
Formula
Lead Time = Queue Time + Cycle TimeQueue Time = time from request to active work start. Cycle Time = time from active work start to completion. Lead Time = Delivery Date - Request Date. Example: Feature requested January 1, development started January 8 (7 days queue time), completed January 13 (5 days cycle time). Lead Time = 12 days. Reducing WIP limits and improving backlog refinement reduces queue time directly.
Industry Benchmarks
- High-performing DevOps teams: median lead time under 1 day for production deployments
- Elite software teams: lead time from code commit to production under 1 hour
- Feature lead time (request to release): under 2 weeks for agile product teams
- Lead time variability matters as much as average: P95 under 3x median indicates predictability
- Teams with lead times over 4 weeks typically have significant WIP or planning bottlenecks
When to Use Lead Time
- Measuring the customer-perceived time from request to value delivery
- Identifying whether delivery slowdowns are caused by queue time (planning problems) or cycle time (execution problems)
- Setting internal SLAs for different types of work (bugs vs features vs tech debt)
- Demonstrating continuous improvement progress to leadership through trend data
- Confusing lead time with cycle time in reports, which incorrectly attributes delays to execution when they are actually in planning and queuing
- Measuring lead time only from when work starts development, which understates the customer-perceived waiting time
- Reducing lead time by rushing work through without adequate testing, trading short-term speed for long-term quality debt
- The biggest lever for reducing lead time is almost always reducing queue time, not speeding up development - work on WIP limits and backlog prioritisation first
- Track lead time by work type (bug, feature, chore) separately because each has different drivers and acceptable thresholds
- Use a cumulative flow diagram to visualise how work accumulates and flows through each workflow stage to pinpoint bottlenecks
Related Terms
Free Lead Time Calculator
Skip the spreadsheet. Enter your numbers in the free Cycle Time Calculator and get a benchmarked Lead Time result in seconds.