Calculator Inputs
Enter team totals for a selected period. The calculator converts those values into lead time, cycle time, queue time, throughput, stability, and forecast metrics.
Example Data Table
| Period | Completed Items | Coding Days | Review Days | QA Days | Waiting Days | Blocked Days | P50 | P95 |
|---|---|---|---|---|---|---|---|---|
| Sprint 12 | 18 | 42 | 16 | 14 | 20 | 8 | 4.3 | 7.4 |
| Sprint 13 | 21 | 47 | 18 | 16 | 17 | 6 | 4.0 | 6.9 |
| Sprint 14 | 19 | 45 | 17 | 15 | 19 | 7 | 4.5 | 7.1 |
This table shows the kind of summarized workflow totals commonly used for team dashboards and release planning.
Formula Used
1) Total Lead Time
Total Lead Time = Coding Days + Review Days + QA Days + Waiting Days + Blocked Days
2) Average Lead Time Per Item
Average Lead Time = Total Lead Time / Completed Items
3) Average Cycle Time Per Item
Average Cycle Time = (Coding Days + Review Days + QA Days) / Completed Items
4) Average Queue Time Per Item
Average Queue Time = (Waiting Days + Blocked Days) / Completed Items
5) Flow Efficiency
Flow Efficiency = Active Work Days / Total Lead Time × 100
6) Throughput
Throughput Per Day = Completed Items / Period Days
7) Lead Time Trend
Lead Change % = (Current Average Lead − Previous Average Lead) / Previous Average Lead × 100
8) Forecast and Stability
Forecast Days = Remaining Backlog / Throughput Per Day
Stability Score = P50 Lead / P95 Lead × 100
How to Use This Calculator
Start by selecting a reporting period, such as a sprint, week, or month. Enter how many items your team completed in that period.
Next, enter the total days spent in coding, review, QA, waiting, and blocked states for those completed items. These can come from issue tracking exports or workflow analytics tools.
Add your previous average lead time and target lead time to compare current performance against past results and delivery goals. Then enter P50, P85, and P95 values if you track percentiles.
Finally, enter your remaining backlog items. After submission, the dashboard shows average lead time, cycle time, queue time, throughput, flow efficiency, a forecast to finish backlog work, and a bottleneck stage.
Frequently Asked Questions
1) What does lead time mean here?
Lead time is the full elapsed time from work start until delivery, including active work, waiting, and blocked periods.
2) How is cycle time different from lead time?
Cycle time covers active work stages only, such as coding, review, and testing. Lead time also includes queues and delays.
3) Why track P50, P85, and P95 values?
Percentiles show delivery consistency. P50 reflects a typical item, while P95 helps estimate risk for slower work and planning buffers.
4) What is flow efficiency?
Flow efficiency measures the share of total lead time spent on actual work. Higher percentages usually mean less queue waste.
5) What does the bottleneck stage tell me?
It identifies the stage with the highest average days per item. That stage is often the best place to investigate process delays first.
6) Can I use this for weekly or monthly dashboards?
Yes. The calculator works for any time window, as long as period days and completed items match the same reporting range.
7) Why estimate backlog clearance time?
Forecasting backlog days helps with release planning, staffing conversations, and delivery expectations based on current throughput rather than guesses.
8) What if I do not have percentile data?
You can still use the calculator. Leave percentile values at zero, and the dashboard will still compute lead, cycle, queue, throughput, and forecast metrics.