Velocity & Throughput Charts is a Jira dashboard app that helps Scrum, Kanban, SAFe®, ITSM, and other teams measure how much work they complete and understand how their delivery pace changes over time.
Track sprint velocity and scope changes, compare committed and completed work, monitor throughput across configurable time intervals, and use rolling averages to identify delivery trends and variations. These insights help teams plan more realistically, avoid overcommitment, evaluate delivery consistency, and forecast future capacity.
The app helps you answer questions such as:
-
How much work does the team typically complete during a sprint or time interval?
-
Is the team’s delivery pace increasing, decreasing, or remaining stable?
-
How much does the sprint scope change after the sprint starts?
-
How much of the initial or final sprint scope is completed?
-
Is the team consistently delivering what it commits to?
-
Which sprints or periods show unusually high or low delivery?
-
How much work can the team realistically plan for future sprints or periods?
Key features
Two complementary delivery perspectives
Use the Team Velocity Chart to analyze completed work, scope, and average velocity across Scrum sprints. Use the Kanban Velocity / Throughput Chart to measure completed work across configurable time intervals for Kanban, continuous-flow, or non-sprint-based teams.
Flexible data sources
Create the Team Velocity Chart using the Scrum board of your team.
For the Kanban Velocity / Throughput Chart, you can use:
-
A Jira agile board
-
A saved filter
-
A JQL query
This allows you to measure throughput for a team, project, service, product, or another custom scope.
Flexible calculation options
Calculate velocity or throughput using:
-
Work Item Count
-
Story Points
-
Original Time Estimate
-
Time Remaining and Time Spent
-
Other numerical custom fields available in Jira
This allows teams to measure delivery using the unit that best matches their estimation and reporting practices.
Sprint scope and completion analysis
Compare the initial sprint scope, final sprint scope, and completed work to understand whether the team is meeting its commitments.
You can also track:
-
Work added after the sprint started
-
Work removed during the sprint
-
Net and absolute scope change
-
Percentage of scope added or removed
-
Percentage of the initial or final scope completed
Configurable averages and reporting history
Choose how many previous sprints or time intervals appear in the chart and how many are included in the average calculation.
The rolling average provides context for short-term changes and makes it easier to distinguish a lasting delivery trend from a temporary variation.
Configurable throughput intervals
Measure throughput using time intervals that match your team’s reporting cadence. Configure the duration and alignment of the intervals, analyze the most recent periods, or display historical periods beginning from a specific date.
You can also include the current incomplete interval when a real-time view is needed.
Custom definition of completed work
Define what “Done” means based on your workflow. Completed work can be defined using:
-
The last column of a selected Jira board
-
Jira’s Done status category
-
One or more selected workflow statuses
-
Work items that reached specified statuses at least once
Configurable subtask handling
Include subtasks and their estimates in the calculations when they represent meaningful work for your team. The Team Velocity Chart can also be configured to exclude subtasks or process only subtasks.
Detailed supporting data
Display a data table alongside the chart to inspect the sprints, intervals, and work items behind the calculated values.
Team Velocity data can also be exported to CSV for further analysis or reporting.
Backlog forecasting
When the Kanban Velocity / Throughput Chart uses a board as its data source, it can estimate completion dates for ranked backlog items based on the team’s current average throughput.
Customizable chart display
Customize chart series, colors, labels, legends, gridlines, and other display options so that the charts match the needs of your team and dashboard audience.
Metrics and delivery signals you can track
|
Metric or signal |
Gadget |
|---|---|
|
Sprint velocity |
Team Velocity |
|
Average sprint velocity |
Team Velocity |
|
Initial sprint scope |
Team Velocity |
|
Final sprint scope |
Team Velocity |
|
Completed work per sprint |
Team Velocity |
|
Committed versus completed work |
Team Velocity |
|
Scope added |
Team Velocity |
|
Scope removed |
Team Velocity |
|
Net scope change |
Team Velocity |
|
Absolute scope change |
Team Velocity |
|
Percentage of scope change |
Team Velocity |
|
Percentage of scope added |
Team Velocity |
|
Percentage of scope removed |
Team Velocity |
|
Sprint completion percentage |
Team Velocity |
|
Sprint-to-sprint variation |
Team Velocity |
|
Throughput |
Kanban Velocity / Throughput |
|
Completed work per time interval |
Kanban Velocity / Throughput |
|
Rolling average throughput |
Kanban Velocity / Throughput |
|
Throughput trend |
Kanban Velocity / Throughput |
|
Period-to-period variation |
Kanban Velocity / Throughput |
|
Backlog completion forecast |
Kanban Velocity / Throughput |
|
Estimated backlog completion dates |
Kanban Velocity / Throughput |
|
Delivery consistency |
Both gadgets |
|
Delivery trend |
Both gadgets |
|
Potential overcommitment |
Team Velocity |
|
Historical delivery capacity |
Both gadgets |
|
Delivery predictability |
Both gadgets |