Jira Velocity Charts: A Step-by-Step Guide for Agile Teams
Need more reliable sprint forecasts? Learn to use the velocity chart Jira provides to plan realistically with this step-by-step guide. Read now.
A sprint can finish with every ticket marked done, yet your next release estimate still feels like a guess. That uncertainty makes planning harder, especially when stakeholders expect a reliable delivery date.
A Jira velocity chart can help, but only if you know what its bars measure and where their limits are. Inconsistent estimates, changing sprint scope, and unfinished work can make the chart look more reassuring—or more alarming—than it should.
Here’s a practical way to find the chart, read it, and use it for planning without treating past performance as a promise. I’ll also show you how to spot common interpretation problems and build a more consistent sprint routine.
How to Use a Jira Velocity Chart
A velocity chart compares the estimated work a team commits to in each sprint with the work it completes. Use the steps below to find the report, check its inputs, and interpret the trend.
Open the right board. In Jira, select the Scrum board connected to the team and project you want to review. Board configuration matters because it determines which issues and workflow statuses the report includes.
Open the Velocity Chart report. From the board, go to Reports and choose Velocity Chart. Jira’s menus can vary slightly by version and configuration, so look under the board’s reporting area if the label has moved.
Choose the sprint range. Select the sprints you want the report to display. Include enough completed sprints to see a useful pattern, while avoiding comparisons across major changes in team composition or estimation practice.
Check the estimation method. Confirm whether the team estimates work using story points or another configured measure. Compare sprints only when the team has applied the same estimation approach consistently.
Compare commitment with completion. The chart typically shows the work planned at the start of a sprint and the work completed by its end. Review both bars for each sprint, then look for a pattern across several sprints.
Discuss what changed. Ask whether the team added work after sprint planning, carried unfinished issues forward, or changed how it estimates. Use those details to explain differences rather than assigning blame.
Apply the trend cautiously. Use recent completed work to inform a future forecast, then account for known changes such as holidays, staffing, or unusual project demands. Treat the chart as a planning aid, not a delivery guarantee.
For example, imagine a team commits to 42 story points and completes 34. The gap is a prompt to investigate scope changes, blockers, or estimation—not proof that the team performed poorly.

What the Chart Measures—and What It Doesn’t
The chart’s central comparison is planned work versus completed work across sprints. A steady completion pattern can help a team estimate how much work it may reasonably take on next, assuming its working conditions remain similar.
But here’s the truth: velocity is a team planning measure, not a score for comparing people or teams. One group’s 35 points may represent a very different amount of effort from another group’s 35 points.
The chart also doesn’t explain why a sprint changed. If a team completes less than it planned, the bars show the difference, but the team still needs to examine scope changes, dependencies, work size, and interruptions.
Think of the report as a dashboard indicator. It can tell you that the pattern shifted; a sprint review or team discussion helps explain what caused the shift.
How to Read Sprint Patterns
Start by looking across several sprints rather than judging one result. A single sprint may be affected by an urgent defect, staff absence, or a large issue that proved harder than expected.
If completed work stays close to the committed amount, the team may be planning at a relatively consistent level. If the gap varies widely, check whether sprint scope or estimation practices have changed.
Here’s why: the shape of the trend matters more than a single high or low bar. For instance, a team that completes 28, 30, and 29 points has a steadier planning signal than one that completes 15, 42, and 24 points.
Use that pattern to start a conversation, then connect it to real events. If the team completed less during a sprint with a major dependency delay, account for similar risks in future planning.
Why Planned and Completed Work Can Differ
A gap between the bars often begins with a change in the sprint. A team may add an urgent request after planning, discover hidden work, or lose time to an external dependency.
Issue status configuration can also affect what Jira counts as complete. If a team’s definition of done doesn’t align with the board’s completed statuses, the report may not reflect how the team understands its finished work.
Let me explain with a simple example: a team moves a feature to a testing status before the sprint ends, but its board only counts a later status as complete. The team may view the feature as nearly finished, while the report excludes it from completed work.
Review board configuration and sprint scope alongside the chart. A short check after each sprint can catch mismatches before they distort several planning conversations.
Practical Habits for More Useful Velocity Trends
Keep estimates consistent. Agree on how the team uses story points and revisit the approach when estimates begin to vary for reasons unrelated to the work.
Protect the sprint plan where possible. When urgent work must enter mid-sprint, record the change so the team can interpret the chart fairly.
Use a stable definition of done. Make sure the board’s workflow reflects the team’s completion criteria, so reported work matches the team’s understanding.
Review causes, not just totals. Ask what helped or hindered delivery before adjusting the next sprint’s commitment.
Keep the forecast realistic. Consider upcoming leave, dependencies, and known operational work instead of copying the previous sprint’s number.
The best part? These habits don’t require a complicated process. A few consistent questions during sprint review can make the trend far more useful for planning.
Jira Velocity Chart Alternative: ONES.com
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project handles project management as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative; the products are sold separately.

