Velocity Charts Explained: What They Do and Don't Tell You

TLDR: Velocity charts reveal your team's sustainable throughput over time, but misusing them as performance targets or cross-team comparisons creates dysfunction.

Velocity is one of the most useful and most misused metrics in agile project management. When understood correctly, it helps teams plan sprints with confidence and stakeholders set realistic expectations. When misunderstood, it becomes a weapon that drives inflated estimates, burnout, and gaming behavior. The difference comes down to understanding what velocity actually measures and what questions it can and cannot answer.

What Velocity Measures

Velocity is the number of story points a team completes in a sprint. That is it. If your team completed stories worth a total of twenty-four points last sprint, your velocity was twenty-four.

Over multiple sprints, velocity reveals patterns. A team that consistently delivers between twenty and twenty-six points per sprint has a reliable velocity range. This range is enormously useful for planning because it tells you roughly how much work the team can commit to in the next sprint without overloading.

The key word is "team." Velocity belongs to the team, not to individuals. Tracking individual velocity is meaningless because stories are collaborative and point values reflect team effort, not individual speed.

It also helps to know that neither velocity nor story points appear in the official Scrum Guide. They are planning practices that teams adopt, and each team calibrates its own scale, which is why the numbers only mean something within the team that produced them.

What Velocity Tells You

How much work to pull into a sprint. If your average velocity over the last three sprints is twenty-two, pulling twenty-two points of work into the next sprint is a well-calibrated bet. Pulling thirty-five is optimistic. Pulling fifteen leaves capacity on the table.

Whether changes affect output. If you add a team member, change your process, or adopt a new tool, velocity over the following sprints shows whether the change helped, hurt, or made no difference. This is the legitimate use of velocity as a diagnostic tool.

Long-term delivery estimates. If an epic has sixty remaining story points and your team's velocity is twenty per sprint, the epic will take approximately three sprints to complete. This is not a guarantee, but it is a reasonable projection for stakeholder communication.

What Velocity Does Not Tell You

Team quality or effort. A velocity of thirty does not mean a team is working harder than a team with a velocity of twenty. Story points are relative within a team and meaningless across teams. Team A's five-point story might be equivalent to Team B's eight-point story because the teams calibrated differently.

Whether the team is improving. Increasing velocity is not necessarily a sign of improvement. Teams that feel pressure to raise velocity simply inflate their estimates. A team that estimated a story at three points last quarter now estimates similar stories at five. Velocity goes up, output stays the same, and the metric becomes useless.

Individual performance. Never use velocity to evaluate individuals. The moment team members believe their personal evaluation depends on velocity numbers, they will avoid helping teammates, avoid taking on risky stories, and inflate their estimates.

Reading a Velocity Chart Correctly

A healthy velocity chart shows a relatively stable line with minor fluctuations. Sprint-to-sprint variation of ten to twenty percent is normal. A sprint where someone was on vacation or a holiday shortened the working days explains a temporary dip. No action needed.

Watch for these patterns that do require attention.

Steady decline over multiple sprints. This could indicate growing technical debt, unclear requirements reaching sprints, or team morale issues. Investigate the cause rather than pressuring the team to produce more.

Wild swings between sprints. Large variations suggest inconsistent estimation, scope changes mid-sprint, or an unreliable definition of done. The team may be counting partially completed work in some sprints but not others.

Sudden sustained increase. If velocity jumps and stays high without any process change, the team is likely inflating estimates. Compare the number of stories completed per sprint alongside the point total. If story count stays flat while points rise, inflation is occurring.

Using Velocity Without Abusing It

The safest approach is to treat velocity as a private team metric used for planning, not a public metric used for evaluation. Share velocity with stakeholders only in the context of delivery forecasts, never as a performance indicator.

In your sprint planning sessions, use the Velocity chart in LocalPM's Reports view, which shows committed versus completed points for each completed sprint. After three or four sprints, you will have enough data to plan confidently. Use the average of the last three sprints as your guide, not the best sprint or the worst.

When someone asks you to increase velocity, reframe the conversation. "We can increase the work we commit to, but that increases the risk of not completing the sprint. Or we can look at reducing blockers and improving flow, which may naturally increase throughput." This redirects from output pressure to process improvement.

Velocity is a compass, not a speedometer. It tells you where you are headed, not how fast you should push. Use it wisely and it becomes one of the most valuable tools in your planning toolkit. Pair velocity with burndown charts for sprint-level diagnostics, and zoom out to compare velocity across quarters for longer-term trend analysis.

Frequently Asked Questions

How do you calculate velocity in agile?

Add up the story points of every story the team fully completed in the sprint, meaning it met your definition of done. Partially finished work counts as zero. For planning, use the average of the last three sprints rather than the best or worst single sprint.

What is a good velocity for a scrum team?

There is no universal good number. Story points are calibrated differently by every team, so a velocity of 20 on one team and 40 on another says nothing about which team delivers more. A healthy velocity is a stable one: sprint-to-sprint variation of about 10 to 20 percent is normal.

Should velocity be used to measure team or individual performance?

No. Velocity is a planning tool that belongs to the whole team. Using it as a performance target encourages estimate inflation, and tracking it per person discourages people from helping each other or taking on risky stories.

How many sprints of data do you need before velocity is reliable?

Three or four completed sprints give you enough data to plan with confidence. Before that, treat any forecast as a rough guess and say so when you share it with stakeholders.

---

Learn More

Ready to use velocity charts to plan smarter sprints? Check out the complete training series:

Watch the Project Management AI Playlist on YouTube

---

For more project management insights and resources, visit subthesis.com