Kanban Cycle Time Tracking: A Weekly Workflow for Forecasting Delivery Dates
kanbancycle-timeforecastingdelivery-managementmetrics

Kanban Cycle Time Tracking: A Weekly Workflow for Forecasting Delivery Dates

BBoards.cloud Editorial Team
2026-11-21
7 min read

Track kanban cycle time consistently, calculate useful percentiles, and turn weekly flow data into more reliable delivery forecasts.

Reliable delivery forecasts begin with reliable cycle-time data. This guide gives you a repeatable weekly workflow for defining kanban cycle time, recording completed work, calculating useful percentiles, setting service-level expectations, and communicating delivery dates as ranges rather than guesses.

Overview

Kanban cycle time is the elapsed time between two agreed points in your workflow. Most teams measure it from the moment work starts to the moment it is finished, but the exact points must be defined before the metric can be useful. For example, a development team might measure from In Progress to Done. A support team might measure from Assigned to Resolved.

Cycle time is different from lead time. Lead time usually includes the wait before work begins, such as the period between a request being submitted and a team member starting it. Cycle time focuses on active delivery. Both measures can be valuable, but combining them creates confusing forecasts.

A kanban board or kanban board software can provide the event history needed for cycle-time tracking, provided cards move through clearly defined columns and completion dates are recorded consistently. You do not need a complex reporting system to begin. A spreadsheet or task management tool with start and finish timestamps is enough for a small team. The important part is using the same rules every week.

A practical forecasting process has five stages:

  1. Define the start and finish points.
  2. Capture cycle time for each completed item.
  3. Review the distribution, not just the average.
  4. Set a service-level expectation from historical results.
  5. Use the result to communicate a delivery range and review it regularly.

Checklist by scenario

For a new team or new board

  • Write down the exact event that starts the clock, such as moving a card into In Progress.
  • Write down the exact event that stops the clock, such as moving a card into Done or Released.
  • Choose one unit of time, usually calendar days or working days, and use it consistently.
  • Make sure every card has a clear completion state and a recorded completion date.
  • Decide how to handle paused work, blocked cards, reopened items, and split cards.
  • Start collecting data before using it to make firm delivery commitments.

For a team with existing data

  • Export or review the last several weeks of completed cards.
  • Remove duplicate records and correct missing or obviously invalid timestamps.
  • Group comparable work together. A tiny configuration change and a large feature may need separate views.
  • Sort cycle times from shortest to longest.
  • Calculate the median and at least one higher percentile, such as the 85th or 90th percentile.
  • Compare the current distribution with the previous review period.

For forecasting a single item

  • Confirm that the item is genuinely ready to start.
  • Check whether its size and type resemble the completed items in your historical sample.
  • Use a typical cycle time for a likely estimate and a higher percentile for a more conservative range.
  • Check the board for blocked work, active work-in-progress, holidays, planned interruptions, or dependencies.
  • Communicate the estimate as a range, for example, “likely within four to seven working days,” rather than as an exact date.

For forecasting several items

  • Confirm the team’s capacity and current work-in-progress before adding new commitments.
  • Order the work by the team’s agreed prioritization rules.
  • Use historical throughput or cycle-time simulations when the forecast covers a larger batch.
  • Separate a forecast from a promise. A forecast describes what the current evidence suggests; a commitment also depends on scope, capacity, and business decisions.
  • Record the assumptions beside the forecast so they can be checked later.

Cycle-time tracking table

Use a table like this in your project tracking board, reporting view, or spreadsheet. The exact columns can be adapted to your workflow.

ItemStartedFinishedCycle timeTypeNotes
API validation updateMondayWednesday2 working daysChangeOne brief review delay
Access-control fixTuesdayFriday3 working daysBugBlocked by test environment
Usage reportWednesdayFollowing Tuesday4 working daysFeatureSplit into two cards

What to double-check

Definitions and timestamps

Forecasts are only as consistent as the events behind them. Confirm that moving a card into a column means the same thing for everyone. If developers start work before moving a card, your recorded cycle time will be longer than the actual active time. If cards remain in Done while awaiting release, decide whether your finish point is completion or release.

Percentiles instead of averages

An average can be distorted by one unusually long item. Percentiles show how the distribution behaves. To calculate one manually, sort the completed cycle times from lowest to highest and select the value at the chosen position. For a small sample, treat the result as directional rather than precise.

Suppose the last ten comparable items took 2, 2, 3, 3, 4, 4, 5, 6, 8, and 12 working days. The median is between 4 and 4, so a typical item took about 4 days. A high percentile will be closer to the longer end of the list. You might communicate a typical forecast of roughly four working days and a service-level expectation of up to eight or twelve working days, depending on the percentile and the level of confidence you need.

Service-level expectations

A service-level expectation, or SLE, is a target range for how long work is expected to take under defined conditions. It is not a guarantee. Document the item type, start and finish points, time unit, historical window, and percentile used. For example: “For standard engineering changes that enter In Progress, 85% are expected to reach Done within seven working days.” Review whether the expectation still matches current data.

Outliers and split work

Do not automatically delete a slow item. First ask what it reveals. A long cycle time may indicate blocked work, unclear requirements, excessive work-in-progress, or a dependency outside the team’s control. Mark the cause and consider reporting normal work and exceptional work separately.

Split work can also change the result. Splitting a large item into several smaller cards may lower measured cycle time without improving the delivery of the original outcome. Define what a completed card represents, and avoid comparing data sets that use materially different slicing rules.

Common mistakes

  • Using cycle time as a performance score. The metric is most useful for improving flow and making forecasts, not ranking individuals.
  • Changing definitions midstream. If the start or finish point changes, label the transition and avoid treating the old and new data as identical.
  • Forecasting from too little data. A handful of cards can provide an initial signal, but not strong certainty.
  • Ignoring waiting time. A card may be active but waiting for review, approval, testing, or another team. Track those states if they affect delivery.
  • Reporting only the fastest work. A fast median without a higher percentile can create unrealistic expectations.
  • Overloading the board. High work-in-progress often increases waiting and makes the historical forecast less relevant to current conditions. Review your kanban WIP limits when cycle time rises.
  • Confusing a forecast with a deadline. State the confidence level, assumptions, and risks beside the date range.

For a broader operational review, pair cycle-time analysis with a capacity review using the weekly kanban capacity planning method. If intake quality is affecting the data, revisit your task intake and prioritization matrix.

When to revisit

Review the data once a week, using the same short checklist:

  1. Add every item completed since the previous review.
  2. Check for missing timestamps, reopened cards, split work, and unusually long items.
  3. Compare the current median and selected percentile with the prior period.
  4. List aging work that has exceeded the current service-level expectation.
  5. Identify the main cause of delay: blocked work, review queues, unclear intake, dependencies, or excess work-in-progress.
  6. Update forecasts for active and upcoming work using the current distribution.
  7. Share the assumptions and ranges with people who depend on the forecast.

Revisit the definitions before seasonal planning cycles, after a major workflow change, when teams or responsibilities change, or when the board is reorganized. Update reporting instructions whenever your kanban board software changes its statuses, timestamps, filters, or export behavior. At least once a year, review whether your item types, percentile choice, and service-level expectations still reflect how work is delivered.

Keep the process lightweight. A useful cycle-time review should end with a clearer forecast and one or two flow improvements, not a larger reporting burden. If the numbers become difficult to explain, return to the basics: consistent start and finish points, comparable work items, visible blockers, and forecast ranges grounded in recent completed work.

Related Topics

#kanban#cycle-time#forecasting#delivery-management#metrics
B

Boards.cloud Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.