If your team is reviewing sprint performance, the practical question is whether its project workflow and reporting setup help you understand planned work, completed work, and changes between sprints. ONES Project offers built-in reporting alongside agile planning capabilities, so teams can assess whether its reporting fits their needs.
Core Capabilities
Disconnected planning and reporting: ONES Project combines sprint management with built-in reporting, helping teams review work and progress in the same project environment.
Rigid workflows: Jira-compatible workflows and custom workflows let teams adapt issue progress to their own delivery process.
Fields that don’t fit the team: Custom fields can capture project-specific details, giving teams more relevant context as they plan and review work.
Manual repeat tasks: Automation can reduce repetitive workflow actions, leaving the team more time to review sprint outcomes and resolve blockers.
Agile planning needs: Sprint management supports planning and tracking work across iterations.
Too many add-ons: Native capabilities across workflows, fields, sprint management, automation, and reporting can reduce reliance on plugins for common project needs.
Deployment constraints: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment to fit their operating environment.
Concerns about self-hosted capability: ONES.com provides full feature parity between its cloud and self-hosted versions, so deployment choice does not require giving up feature access.
Application Scenarios
An agile product team moving from Jira: A team can assess Jira-compatible workflows, sprint management, and built-in reporting against its existing planning and review practices. It should verify that the reporting supports the specific velocity questions it needs to answer.
A team working in a restricted environment: An organization that cannot use a public cloud service can consider On-Premise, Private Cloud, or Air-gapped deployment while retaining feature parity with the cloud version.
ONES.com offers a free option for up to 30 seats. Consider the deployment requirements, workflow needs, and reporting expectations before deciding whether ONES Project fits your team.
Common Challenges When Interpreting Velocity
One Sprint Looks Like a Sudden Drop
Problem: A single low completion bar can trigger concern, even when the team faced an unusual blocker or urgent work.
Solution: Review several sprints and discuss what changed in the outlier. Adjust future planning for known conditions rather than reacting to one result alone.
Work Is Added After Sprint Planning
Problem: The original commitment no longer reflects the actual workload, making the difference between planned and completed work harder to interpret.
Solution: Make scope changes visible during the sprint. Discuss how urgent additions affected delivery during the retrospective or sprint review.
Teams Compare Their Point Totals
Problem: Story points are relative to a team’s own estimation practice, so comparing totals across teams can create misleading conclusions.
Solution: Use velocity to support a team’s own planning. For broader reporting, agree on measures that can be compared fairly across groups.
The Report Doesn’t Match the Team’s Definition of Done
Problem: Jira may not count an issue as complete if its status or board configuration differs from the team’s working agreement.
Solution: Review the board’s workflow and completed statuses with the team. Confirm that the report’s definition of completed work matches how the team closes sprint work.
FAQs About Jira Velocity Charts
Where can I find the Velocity Chart in Jira?
Open the Scrum board you want to review, then go to its Reports area and select Velocity Chart. Jira’s navigation can vary by version, permissions, or board configuration. If you can’t see the report, confirm that you’re viewing the right board and have access to its reports.
What do the two bars represent?
The chart compares work planned for a sprint with work completed by the sprint’s end. The exact labels and display can depend on the Jira configuration. Review the team’s estimation method and board settings so you understand what each bar includes before using the report for planning.
Should a team try to increase its velocity?
Use velocity to improve planning predictability, rather than as a target that teams must continually raise. Chasing a larger point total can encourage inflated estimates or pressure people to take on too much. A steadier understanding of how much work the team can complete is usually more useful for forecasting.
How many sprints should I review?
There isn’t one ideal number for every team. Review enough completed sprints to see whether a pattern is emerging, and consider whether the team’s membership, estimation approach, or work type changed during that period. A recent, relevant trend is generally more useful than a long history that mixes very different conditions.
Can I compare velocity across different teams?
Comparisons are usually misleading because teams may estimate work differently. A team’s story points are useful within that team’s own planning practice, but they don’t represent a universal unit of effort. Compare shared outcomes and delivery context instead, or agree on a common measure designed for cross-team reporting.
Conclusion
A Jira velocity chart compares planned and completed sprint work, giving your team a practical signal for future planning. Its value depends on consistent estimates, clear completion rules, and thoughtful discussion of scope changes.
When a sprint result surprises you, look for the cause before changing the next commitment. Use several sprints to understand the pattern, and account for known constraints when forecasting.
That approach turns the chart from a scorecard into a useful planning aid. If your team is considering another project platform, compare its workflow, sprint management, deployment options, and reporting against the way you actually work.