Forums

Articles
Create
cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

πŸ“’ Coming soon: Agile Throughput Charts – measure what your team actually delivers in each period πŸš€

Hey Atlassian Community!

What if you could finally answer questions like: β€œAre we keeping up with demand?” and β€œIs our delivery stable?”

Not with guesswork. Not with wishful thinking. But with data that shows you exactly what's leaving your system, how predictable your delivery is, and whether your throughput is stable enough to trust.

At Broken Build, we're on a mission to give Agile teams the metrics that matter. We recently launched Agile Cumulative Flow Charts to help you visualize work in progress and identify flow bottlenecks.

Now, we're preparing to launch Agile Throughput Charts - your new tool for assessing delivery pace, assessing predictability, and balancing with demand.

What makes Throughput Charts essential?

A Throughput chart is your delivery heartbeat monitor. It transforms raw completion data into clear visuals that show:

  • Whether you're keeping up with incoming work

  • How stable (or volatile) your throughput is to build credible forecasts

  • If delivery keeps up with arrivals (work added), using throughput as the departure side of the equation

The Throughput run chart reveals what's successfully leaving the system - sprint after sprint, week after week.

Powerful features of Agile Throughput Charts by Broken Build

1. πŸ”€ Flexible chart modes

πŸ”Ά Line and Bar charts – track completion trends
Both modes show how much work the team completed in each period. High points indicate productive periods; low points highlight bottlenecks or downtime.

Flexible chart modes.png

  • Line charts are perfect for spotting trends over time - whether your throughput is climbing, declining, or holding steady. Ideal for executive dashboards and quarterly reviews.

  • Bar charts give you clear, period-by-period comparisons. Quickly identify which sprints or weeks were high performers and which ones lagged. Great for retrospectives and sprint planning.

2. βš™οΈ Smart calculation rules – count what matters

πŸ”Ά Estimation Options: story points (default), issue count, custom numeric fields

πŸ”Ά Throughput rules:

  • Define which statuses count as "done" (supports per-board customization for multi-team setups)

  • Set default estimates for items without story points

  • Filter by resolution (include/exclude Won't Do, Duplicate, etc.)

  • Automatically exclude the active interval (current day/week/sprint) from statistics to prevent skewed averages

Smart calculation rules.png

πŸ”Ά Grouping flexibility:
Choose daily, weekly, or by-sprint grouping to match your team's cadence. Scrum teams benefit from daily granularity across 3-6 sprints; Kanban teams prefer weekly grouping over 8-12 weeks to smooth out noise.

Grouping flexibility.png

3. πŸ“Š Statistical intelligence – see beyond simple averages

The Throughput graph isn't just about showing bars or lines - it's about understanding what those numbers mean for your planning and forecasting.

Statistical intelligence.jpeg

βœ… What you'll get:

  • Mean throughput – Your average delivery rate across the selected period

  • Percentile lines (P50, P85, P95) – Probability-based benchmarks that show what you can deliver most of the time (P50/median) versus high-confidence scenarios (P85/P95)

  • Custom target lines – Set capacity goals and compare actual throughput against your commitments

πŸ’‘ Why this matters:
Percentiles help you move beyond averages that can be misleading. If your mean is 25 story points but your P50 is only 18, you're routinely over-committing. The Throughput report in Jira gives you the confidence intervals you need to set realistic expectations with stakeholders.

...and more features designed to make Throughput analysis accessible, actionable, and integrated directly into your Jira environment.

πŸ’‘Why teams need Throughput insights

Whether you're planning the next sprint or setting quarterly capacity targets, a reliable Throughput chart helps you:

βœ… Set realistic commitments based on historical data, not gut feeling
βœ… Spot delivery slowdowns early and investigate root causes (blocked work, WIP violations, team changes)
βœ… Balance throughput against demand to prevent backlog bloat
βœ… Quantify predictability so stakeholders understand confidence ranges

πŸš€ Stay tuned for the launch!

We're putting the final touches on the Agile Throughput Charts app and will be releasing it very soon.

Be first to know:

πŸ’Œ Join the waiting list:

🧭 Explore more:

πŸ“£ Stay tuned for the detailed release post!

πŸ“¦ Explore our Agile reports suite

While you're waiting for the Agile Throughput Charts app launch, check out our other powerful apps designed to elevate your Agile workflows:

Individual Apps:

Complete Solution:

  • Agile Reports & Gadgets (Bundle) - Access the combined capabilities of our four individual apps in a single comprehensive package, including Velocity Charts, Cycle Time Charts, and Burnup Burndown Charts.

Each app is built with the same philosophy: turn raw Jira data into insights you can trust and act on.

Ready to measure delivery with clarity and confidence? Discover new Agile insights with Broken Build πŸš€

Looking forward to sharing Agile Throughput Charts with you soon!

Cheers,
The Broken Build Team

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events