Definition
Velocity
Velocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
Key takeaways
- Velocity is the average work a team completes per cycle, measured in issues or story points, used to forecast the next cycle.
- It is relative and local: meaningful only against that same team's history, never as a way to compare teams.
- Pushing a team to increase velocity corrupts it — people inflate estimates and the number loses all forecasting value.
- A rolling average over several cycles is far more useful than any single reading, which holidays and scope changes distort.
Velocity is an empirical measurement: count the completed work at the end of each cycle, average it across the last several cycles, and use that number to plan the next one. If a team reliably finishes around forty points a cycle, committing to eighty is fiction. Velocity replaces optimism with evidence.
Its single most important property is that it is relative and local. A team's velocity is meaningful only against that same team's history, because story points and working norms differ everywhere. Comparing velocity between teams, or pushing a team to increase it, corrupts the measurement — people simply inflate estimates and the number loses all forecasting value.
Velocity stabilizes only when cycles are consistent in length and the team is stable. New members, holidays, and shifting scope all perturb it, which is why a rolling average over several cycles is far more useful than any single reading.
Planoda computes rolling velocity from completed cycle work automatically, so forecasting draws on real history rather than a hopeful guess.
Related terms
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
- BurndownA burndown chart tracks remaining work against time over a cycle, sloping from the total scope down toward zero as items are completed. It shows whether a team is on pace to finish what it committed to, making slippage visible early. The ideal line falls steadily; a flat line warns that work is stalling.
- Story Points (Estimation)Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.
- WIP LimitA WIP (work-in-progress) limit is a cap on how many items may be active in a given workflow stage at once. By forcing a team to finish work before starting more, WIP limits expose bottlenecks, reduce context-switching, and shorten cycle time. They are the core mechanism that makes Kanban flow rather than pile up.