Cycle Time Calculator
Cycle time measures how long it takes to complete a unit of work from start to finish. It is one of the four DORA (DevOps Research and Assessment) key metrics, which research shows are the strongest predictors of both IT performance and organizational performance. Reducing cycle time improves delivery frequency and responsiveness to change. Enter the start and end dates for multiple work items (user stories, tickets, or features) to calculate average cycle time, the 85th percentile, and your team's throughput rate in items per week.
Cycle time formula
cycle_time = delivery_date - work_start_date (days)
average = sum(cycle_times) / count
throughput = items_completed / (period_days / 7)
percentile(p) = sorted_values[ceil(p/100 * n) - 1]
Cycle time improvement strategies
- Limit WIP (work in progress) to expose bottlenecks and reduce multitasking.
- Break large stories into smaller, independently deliverable pieces.
- Reduce handoffs and waiting time between stages (code review, QA, deployment).
- Automate repetitive steps in the delivery pipeline: testing, builds, deployments.
- Track cycle time by work type: bugs typically have shorter cycle times than features.
Frequently asked questions
What is cycle time in software development?
Cycle time is the time elapsed from when work actively begins on a task to when it is delivered and ready for use. It measures process efficiency. A low cycle time means items flow quickly through the development pipeline. Cycle time is distinct from lead time, which includes the waiting period before work begins.
How is cycle time calculated?
Cycle time = delivery_date - work_start_date (in business days or calendar days, depending on convention). Track cycle time for multiple items and calculate the average and percentiles. The 85th percentile cycle time is a useful Service Level Expectation (SLE) - it tells you the cycle time that 85% of items are completed within.
What is the difference between cycle time and lead time?
Lead time starts when a customer or stakeholder requests work (when a ticket is created or added to the queue). Cycle time starts when the team begins actively working on it. Lead time = wait time + cycle time. Reducing cycle time requires process improvement; reducing lead time also requires reducing the work queue.
What is a good cycle time for software features?
There is no universal target since it depends on team size, feature complexity, and process maturity. High-performing DevOps teams (per DORA research) deploy frequently and have low change lead times. For user stories, a cycle time of 1-3 days is excellent; 3-7 days is good; above 14 days often indicates process or scope issues.
How does cycle time relate to throughput?
Little's Law connects cycle time, throughput, and work in progress (WIP): WIP = throughput * cycle_time. If cycle time increases but WIP stays constant, throughput decreases. Limiting WIP (Kanban's core principle) is the most direct way to reduce cycle time and increase throughput.
Official sources
- DORA: DORA Research Program - Accelerate State of DevOps Report.
- PMI: PMBOK Guide - Project Management Body of Knowledge.
Reviewed by the CalculatorHub team, edited by James Graham, 14 June 2026. See our methodology.