Velocity (Agile)
How much a team gets done per sprint, in story points - a gauge for realistic planning. Turn it into a target to maximize and teams just inflate their estimates.
- Term
- Velocity (agile)
- Measures
- Story points completed per sprint
- Used for
- Forecasting team capacity
- Not
- A productivity target to maximize
Forms & parts of speech
Definition in plain terms
Velocity, in agile development, is a measure of how much work a team completes in a sprint, usually expressed in story points.
After each sprint, the team adds up the points of the work it actually finished; averaged over several sprints, this gives the team's velocity - a realistic gauge of its capacity.
Velocity is used for planning: knowing a team typically completes around a certain number of points per sprint lets it forecast how much it can take on next sprint and roughly how long a larger body of work will take. Crucially, velocity is a descriptive planning tool, not a performance target.
Because it's measured in the team's own relative points, it isn't comparable across teams, and trying to push velocity up as a goal usually just causes teams to inflate their point estimates, making the number meaningless. Healthy velocity is stable and used for honest forecasting.
Why it matters to growth leaders
Velocity is an engineering-team metric, but understanding it helps a growth leader plan realistic roadmaps and avoid a common management mistake.
The useful part is that a team's velocity provides an evidence-based forecast of capacity - far better than wishful timelines - so a growth leader scoping initiatives with engineering can set expectations grounded in what the team actually delivers.
The important caution is not to treat velocity as a productivity target to maximize, because doing so corrupts it: teams respond to pressure on velocity by inflating estimates rather than doing more real work, and the metric stops reflecting reality.
This is a specific case of a general lesson - when a measure becomes a target, it ceases to be a good measure.
For a growth leader, respecting velocity as a planning gauge rather than a stick, and resisting the urge to compare velocities across teams, leads to more realistic roadmaps and a healthier relationship with the teams building growth.
Velocity is simply how many story points the team completes per sprint, averaged over time to gauge realistic capacity.
Used well, it gives the growth leader an evidence-based forecast: the team reliably completes around 32 points a sprint, so the roadmap should be planned around that, not around wishful timelines.
But the leader recognizes that velocity is a descriptive planning tool, not a target to maximize - pressing the team to raise it just prompts them to inflate their point estimates, doing no more real work while making the number meaningless.
It's the classic trap: when a measure becomes a target, it stops being a good measure.
So the growth leader uses velocity to set honest expectations and scope realistic sprints, resists comparing it to other teams' (since points aren't standardized), and keeps it as a stable gauge rather than a stick.
Respecting velocity as a planning tool, the leader builds realistic roadmaps and a healthier, more trusting relationship with the team actually delivering the growth work.
Synonyms & antonyms
Synonyms
Antonyms
Origin & history
Velocity gauges how many story points an agile team completes per sprint, used to forecast capacity; a descriptive planning tool rather than a target, it loses meaning when pushed as a goal or compared across teams.
Etymology: source.
Usage trends
Search interest for this term over the last five years:
Common questions
- What is velocity in agile?
- A measure of how much work — typically in story points — a team completes per sprint; averaged over time, it forecasts how much the team can take on.
- Why shouldn't velocity be a target?
- Pushing velocity up as a goal usually just makes teams inflate their estimates rather than do more real work, corrupting the metric — when a measure becomes a target, it stops being a good measure.
- Can you compare velocity across teams?
- No — velocity is measured in each team's own relative story points, so it isn't comparable across teams; it's a per-team planning gauge, not a standardized productivity score.
Related tools & calculators
Resources & people to follow
- referenceWikipedia — velocity (software development)
- referenceAgile and product practice
- referenceRGM analysis — velocity is a planning gauge, not a target; making it a target just inflates estimates — when a measure becomes a target it stops measuring
Curated, non-competitor resources verified per term.
Related training
Disciplines
Areas of marketing where velocity (agile) is a core concern: