Advanced Velocity Reports
on Your Jira Dashboard

Our velocity chart for Jira and Confluence allows you to:

Closely monitor individual, team, and cross-team progress
Analyze enriched velocity data, including the Say:Do ratio, and work added, removed, and completed
Slice and dice velocity charts: filter by epics, releases, or custom JQL
Analyze the entire sprint history through detailed, one-click sprint reports

Try it free

Schedule a demo

The Ultimate Velocity Chart in Agile to help you:

Build individual velocity charts. Group by a person to view their sprint-by-sprint progress or by sprints to compare various team members’ sprint performance
Support your Scaled Agile process in Jira by aggregating velocity data across multiple teams and Scrum boards

Move beyond the basic velocity metrics. Analyze the Say:Do ratio along with added, removed, and completed tasks
Break free from the limitations of a default velocity chart: with no need to stick to a Scrum Board, create multiple velocity charts on a Jira Dashboard

Filter velocity by epics, releases, bugs, stories, or custom JQL
Analyze the entire sprint history with detailed, single-click sprint reports
Apply advanced settings to suit your Jira configuration

Features of the Advanced Velocity Chart in Jira

Instantly access a detailed sprint report to analyze scope changes issue by issue — without the need to leave a Jira Dashboard.

Build a velocity chart using:

any Jira numeric field (e.g., “Feature Points” or “Epic Points” custom field)
“Story Points” and “Story Point Estimate” fields, used in company-managed and team-managed Jira projects, respectively. Combine both types of Jira projects on cross-team velocity charts
an integrated approach that accounts for both “Time Spent” and “Remaining Time” fields for precise chart calculations

Analyze data trends using velocity data for sprints grouped by months or quarters.

Apply User Preferences to view or hide data on your velocity chart without affecting other users’ views. Edit rights for a Jira dashboard are not necessary.

Analyzing relative metrics you can:

check the Say:Do ratio
adopt a unified approach to compare performance of multiple teams
track the continuous progress of teams over time

Use target lines to set goals or thresholds.

View active and future sprints on the same velocity chart, unlike the built-in Jira chart.

Different teams may have different Definitions of Done - this is crucial when building cross-team velocity charts.
‍
Select which status counts as Done for each separate team, or stick to the default approach where statuses from the last board column are considered Done.

Often, teams don’t estimate minor issues, like small bugs discovered during an active sprint. To include these in Jira, utilize a default estimate.

Exclude specific sprints from a velocity chart. This is useful when:

Teams sharing a Scrum Board have different sprint names like “Team A - Sprint 1”, “Team B - Sprint 1”
You wish to exclude certain sprints from the chart