Cycle Time Calculator

Cycle time measures the elapsed time from when work actually begins on an item to when that item is completed and ready for delivery. It is one of the most fundamental flow metrics in project management and a cornerstone of Kanban and Lean thinking. Unlike lead time, which includes the waiting period before work starts, cycle time focuses exclusively on active processing, making it the purest measure of your team's execution speed.

In the PMBOK Guide's framework, cycle time connects directly to the Control Schedule process in the Monitoring and Controlling Process Group. For predictive life cycles, schedule performance is typically measured through earned value metrics like Schedule Variance and Schedule Performance Index. For adaptive and hybrid life cycles, however, cycle time provides a more granular, actionable signal. When cycle time increases, it tells you that your delivery pipeline is slowing down before the impact shows up on a Gantt chart.

Understanding cycle time distribution is just as important as knowing the average. Most teams discover that their cycle times follow a right-skewed distribution: most items finish quickly, but a few outliers take significantly longer. This is why tracking percentiles (50th, 85th, and 95th) gives you a much more reliable picture of delivery capability than averages alone. The 85th percentile cycle time, for example, tells you that 85% of your items finish within that timeframe, which is far more useful for setting service-level expectations than a mean that can be distorted by a single outlier.

Start Date is the date (or timestamp) when the team actively begins working on a task. This is not when the request was submitted or when the item entered the backlog; it is the moment work transitions from "waiting" to "in progress."

End Date is the date when the task meets its definition of done and is considered complete. In Kanban, this corresponds to the item moving into the rightmost column (typically "Done" or "Deployed").

Process Efficiency is a derived metric calculated as Cycle Time divided by Lead Time, expressed as a percentage. A process efficiency of 15-20% is typical for knowledge work, meaning that 80-85% of lead time is actually wait time. World-class Lean organizations target 40% or higher by aggressively eliminating handoff delays, approval queues, and context-switching overhead.

• Confusing cycle time with lead time — This is the most common error. Cycle time starts when work begins; lead time starts when the request is made. Using the wrong metric for planning will systematically underestimate delivery timelines.
• Relying on averages alone — Averages mask outliers and give a false sense of predictability. Always use percentile-based analysis for commitments and forecasts.
• Ignoring blocked time — If a task sits "in progress" but is blocked for 3 of 5 days, the cycle time still counts those blocked days. This is by design: blocked time is real delay that your customer experiences.
• Not separating work types — Mixing bug fixes (typically fast) with new feature development (typically slow) in the same cycle time dataset creates misleading statistics. Always segment by work category.

On the PMP exam, cycle time questions typically appear in the context of Agile and Kanban methodologies within the Executing and Monitoring and Controlling domains. Know the distinction between cycle time, lead time, and takt time. Cycle time measures actual work duration, lead time measures the total customer-facing wait, and takt time is the rate at which you need to produce to meet customer demand (available work time divided by customer demand).

Be prepared for questions that give you a scenario where cycle time is increasing and ask you to identify the root cause or recommend corrective action. The correct answer usually involves either reducing WIP (which reduces context-switching and queue delays), addressing a specific bottleneck stage, or breaking large items into smaller ones to improve flow consistency. Remember: in Kanban, the primary lever for improving cycle time is reducing WIP limits, not adding people.

You should also understand how cycle time relates to earned value in hybrid environments. If your cycle time is increasing, your Schedule Performance Index will trend below 1.0. The Agile Practice Guide specifically highlights cycle time as a leading indicator that provides earlier warnings than traditional earned value metrics, which is why hybrid teams should track both.