Cycle Time measures the duration from when work begins to when it is completed. Lead Time measures from when work is requested to when it is delivered, including queue time. The formula is Lead Time = Request Date to Delivery Date; Cycle Time = Work Start to Work Complete. Compare similar work using consistent start and finish boundaries. PM Toolkit's free cycle time calculator helps product managers track delivery performance with percentile analysis (P50, P85, P95) and bottleneck identification.
What is Cycle Time vs Lead Time?
Cycle time measures how long work takes from start to completion. Lead time measures the total time from request to delivery, including wait time. Together, they reveal delivery efficiency and bottlenecks in product development workflows.
Formulas
Cycle Time = Completion Date - Work Start Date
Lead Time = Delivery Date - Request Date
Throughput = Work Items Completed / Time Period
Little's Law: WIP = Throughput x Cycle Time
Set a local baseline
Use completed items from a comparable workflow to set a baseline. DORA change lead time measures commit to production, so its bands do not describe request-to-delivery lead time.
Ask Claude, Cursor, or ChatGPT to run this calculator.
This calculator isn't in MCP yet — but install once for 17 others your AI can call.
Start with
Cycle Time Calculator
Measure elapsed time from work start to completion and review the distribution of completed items.
Updated
Ready
Start by importing CSV data, using sample data, or manually adding cycle-time entries above.
Understanding Cycle Time for Software Development Teams
Cycle Time measures elapsed time from "In Progress" to "Done", including any waiting after work starts. Lead Time also includes the time before work starts. Define these boundaries consistently when comparing delivery times.
Cycle Time vs Lead Time: Key Differences
Cycle Time: Measures elapsed time from start to completion, including waiting after work starts. Use this for sprint planning, capacity planning, and process optimization.
Lead Time: Includes waiting time before work begins (Lead Time = Wait Time + Cycle Time). Use this for customer commitments and stakeholder expectations.
Compare Lead Time and Cycle Time to identify waiting before work starts. Examine individual workflow stages to investigate delays after work has started.
Choosing a comparison
Compare similar work using the same start and finish boundaries. The Kanban Guide uses historical cycle time to inform service-level expectations. Those expectations are forecasts, not guarantees.
DORA change lead time measures commit to production. Its performance bands should not be applied to ticket cycle time or request-to-delivery lead time.
How to Improve Your Team's Cycle Time
Focus on Consistency First: Review variation as well as average Cycle Time. A consistent 6-day cycle is easier to forecast than a range of 2-15 days with a 5-day average.
Common Bottlenecks and Solutions
- Code Review Delays: Implement PR buddy systems and async review processes to reduce 3+ day waits
- Testing Bottlenecks: If testing queues cause delays, assess parallel testing or automation.
- High Work-in-Progress: For a stable system, average WIP equals throughput times average cycle time. Lower WIP corresponds to shorter cycle time if throughput stays unchanged.
- Large Pull Requests: Big PRs sit in review longer and are harder to test; break them into smaller chunks to move work through faster
- Context Switching: Limit developers to 1-2 active items to maintain focus and flow
Agile Best Practices for Cycle Time Optimization
Sprint Planning: If P85 is 8 days, about 85% of recorded items finished within 8 days. This does not determine items per developer in a 10-day sprint; also review throughput and work in progress.
Daily Standups: Focus on items approaching P85 cycle time rather than just status updates. Treat long-running items as priority issues requiring immediate attention.
Retrospectives: Review cycle time trends alongside work mix, queues, and team feedback. Rising times alone do not establish burnout or quality problems.
What is Cycle Time and Lead Time?
Cycle time runs from starting a work item to completing it, including waiting after work starts. Lead time runs from the original request to completion. Their difference measures the time before work started.
Cycle and Lead Time Formulas
Cycle Time = Completed Date - Started Date; Lead Time = Completed Date - Requested Date
Metric boundary
DORA measures code commit to production. Its change lead time is different from this calculator’s request-to-delivery lead time.
DORA 2024: change lead time definitionRate this calculator:
Cycle time benchmarks
| Segment | Benchmark |
|---|---|
| Cycle time | Use your own completed-item history |
| DORA change lead time | Commit to production |
Common questions
What is the difference between cycle time and lead time?
Cycle time is elapsed time from starting work to completing it, including waiting after work starts. Lead time runs from the request to delivery, including the wait before work starts. Define the start and end events consistently when comparing tasks.
What is a good cycle time for software development?
Compare similar work with the same start and end events. DORA’s change lead time runs from a code commit to production; it is not the same as request-to-delivery lead time or task cycle time. Use your own distribution to find delays rather than treating DORA bands as task-time standards.
How do I reduce cycle time?
Reduce cycle time by breaking work into smaller batches, limiting work in progress (WIP), automating CI/CD pipelines, reducing code review turnaround, and eliminating handoff delays between teams. Start by measuring where time is spent in each workflow stage.