Throughput answers the most practical question in delivery: how much does your team actually finish? It is the number of work items completed in a given period, and it is the honest, estimation-free foundation of realistic planning and forecasting. This guide explains what throughput is, how Flow Metrics Charts for Jira Cloud measures it, how to read the chart, and how to forecast delivery from it.
What is throughput?
Throughput is the count of work items a team completes per unit of time — typically per day, week, sprint or month. It is also called flow velocity. Unlike story-point velocity, throughput needs no estimation: it simply counts the work that crossed the finish line. That makes it objective, hard to game, and easy to explain to anyone — including stakeholders who neither know nor care what a story point is.
Throughput vs story-point velocity
Story-point velocity measures estimated effort completed; throughput measures items completed. Because points are subjective and re-calibrated by every team, velocity cannot be compared across teams or reliably over time. Throughput counts real, finished work, so it stays comparable as teams and estimation habits change. If your team struggles with estimation — or has abandoned points entirely — throughput lets you plan with confidence anyway. For the leadership-facing case, see Beyond the Burndown.
How throughput is measured in Jira
Flow Metrics Charts counts resolved issues in each period for your chosen data source — a project, board, saved filter, user or custom JQL query. You can view throughput by day, week or month, and each period reports the minimum, average and maximum so you see both your typical pace and your range. Because it is unit-agnostic, throughput works equally well for Scrum stories, Kanban cards and Jira Service Management requests.
How to read the throughput chart
Look at consistency as much as the average:
- A steady line means a predictable system you can plan around. Pair it with system stability to quantify how reliable that pace is.
- A rising trend is usually healthy — more value delivered per period — as long as quality and work mix hold steady.
- A sudden drop is a signal, not a verdict: investigate interruptions, attrition, larger items, growing rework or dependencies before drawing conclusions.
- A jagged line points to variability worth understanding — often inconsistent item sizes or too much work in progress.
Why throughput matters for your business
Throughput is the foundation of capacity planning and delivery forecasting. Combined with the size of your backlog it answers “when will this be done?” with a range grounded in real history rather than optimism. It is also the plainest-language way to show delivery performance to executives: a steady or rising throughput signals healthy delivery, while a drop flags an impediment worth attention — no story points required.
How to forecast with throughput
The simplest forecast divides remaining scope by average throughput: 100 backlog items at an average of 20 per week is roughly five weeks of work. For a more honest forecast, use your throughput range — the recent minimum and maximum — to express best- and worst-case dates, or feed the distribution into a Monte Carlo simulation. Throughput also anchors Little’s Law (lead time is approximately work in progress divided by throughput), which is why holding throughput steady while cutting work in progress shortens lead time.
How throughput connects to the other flow metrics
Throughput is the delivery-rate term in the flow-metrics system. Read it beside flow time (how long work takes), flow load (how much is in progress) and predictability (how reliable the pace is). A rising throughput bought by ballooning WIP or collapsing quality is not real progress — which is why throughput is best read as part of the whole picture. Throughput isn’t one of the four official DORA keys, but many teams track it alongside them — see DORA Metrics in Jira for the four measures of software delivery performance and where they overlap with flow metrics like this one.
Track throughput in Jira
Flow Metrics Charts for Jira Cloud counts throughput directly from your Jira history — no story points, spreadsheets or exports — on an interactive board and in configurable dashboard gadgets, with Rovo AI explaining shifts in your delivery rate automatically. Start with the flow metrics for Jira overview, or read the canonical explainer, Flow Metrics Explained.
Frequently asked questions
What is throughput in Agile?
Throughput is the number of work items a team completes in a period, such as issues closed per week. Also called flow velocity, it counts finished work rather than estimated effort, which makes it objective and comparable over time.
What is the difference between throughput and velocity?
Velocity usually measures completed story points (estimated effort); throughput counts completed items. Because points are subjective, throughput is more comparable across teams and more stable over time.
How is throughput measured in Jira?
Flow Metrics Charts for Jira counts resolved issues per period for your chosen project, board, filter, user or JQL, and reports minimum, average and maximum for each period.
2 Comments
Leave your reply.