Jira Cloud app · Velocity tracking
Jira Velocity Chart: see average velocity, commitment and completed points in one view
Stop digging through the Reports tab. PM Overview shows sprint velocity, the gap between commitment and completed work, and the trend over past sprints, right next to your sprint progress in Jira.
- ★ 5.0 on the Atlassian Marketplace (17 reviews)
- Free for teams up to 10 users
- 30-day free trial for any team size
- Scrum and Kanban boards
- Opens inside Jira Cloud, no setup
In short: PM Overview adds a configurable velocity chart to Jira Cloud. It shows average velocity, total commitment and completed story points per sprint or custom timeframe, lets you exclude outlier sprints, and keeps the full history of previous sprints. Use it to plan sprints on real capacity instead of hope.
Why Jira’s built-in velocity report isn’t enough
- It lives on a separate screen. The Velocity Report sits under the board’s Reports tab and can’t be added to a Jira dashboard as a gadget.
- No average to plan with. You have to eyeball bars and work out the average yourself before every planning session.
- Outliers distort the picture. A holiday sprint or an incident week drags the numbers down, and you can’t leave it out.
- No early warning. You only find out velocity dropped when the sprint is already over.
What the PM Overview velocity chart gives you
Average velocity, calculated for you
The chart title shows your average velocity over the selected sprints, ready for capacity planning.
Commitment vs completed
See planned and delivered story points side by side for every sprint, and how reliably the team hits its commitments.
Exclude outlier sprints
Filter sprints in or out, so one unusual sprint doesn’t skew your forecast.
Custom timeframes
Switch the data source between sprint, backlog or both, and pick a custom timeframe for quarterly reviews.
Full sprint history
Every previous sprint stays available, so retrospectives can compare trends instead of guessing.
Alerts when velocity dips
The notification panel tells you when this sprint’s velocity is lower than the average, while you can still act.
How to use velocity for better sprint planning
- Plan on the average, not the best sprint. Use the average of the last 3–6 normal sprints as your planning ceiling.
- Watch the commitment gap. If completed is consistently below commitment, commit less, or find out what is being added mid-sprint.
- Leave outliers out. Exclude holiday or incident sprints from the average.
- Never compare teams on velocity. Story points are team-specific. Use velocity to plan, not to rank people or teams.
Up and running in 2 minutes
- Install PM Overview from the Atlassian Marketplace. It is free for up to 10 users, and every team size gets a 30-day trial.
- Open your Jira project and click PM Overview in the project navigation (or under More).
- Pick a board and sprint. The dashboard fills itself from your existing Jira data. No gadgets, JQL or spreadsheets to set up.
What teams say on the Atlassian Marketplace
Great to use so far. I was looking for a time tracking and resource allocation dashboard.
Charles Smith, Marketplace review, Sep 2025
We were looking for this kind of plugin, one view to manage our project. Also helps with reporting and retrospectives.
Marketplace review, Aug 2024
This dashboard is exactly what we were looking for!
Sarah, Marketplace review, Jul 2024
Frequently asked questions
Can I add a velocity chart to a Jira dashboard?
Not with native Jira Cloud gadgets. The built-in Velocity Report sits under the board’s Reports tab, separate from dashboards. PM Overview shows velocity next to sprint progress, notifications and KPIs in one view inside Jira.
How is average velocity calculated in PM Overview?
Average velocity is the mean of completed story points across the sprints (or timeframe) you include. You can exclude unusual sprints, such as a holiday sprint, so the average reflects normal capacity.
What is the difference between commitment and completed?
Commitment is the story points planned into a sprint at the start. Completed is the story points done by the end. A gap between the two, sprint after sprint, is a sign of overcommitment or scope added mid-sprint.
Does the velocity chart work for Kanban boards?
Velocity is a Scrum concept, so the chart is most useful on Scrum boards. On Kanban boards you can use custom timeframes and the task completion time charts instead.
Is PM Overview free?
PM Overview is free for Jira Cloud sites with up to 10 users. Larger teams get a 30-day free trial and then pay per user through Atlassian.
Plan your next sprint on real velocity
Install PM Overview in Jira Cloud and see your average velocity, commitment and completed points in under two minutes. Free for up to 10 users.
