What is Cycle Time?
Cycle Time measures the duration from when active work starts to completion; Lead Time measures from when work is first requested to when it is delivered to the customer.
Cycle Time measures the elapsed time from when active work begins on a task until it is marked as done. It is distinct from Lead Time, which measures from initial request to delivery. Cycle Time is the metric teams can most directly control by improving processes, reducing batch sizes, and removing blockers. Together, Cycle Time and Lead Time reveal both how fast the team works and how long work waits before being started.
Formula
Cycle Time = Work Completion Date - Work Start DateLead Time = Delivery Date - Request Date (includes queue time). Cycle Time = Completion Date - Active Work Start Date. The gap between Lead Time and Cycle Time is queue time - how long work waited before anyone started it. Example: Feature requested Monday, work started Wednesday, completed Friday. Lead Time = 5 days, Cycle Time = 3 days, Queue Time = 2 days.
Industry Benchmarks
- World-class software teams: median cycle time of 1-2 days for individual tasks
- High-performing agile teams: cycle time under 3 days for most user stories
- P95 cycle time (95th percentile) should be less than 3x the median to indicate consistency
- Queue time exceeding cycle time indicates a planning or prioritization bottleneck
- Cycle time trending upward over 4+ weeks signals growing technical debt or team capacity issues
When to Use Cycle Time
- Diagnosing delivery bottlenecks by comparing cycle time distributions across workflow stages
- Setting SLA commitments for bug fix response times based on historical cycle time data
- Measuring the impact of process improvements such as reducing work-in-progress limits
- Identifying outlier tasks with anomalously long cycle times that need root cause analysis
- Confusing cycle time with lead time and using them interchangeably in reports, which misleads stakeholders about where delays occur
- Measuring cycle time only at the task level and missing stage-level bottlenecks within the workflow
- Targeting average cycle time reduction without also reducing cycle time variance, which matters more for predictability
- Use a cycle time scatterplot (time to complete on Y axis, completion date on X axis) to spot trends and outliers more clearly than averages alone
- Limiting work-in-progress (WIP) is the single most effective lever for reducing cycle time
- Decompose stories into smaller tasks to reduce cycle time and increase delivery frequency without changing team capacity
Related Terms
Free Cycle Time Calculator
Skip the spreadsheet. Enter your numbers in the free Cycle Time Calculator and get a benchmarked Cycle Time result in seconds.