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.
About this tool
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
Loading more......
Information
Categories
Tags
Similar Products
6 result(s)Short 15-minute daily meeting in agile methodologies where team members synchronize work, discuss progress toward sprint goals, and identify blockers. Promotes collaboration, transparency, and quick problem resolution.
Agile estimation technique where team members use cards to provide time/effort estimates for tasks anonymously before discussion. Combines individual expertise with team consensus to improve estimation accuracy and reduce anchoring bias.
Agile management method using visual boards to track work through stages of completion. Built on continuous improvement philosophy with four core principles: visualize workflow, limit work in progress, manage flow, and continuously improve.
A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.
A stakeholder-driven prioritization approach that categorizes requirements and features as Must have, Should have, Could have, and Won't have to prevent scope creep and ensure focus.
A regular team or personal reflection practice borrowed from Agile to review what went well, what didn't, and what to improve, enabling continuous learning and process optimization.