What is velocity?
Velocity is a metric that tracks how much work a team delivers in a single iteration or sprint. It is usually measured in story points, tasks completed, or another consistent unit. Teams calculate velocity by summing the estimates of all items finished and accepted at the end of each sprint, then averaging over several sprints to get a reliable baseline.
The concept originated in Extreme Programming and was popularized by Scrum. It serves as a planning input rather than a performance target: teams use their historical velocity to forecast how many items they can commit to in upcoming sprints.
Why velocity matters
Velocity gives product managers and team leads a data-driven foundation for release planning. Instead of guessing whether a feature set will ship in four weeks or eight, they can compare the backlog's total estimated effort against the team's average velocity and produce a realistic range. This reduces the guesswork that leads to missed deadlines and overcommitted roadmaps.
It also acts as an early warning system. A sustained drop in velocity often signals blockers, scope creep, or mounting technical debt. Conversely, a sudden spike can indicate that estimates are being inflated or that the team is cutting corners on quality. The metric is most useful when paired with qualitative checks like retrospectives.
One important caveat: velocity should never be used to compare teams. Different teams estimate differently, work on different problem domains, and have different definitions of done. Velocity is a self-calibration tool, not a leaderboard.
How Flux approaches velocity
Flux is a kanban-first platform, so it does not include native sprint-based velocity tracking. Kanban teams typically measure throughput (items completed per time period) instead, which serves a similar forecasting purpose without requiring fixed iteration boundaries. Flux's event-sourced activity log records every card creation, move, and completion with timestamps, giving you the raw data to calculate throughput or export to a dedicated analytics tool for velocity charts.
If your team follows Scrum and needs velocity tracking, you can use Flux's labels and multi-board views to organize work into sprints, then measure completed items per cycle using the activity history.
Related terms
See also: Throughput, Sprint, Burndown chart.