Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
The Kanban Throughput run chart helps you make sense of how work actually moves through your system by showing how much is completed over time and how stable that output is.
Instead of relying on a single perspective, it lets you combine data from multiple boards, adjust how time is analyzed, and switch between different visual and statistical views. This makes it easier to move from a rough understanding of delivery pace to a more precise analysis of patterns, variability, and capacity distribution.
Whether you’re looking at one team or coordinating work across several workflows, Agile Throughput Charts give you a clearer picture of how your delivery system behaves.
✅ Product Owner: I rely on throughput trends to understand how quickly backlog items are actually completed. This helps me prioritize work more effectively and align expectations with stakeholders based on real delivery capacity rather than assumptions.
✅ Agile Coach: I use throughput analysis to help teams focus on flow and system behavior instead of isolated metrics. It’s a practical way to demonstrate variability, highlight improvement areas, and support continuous improvement initiatives.
✅ Delivery Manager: I monitor throughput across multiple boards to ensure delivery stays aligned with expectations. If trends show declining or unstable throughput, I can address risks early, rebalance workload, or adjust commitments.
✅ Program Manager: I rely on throughput trends to evaluate whether initiatives are progressing at the expected pace. The chart helps me detect delays early and make informed decisions about scope, sequencing, or prioritization.
The Throughput run chart for Kanban boards lets you define which data is included in the analysis, so you can measure throughput across the full delivery system with a precise, relevant dataset.
Instead of being limited to a single team’s board, you can aggregate throughput across multiple boards or projects. This is especially useful when delivery spans several teams or when work is distributed across different Jira boards. You can further refine the scope using an Issue filter, focusing only on relevant work - such as a specific issue type, epic, release, or any custom JQL query.
✅ This feature is helpful for:
Once you’ve defined the scope, the next step is deciding on the timeframe for the analysis and how the data is grouped within it.
The Agile Throughput run chart for Kanban teams lets you configure the time interval by selecting a rolling window (for example, last N days, weeks, or months) or defining a custom date range. On top of that, you can group completed work into different time intervals - from daily and weekly views to longer periods like monthly or quarterly. Shorter groupings highlight variability and fluctuations in delivery, while longer ones smooth out noise and make overall throughput trends easier to interpret.
✅ This feature is helpful for:
With the data in place, you can explore it from different perspectives by switching between chart views. Line and bar charts show total throughput per period, making it easy to spot trends, compare intervals, and assess delivery pace over time.
For deeper analysis, the stacked bar view lets you break down throughput by any Jira field, such as issue type, assignee, team, or component, revealing how capacity is distributed across different types of work.
✅ This feature is helpful for:
To move beyond raw throughput values, the chart lets you overlay customizable statistical benchmarks on the data.
You can display metrics such as the mean, median (P50), and higher percentiles (P85, P95, or any custom value) to understand what typical and high-confidence delivery looks like over time. These indicators help you separate normal variation from meaningful changes in performance.
In addition, you can apply moving statistics calculated over a selected number of recent intervals. This allows you to track how throughput evolves, rather than relying only on long-term averages.
✅ This feature is helpful for:
High-level metrics are only useful if you can understand what drives them.
The Kanban Throughput run chart lets you drill down into any time interval to open a detailed breakdown of completed work. You can group results by any two Jira fields, such as team, assignee, or component (), to see how different segments contribute to overall throughput.
From there, you can go one level deeper into the Issue list ( ), which shows the exact items included in the selected period. Each issue is linked back to Jira, allowing you to inspect, validate, or update the data directly.
✅ This feature is helpful for:
The Kanban Throughput run chart in the Jira dashboard lets you tailor how throughput is calculated so the data reflects how your teams actually deliver work in a continuous flow.
You can define throughput based on custom column transitions, selecting which workflow movements count as completed work. It’s also possible to choose an estimation field, such as issue count (most common for Kanban), story points, or any numeric field, depending on how your teams measure delivery. When working with multiple boards, these calculation rules can be configured individually for each board, ensuring accurate and consistent throughput measurement across different workflows.
Once your chart is set up, you can easily share it with stakeholders.
Add it to a Jira dashboard to provide real-time visibility into delivery trends, or export it as PNG or PDF to include in presentations, reports, or documentation.
Jira does not provide a dedicated throughput chart for Kanban teams. Native reports are primarily built around cycle time (Control Chart) or sprint-based delivery (Velocity), which makes them less suitable for analyzing throughput in a continuous flow environment.
In practice, this creates several gaps when working with Kanban:
The Kanban Throughput Chart addresses these limitations by providing a flexible and configurable view of delivery in a flow-based system.
With it, you can:
Use these examples to create your own Kanban Throughput run report use cases on the Jira Dashboard.
Both Jira apps (plugins) featured here offer a 30-day free trial and are completely free for teams of up to 10 users:
The Agile Reports and Gadgets app includes Kanban Throughput run chart functionality plus a wide range of additional charts and reports.
.svg)
.png)
.png)
