Agile Throughput Charts for Jira Dashboard

Q: What is a Throughput chart in Agile?

A Throughput Chart is a visual Agile tool that shows how much work a team completes over time. It tracks the number of issues finished in each period (such as days, weeks, or sprints), helping teams understand delivery pace and identify trends in their output.

Q: What questions does a Throughput chart answer?

A throughput chart helps answer: How much work does the team typically complete in each period? Is delivery stable or highly variable? What throughput levels occur most frequently? How predictable is our delivery? and Where is team capacity actually spent?

Q: How do you calculate throughput in Agile?

Traditionally, Throughput is calculated using the number of completed work items that transition to Done within a defined time bucket, like a day, week, or sprint. Tools like the Agile Throughput Chart aggregate this directly from Jira workflows.

Q: What is the difference between throughput and velocity?

Throughput measures the amount of completed work items within a given time period, while velocity measures the amount of estimated work completed (usually in story points). Throughput focuses on actual completed items rather than estimation accuracy.

Q: What is a good throughput for an Agile team?

There is no universal “good” throughput value. The most important factor is consistency over time. Stable throughput helps teams understand delivery capacity and plan future work more reliably.

Q: How is throughput used for forecasting?

Historical throughput data helps identify typical delivery ranges and variability. This data is used for probabilistic forecasting methods, such as Monte Carlo simulations, to support more realistic planning.

Q: Can I visualize cross-team throughput in one chart?

Yes. Agile Throughput Charts support cross-team analysis by aggregating data from multiple sources, including boards, projects, releases, issue hierarchies, epics, and custom JQL filters into a single chart.

Q: How to add Agile Throughput Charts to a Jira dashboard?

Install the app from the marketplace, then open your Jira dashboard, browse the gadget library, and add the 'Agile Throughput Charts by Broken Build' gadget. It appears instantly and is ready for configuration.

Q: How much does the Agile Throughput Charts app cost?

The app is free for teams with up to 10 users. For larger teams, pricing scales based on the number of users. A 30-day free trial is available to explore all features.

Understand, configure, and scale your delivery analytics in Jirawith the Throughput chart

Understand your true delivery capacity by tracking completed work over time
Visualize trends with throughput run chart and patterns with throughput histogram powered by advanced statistics
Set targets and RAG thresholds to highlight delivery risks instantly
Drill down to issue details and investigate results directly in Jira
Break down results by any Jira field to compare teams, workflows, or issue types

TRY IT FREE

Start quickly with ready-to-use templates and configure the metric in minutes
Define what “done” means for your workflow to ensure accurate measurement
Highlight SLA targets and health indicators to monitor delivery status at a glance
Share insights or export reports directly from a single Jira gadget

iNTERACTIVE EXAMPLES

Unlock multiple chart families in one subscription - ideal when you need more than one reporting perspective
Keep all your existing dashboards and saved charts - no migration or reconfiguration required
Combine Throughput, Velocity, Cycle Time, Burnup, and Monte Carlo forecasting, Cumulative Flow, WIP, and more in a single reporting suite
Create consistent Jira analytics across multiple teams, initiatives, or your entire portfolio.

TRY IT FREE

Key features of Agile Throughput Charts in Jira

Analyze throughput directly in Jira using data from one or multiple Boards or Teams, Projects, Epics, Releases, Initiatives (issue hierarchy), or JQL filters.

Choose how much historical data to analyze and how to group it. Use recent, current, custom, or date-based ranges, and group throughput by day, week, sprint, or month to fit your reporting needs.

Control how throughput is counted by selecting estimation fields, setting default estimates for missing values, and defining which statuses, transitions, or resolutions count as completed work.

Track how much work your team completes in each period to uncover delivery trends, throughput stability, and where team capacity is spent.

Segment completed work by issue type, team, priority, or any custom field to see how your capacity is distributed. Stacked bar charts make it easy to spot trends, such as an increasing share of bug work, rising operational load, or uneven contribution across teams.

Understand delivery predictability by visualizing the distribution of throughput values, revealing typical output ranges, variability, and the reliability of historical performance for planning.

Monitor key delivery signals with summary tiles displayed above the chart, helping teams quickly assess throughput performance:

Active / last interval throughput work completed in the most recent period
Throughput (%) - typical delivery level based on statistical measures
Throughput variance - how stable and predictable delivery is over time
Low throughput intervals - periods where throughput drops below expected levels
Custom health metrics - define custom throughput ranges using percentiles or absolute values

Use visual markers to interpret throughput performance on different charts.

Throughput Histogram chart → Highlights
- Mark important throughput ranges, such as low or typical delivery
- Define ranges using percentiles or absolute values
- Display selected ranges as health metrics above the chart
Throughput Run chart → Targets
- Add horizontal target lines to represent delivery goals or SLAs
- Compare actual throughput against defined limits
- Customize target name, color, and value

Break down throughput by team, assignee, issue type, release, JQL, etc., and other fields to understand what drives delivery results. Drill down to the issue list to verify the exact work items behind the metrics.

Refine your throughput analysis by selecting exactly which issues to include in calculations.

