# Sprint Velocity Tracking

> Agile metric measuring team output in story points per sprint, enabling predictable planning and continuous improvement through data-driven capacity assessment over multiple iterations.

- **URL:** https://www.atlassian.com/agile/project-management/metrics
- **Category:** Practices
- **Tags:** Agile, Scrum, velocity
- **Updated:** 2026-03-14 18:50
- **Canonical page:** https://timetrack.works/ja/items/sprint-velocity-tracking

## Details

## Overview

Sprint velocity measures the amount of work (typically story points) a team completes in a sprint, building predictability through historical averages for accurate planning.

## Calculation

**Velocity = Sum of story points for completed user stories in sprint**

**Average Velocity = Mean over last 3-7 sprints**

## Benefits

- Predictable capacity estimation
- Release date forecasting  
- Team performance trends
- Realistic sprint planning
- Continuous improvement metrics

## Best Practices

1. Track 5-7 sprints for reliable average
2. Use consistent story point scale
3. Don't compare teams (different contexts)
4. Focus on trend not absolute numbers
5. Account for team changes and holidays

## Common Pitfalls

- Using as performance metric
- Expecting constant increases
- Ignoring context changes
- Gaming the numbers
- Cross-team comparisons

---

_This Markdown mirror is generated by Ever Works for AI agents. The canonical HTML page is at https://timetrack.works/ja/items/sprint-velocity-tracking._