Definition
Throughput
Throughput is the number of work items a team completes in a given period — issues finished per week, for example. It is the simplest flow metric: a direct count of output over time. Tracked across periods, throughput reveals a team's real delivery capacity and is the basis for probabilistic, estimate-free forecasting.
Key takeaways
- Throughput is the count of work items a team completes in a period — issues finished per week, for example — the simplest flow metric.
- It requires no estimation at all, just the completion events you already have, which makes it reliable when issues are similar in size.
- Sampling historical throughput and running a Monte Carlo simulation answers 'how likely to finish by month-end' with a probability, not a false-precision date.
- Throughput pairs with cycle time: throughput tells you how much flows through; cycle time tells you how fast each item moves.
Throughput counts finished work, full stop: how many issues reached 'done' this week, this cycle, this month. Its appeal is that it requires no estimation at all — you do not need story points or hour guesses, just the completion events you already have. For teams that keep issues reasonably similar in size, throughput alone is a remarkably reliable planning signal.
Where it shines is forecasting. By sampling a team's historical throughput and running a simple Monte Carlo simulation, you can answer 'how likely are we to finish these forty issues by month-end' with a probability rather than a false-precision date. This estimate-free approach sidesteps the entire debate about points and is often more accurate than committing to a single number.
Throughput pairs naturally with cycle time: throughput tells you how much flows through the system, cycle time tells you how fast each item moves. Read together they give a complete picture of flow, and both fall straight out of issue state changes with no extra ceremony.
Planoda charts throughput per period from completion events, so teams can forecast on real historical flow instead of optimistic estimates.
Related terms
- Cycle TimeCycle time is how long an issue takes from the moment work actively starts on it to the moment it is done. Measured in hours or days, it captures the team's hands-on flow efficiency. Shorter, more consistent cycle times mean a more predictable system — the core flow metric Kanban teams optimize.
- Lead TimeLead time is the total elapsed time from when an issue is first created or requested to when it is delivered. Unlike cycle time, it includes the waiting period in the backlog before work begins. Lead time reflects the customer's experience of how long a request actually takes end to end.
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- KanbanKanban is a visual workflow method that maps work onto a board of columns representing stages — typically backlog, in progress, and done. Cards move left to right as work advances. It emphasizes continuous flow, making bottlenecks visible, and limiting work in progress rather than committing to fixed time-boxes.