Tracking sprint velocity across your Agile teams shouldn't feel like solving a puzzle. Yet, many teams struggle with incomplete data, limited customization, and charts that do not accurately reflect their actual workflow. Without clear velocity metrics, capacity planning becomes a matter of guesswork, and team performance remains a mystery.
The Team velocity chart, part of the Agile Velocity Charts app by Broken Build, solves this by delivering comprehensive sprint velocity tracking with the flexibility your team needs.
π Explore the interactive Team velocity chart π example to see how it transforms sprint velocity tracking into actionable insights.
Let's examine why Jira's built-in option often falls short.
Jira offers the Velocity Chart report as part of its native Scrum board reporting suite. While functional for basic needs, it comes with significant constraints that hinder deeper analysis.
Here's what teams typically encounter:
π Single board limitation β You can only view velocity for one Scrum board at a time, making cross-team analysis nearly impossible
π No scope visibility β The native chart doesn't surface scope changes, estimation deltas, or work added mid-sprint
βοΈ Fixed estimation field β Stuck with the board's configured estimation statistic, with no flexibility to switch metrics
π Basic averaging only β Simple average velocity line without median options, moving averages, or custom target tracking
π― No drill-down capability β You can't click intervals to see which specific issues contributed to metrics
These limitations leave teams wanting more sophisticated tools that adapt to real-world complexity. That's where a more powerful solution comes into play.
The Team velocity chart, part of the Agile Velocity Charts app by Broken Build, transforms velocity tracking from a basic report into a strategic planning tool. Built for teams that need flexibility without complexity, it fills every gap left by Jira's native chart.
What makes it different?
Track velocity across multiple boards simultaneously, visualize scope and estimation changes, compare initial versus final commitments, and drill into the exact issues behind every metric - all from a single configurable dashboard gadget.
Now let's explore the specific capabilities that make this possible.
The Team velocity chart packs powerful functionality into an intuitive interface. Here's what sets it apart and how each feature solves real team challenges.
Monitor delivery trends through a rich set of velocity metrics that show not just what got done, but how scope and commitments evolved throughout each interval. The metrics dropdown lets you display or hide individual metrics and add average lines for each one, keeping your chart focused on what matters most.
Available metrics include:
Rollover β Work carried between intervals
Initial commitment β Scope at interval start
Final commitment β Scope after all changes
Total scope change β Net scope delta during the interval
Added work β Work items introduced after the interval start
Removed work β Work items deferred or removed
Estimation change β Re-estimation impact within the interval
Not completed work β Unfinished work items needing replanning
Completed work (initial) β Delivered from original commitment
Completed work β Total completed regardless of timing
You can toggle visibility for any metric, add average lines (mean, median, or moving average), reorder metrics by dragging, and customize colors for emphasis.
π― Why this helps:
Complete transparency β See exactly how commitments, scope, and delivery relate throughout each interval
Flexible focus β Show only the metrics relevant to your current analysis without visual clutter
Trend identification β Average lines reveal patterns hidden in sprint-to-sprint volatility
Solves the "what changed" problem β Stop wondering why velocity fluctuates - see scope and estimation changes directly
Switch instantly between Bar, Line, and Stacked Bar visualizations to find the view that best answers your current question. Each chart type reveals different aspects of your velocity data.
Bar charts highlight interval-by-interval metric values, making precise comparisons straightforward.
Line charts emphasize trends over time, helping you spot gradual improvements or declines.
Stacked bar charts show how multiple metrics compose each interval's total, revealing the work breakdown at a glance.
π― Why this helps:
Adaptable analysis β Match visualization to your question (trends? comparisons? composition?)
Stakeholder communication β Choose the format that resonates with your audience
Pattern recognition β Different chart types surface different insights from identical data
Eliminates export hassle β No need to dump data into other tools for different views
Display each metric as a percentage of the interval commitment instead of raw estimation values. This makes cross-interval and cross-team comparisons meaningful even when absolute capacity varies.
Calculate percentages based on the Initial Commitment (original plan) or the Final Commitment (plan after scope changes). Comparing results to the Initial Commitment highlights planning accuracy, while the Final Commitment reflects delivery against the adjusted scope. Average lines automatically convert to percentages as well, showing smoothed percentage trends.
π― Why this helps:
Fair comparisons β Compare velocity across teams with different capacities or estimation scales
Planning accuracy insight β See what percentage of commitments actually get delivered
Normalized forecasting β Use historical percent-complete data for capacity planning
Solves the apples-to-oranges problem β Stop struggling to compare teams with vastly different story point scales
Click any interval on the chart to open detailed tables showing exactly which issues contributed to each metric. The breakdown panel displays how metric values distribute across boards, issue types, assignees, or any custom field you choose. The issue list shows every contributing work item with direct links to Jira.
Click a specific metric in the breakdown, and the issue list automatically filters to show only issues that contributed to that metric in the selected interval.
π― Why this helps:
Root cause analysis β Trace unexpected velocity changes back to specific work items or work types
Retrospective fuel β Walk into retros with concrete examples of what impacted velocity
Bottleneck identification β See which teams, issue types, or assignees drive metrics
Eliminates guesswork β Stop asking "why did velocity drop?" - click and see the exact issues
Select the Project Velocity monthly template in the Agile Velocity Charts app by Broken Build to instantly visualize project performance over your chosen interval. Track exactly how much your team delivers month over month, identifying productivity peaks and periods where progress slowed.
This historical insight supports future sprint planning, resource allocation, and realistic goal setting by showing actual delivery patterns at the project level.
π― Why this helps:
Macro-level planning β See project velocity trends beyond individual sprints
Resource planning β Identify seasonal patterns or capacity changes over time
Goal calibration β Set realistic targets based on actual monthly throughput
Solves the zoom-out problem β Get the big picture view without losing sprint-level detail
The bottom line: These features work together to give you complete control over velocity tracking -from granular issue-level investigation to strategic cross-team forecasting. You get the insights you need, formatted exactly how you need them.
The best way to understand the Team velocity chart's capabilities is to experience them firsthand. The interactive example lets you experiment with different configurations, metric selections, and visualization options in real time.
π Test drive the chart's features and see how it adapts to different team scenarios with the Team velocity chart example π
Toggle between chart types, enable percentage view, select which metrics to display, and click intervals to explore the breakdown tables. You'll immediately see how the chart surfaces insights that would take hours to compile manually.
Getting the most from your Team velocity chart means knowing a few insider techniques that go beyond basic setup.
π‘ Use moving averages to smooth out sprint volatility β Individual sprint velocity can swing wildly due to holidays, incidents, or one-off events. Apply a moving average (2-5 sprints) to see the underlying trend and make more reliable capacity forecasts.
π Track commitment accuracy as a leading indicator β Monitor the gap between initial commitment and completed work consistently. Teams that regularly complete 90-100% of committed work demonstrate strong estimation and planning discipline. Persistent over- or under-commitment signals process issues worth addressing.
π Compare scope change patterns across teams β Use the cross-team velocity chart view to see which teams experience frequent added work or estimation changes. Teams with stable scope typically deliver more predictably - unstable scope may indicate unclear requirements or poor backlog refinement.
π― Create custom target lines for delivery milestones β Add target lines representing your required velocity to hit delivery dates. When the chart shows actual velocity trending below the target, you can proactively adjust scope, timeline, or resources before the gap becomes critical.
β‘ Use the exclude from rollover feature strategically β Filter out issues in specific statuses (like "Blocked" or "Waiting for Input") from rollover calculations to get a clearer picture of work genuinely carried forward versus work that was paused for external reasons.
Team velocity chart is part of the Agile Velocity Charts app, available as a separate gadget or inside the Agile Reports & Gadgets bundle. Setup takes just a few minutes, and you'll have enterprise-grade velocity tracking running immediately.
The configuration process is straightforward - Jira users of any skill level can add and customize the chart without technical expertise.
Setup steps:
1οΈβ£ Navigate to your Jira dashboard β Go to the dashboard where you want the velocity chart to appear
2οΈβ£ Click "Add gadget" β Find the gadget button in your dashboard controls
3οΈβ£ Search for "Agile Velocity Charts" β Locate the Team velocity chart gadget in the marketplace
4οΈβ£ Click "Add" and configure your preferences β Select your boards or projects, choose your estimation field (Story Points, Issue Count, time estimates, or custom fields), set your desired interval and grouping, and customize display options, including which metrics to show and chart type
You're all set! Your Team velocity chart is now live and ready to deliver sprint insights. Adjust filters, metrics, and visualization options anytime as your tracking needs evolve.
Stop settling for incomplete velocity data and limited reporting flexibility. The Team velocity chart transforms sprint velocity from a basic metric into a strategic advantage that drives better planning, more accurate forecasting, and improved team performance.
β Here's what you gain:
Comprehensive metrics β Track commitments, scope changes, rollovers, and completion in one unified view
Multi-board aggregation β Monitor velocity across teams, projects, and boards simultaneously for portfolio-level insights
Flexible visualization β Switch between chart types and percentage views to match your analysis needs
Issue-level transparency β Drill into any interval to see exactly which work items contributed to each metric
Advanced forecasting β Use average lines, target lines, and historical patterns for realistic capacity planning
π See the chart in action through this interactive demonstration: Team velocity report example π
To start using the Team velocity chart, install either the Agile Velocity Charts app as a standalone gadget or choose the Agile Reports & Gadgets bundle for comprehensive sprint analytics. Get started with a 30-day free trial that requires no credit card, and teams of up to 10 users can use it completely free.
π Ready to transform your velocity tracking? Try the Team velocity chart today and experience sprint reporting that finally keeps pace with how your teams actually work.
β¨Your journey to better sprint insights starts now - and your team's improved predictability and performance will prove it was worth it!
Vasyl Krokha _Broken Build_
0 comments