Building a Sprint Velocity Metrics Dashboard
Design a velocity dashboard with the right metrics: average velocity, trend, standard deviation, forecast, and supporting indicators. Includes layout recommendations.
Detailed Explanation
Designing a Velocity Dashboard
A good velocity dashboard gives the team and stakeholders a single view of capacity, predictability, and forecast. Here is what to include.
Essential Metrics
1. Current Average Velocity
- Rolling average over last 5-8 sprints
- Display as a large, prominent number
- Include unit: "points/sprint"
2. Velocity Trend
- Bar chart showing points per sprint over time
- Overlay the average line
- Color-code: green for above average, red for below
3. Standard Deviation
- Show as a percentage of the mean
- Traffic light: Green (<15%), Yellow (15-25%), Red (>25%)
4. Forecast
Remaining backlog: 120 points
Sprints to complete:
Optimistic: 4 sprints (8 weeks)
Expected: 5 sprints (10 weeks)
Conservative: 6 sprints (12 weeks)
Supporting Indicators
5. Sprint Completion Rate
- Percentage of planned stories actually completed
- Target: >85%
6. Carryover Count
- Number of stories that spilled into the next sprint
- Increasing carryover predicts future velocity drops
7. Bug Ratio
- Percentage of velocity spent on bugs vs. features
- Rising bug ratio indicates quality problems
Dashboard Layout
┌─────────────────┬─────────────────┬─────────────────┐
│ Avg Velocity │ Std Deviation │ Completion Rate│
│ 28.5 pts │ 3.2 (11%) │ 89% │
├─────────────────┴─────────────────┴─────────────────┤
│ Velocity Trend (Bar Chart) │
│ ▓▓▓ ▓▓▓▓ ▓▓ ▓▓▓▓ ▓▓▓ ▓▓▓▓ ▓▓▓ ▓▓▓▓ │
├─────────────────────────────────────────────────────┤
│ Release Forecast │
│ Optimistic: Mar 15 │ Expected: Mar 29 │
│ Conservative: Apr 12 │
├─────────────────┬───────────────────────────────────┤
│ Carryover: 1.5 │ Bug Ratio: 18% │
└─────────────────┴───────────────────────────────────┘
Audience-Specific Views
| Audience | Focus Metrics |
|---|---|
| Team | Burndown, WIP, completion rate |
| Scrum Master | Velocity trend, std dev, carryover |
| Product Owner | Forecast, scope changes, burn-up |
| Executives | Release date range, risk indicators |
Tools
You can build dashboards with Jira, Azure DevOps, or simple spreadsheets. The Sprint Velocity Calculator tool on this page provides the core statistics you need.
Use Case
Use this guide when setting up a team or program dashboard for velocity tracking, or when asked to present velocity data to different stakeholder groups.