Velocity Tracking
Agile metric measuring team's average amount of work completed per sprint, typically in story points. Used for capacity planning, forecasting, and identifying productivity trends over time.
Last updated: 2026-03-12 11:52
Overview
Velocity tracking is an agile practice that measures how much work a team completes in each sprint, typically measured in story points. It provides a baseline for planning future sprints and forecasting project completion dates.
What is Velocity
Velocity = Sum of story points for completed user stories in a sprint
For example:
- Sprint 1: 23 points completed
- Sprint 2: 27 points completed
- Sprint 3: 25 points completed
- Average velocity: 25 points per sprint
How to Calculate
Per Sprint:
- Add up story points for all completed stories
- Only count fully "done" stories (not partially complete)
- Don't count carried-over work
- Record the total
Average Velocity:
- Calculate mean of last 3-5 sprints
- More sprints = more stable average
- Use for capacity planning
- Adjust for team changes
Uses of Velocity
Sprint Planning:
- Determine realistic sprint commitment
- Avoid over/under-committing
- Balance team capacity
- Set achievable goals
Forecasting:
- Estimate completion dates
- Calculate remaining sprints needed
- Project roadmap timelines
- Set stakeholder expectations
Improvement Tracking:
- Identify productivity trends
- Measure impact of process changes
- Assess team growth
- Spot impediments early
Best Practices
- Track consistently across sprints
- Don't compare velocity between teams
- Use as planning tool, not performance metric
- Account for team changes
- Consider capacity variations (holidays, etc.)
- Track over 3-5 sprints for stability
- Don't artificially inflate velocity
Common Mistakes
- Using as performance measurement
- Pressuring teams to increase velocity
- Comparing different teams
- Focusing on velocity over value delivered
- Not adjusting for team size changes
- Using first few sprints (unstable)
Factors Affecting Velocity
- Team size and composition
- Team experience and skill
- Technical debt
- Process improvements
- External dependencies
- Sprint length
- Definition of done consistency
Tools for Tracking
- Jira velocity charts
- Azure DevOps analytics
- Trello with power-ups
- Spreadsheet tracking
- Rally Software
- VersionOne
Related Metrics
- Sprint burndown
- Cumulative flow
- Cycle time
- Lead time
- Throughput
Related Items
1-3-9 Method
A powerful task prioritization framework that limits daily focus to 13 manageable tasks: one critical priority, three important tasks, and nine smaller tasks to ensure proper attention allocation across different priority levels.
10-10-10 Rule
Decision-making framework by Suzy Welch that evaluates choices by considering their impact in 10 minutes, 10 months, and 10 years. This method enables logical, grounded decisions by balancing short-term demands with long-term vision, eradicating rash decision-making.
12 Week Year Method
A productivity and goal-setting system developed by Brian P. Moran and Michael Lennington that redefines your year to be 12 weeks long, eliminating procrastination through increased urgency and shortened planning cycles to achieve more in less time.
18-Minute Plan
The 18-Minute Plan is a daily productivity ritual created by Peter Bregman consisting of 5 minutes of morning planning, 1 minute of refocus every hour for 8 hours, and 5 minutes of evening review to manage your day and master distraction.