Filter by issue type – include stories, bugs, tasks, or any custom types
Focus on specific epics – analyze delivery within selected initiatives
Include or exclude issues – remove outliers, test work, or irrelevant tickets
Filter by releases – track throughput for specific versions or delivery scopes
Use custom JQL filters – apply advanced queries for maximum flexibility (including extended JQL)
Support multi-level filtering – combine conditions to match real workflows

Frequently Asked Questions

1. What is a Throughput chart in Agile?

A Throughput Chart is a visual Agile tool that shows how much work a team completes over time. It tracks the number of issues finished in each period (such as days, weeks, or sprints), helping teams understand delivery pace and identify trends in their output.

By analyzing throughput, teams can see whether delivery is increasing, stable, or declining, evaluate workflow predictability, and make more realistic planning decisions.

You can explore this approach in practice using the Agile Throughput Chart for Jira, which visualizes throughput trends, distribution, and delivery metrics directly from your Jira data.

2. What is an example of throughput in Agile?

An example of throughput in Agile is the total amount of work a team completes during a specific time period.

For example, if a team finishes 10 work items during a two-week sprint, the throughput for that sprint is 10 completed work items. In another sprint, the numbers may be different, which helps teams observe trends in delivery and understand how consistently work is completed.

By tracking throughput across multiple periods, teams can identify delivery patterns, assess variability, and make more realistic planning decisions.

You can visualize these trends using the Agile Throughput Chart for Jira, which calculates throughput based on work items that transition to a Done status and aggregates the selected estimation field over time.

3. What questions does a Throughput chart answer?

A throughput chart helps Agile teams understand how consistently work is completed over time and how predictable their delivery is.

It can help answer questions such as:

How much work does the team typically complete in each period (day, week, or sprint)?
Is delivery stable or highly variable from one period to another?
What throughput levels occur most frequently?
How predictable is our delivery based on historical performance?
Where is team capacity actually spent across work types or teams?

Using the Agile Throughput Charts, teams can analyze throughput trends, identify variability in delivery, and make more reliable planning and forecasting decisions.

4. How do you calculate throughput in Agile?

Traditionally, Throughput in Agile is calculated using the number of completed work items that transition to Done within a defined time bucket, like a day, week, or sprint. Some teams use story points or other estimation measures and track items completed in specific statuses like Dev Done or Released.

Tools such as the Agile Throughput Chart aggregate completed work directly from Jira workflows and allow you to choose the estimation field and completion statuses that match your process.

5. What is the difference between throughput and velocity?

Throughput and velocity are both Agile metrics used to measure delivery, but they represent different things.

Throughput measures the amount of completed work items within a given time period.Velocity measures the amount of estimated work completed, usually in story points.

While velocity depends on estimation accuracy, throughput focuses on actual completed work, which often makes it easier to analyze delivery trends and workflow stability.

6. What is a good throughput for an Agile team?

There is no universal “good” throughput value for Agile teams. The most important factor is consistency over time.

A stable throughput helps teams understand their delivery capacity, identify trends in completed work, and plan future work more reliably.

By analyzing historical data with tools like the Agile Throughput Chart, teams can track delivery patterns and improve planning decisions.

7. How is throughput used for forecasting?

Historical throughput data can help teams estimate how much work they are likely to complete in the future.

By analyzing completed work across multiple time periods, teams can identify typical delivery ranges and variability. This data can then be used for probabilistic forecasting methods, such as Monte Carlo simulations.

The Agile Throughput Chart helps teams analyze historical throughput and identify patterns that support more realistic planning and forecasting.

8. Can I visualize cross-team throughput in one chart?

Yes. Agile Throughput Charts support cross-team analysis by aggregating data from multiple sources, including boards (Scrum/Kanban), project scopes (projects or releases), issue hierarchies, epics, and custom JQL filters.

This allows you to view throughput across multiple teams, projects, or workflows in a single chart, helping you compare delivery pace, identify bottlenecks, and understand how work is completed across the organization.

9. How to add Agile Throughput Charts to a Jira dashboard?

To add a throughput chart to a Jira dashboard, install the Agile Throughput Charts app using this link and start with a free 30-day trial. After installation, open your Jira dashboard, go to the gadget library, and add the Agile Throughput Charts by Broken Build gadget.

The throughput chart will appear on your dashboard instantly, allowing you to track completed work, monitor delivery trends, and analyze your team’s throughput directly in Jira.

10. How much does the Agile Throughput Charts app cost?

The Agile Throughput Charts app is free for teams with up to 10 users. For larger teams, pricing scales based on the number of users can be calculated here. A 30-day free trial is also available, allowing you to explore all chart features and throughput analytics before purchasing.

Agile Throughput Charts

Turn delivery throughput data into actionable insights

Understand, configure, and scale your delivery analytics in Jirawith the Throughput chart

Throughput analytics & real-time insights

Flexible setup that works for any team and workflow

Go beyond throughput with a complete Agile reporting suite

Start tracking throughput and delivery trends directly in Jira

Key features of Agile Throughput Charts in Jira

Frequently Asked Questions

Related interactive Examples

Throughput Run chart

Why trust Broken Build apps?