agile-metrics

spjoshis's avatarfrom spjoshis

Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 30, 2025
[Project Management]

When & Why to Use This Skill

This Claude skill empowers teams to master agile metrics by tracking key performance indicators like velocity, burn-down charts, and cycle times. It facilitates data-driven decision-making to optimize team productivity, accurately forecast delivery timelines, and identify process bottlenecks for continuous improvement in software development lifecycles.

Use Cases

  • Sprint Planning: Use historical velocity trends to accurately forecast team capacity and commit to the right amount of work for upcoming sprints.
  • Bottleneck Identification: Analyze cycle time and burn-down charts to pinpoint where tasks are stalling and implement process improvements.
  • Stakeholder Reporting: Generate visual data representations and health indicators to provide transparent progress updates and delivery predictions to management.
  • Team Health Assessment: Monitor a balanced scorecard of velocity, happiness, and code quality to ensure sustainable team performance and morale.
nameagile-metrics
descriptionMaster agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.

Agile Metrics

Track and analyze agile metrics to measure team performance, predict delivery, and drive continuous improvement.

When to Use This Skill

  • Measuring team performance
  • Forecasting delivery
  • Identifying bottlenecks
  • Sprint planning
  • Stakeholder reporting
  • Process improvement
  • Team health assessment
  • Trend analysis

Core Concepts

1. Velocity

Definition: Story points completed per sprint

## Velocity Trend

Sprint 1: 35 points
Sprint 2: 42 points
Sprint 3: 38 points
Sprint 4: 45 points
Sprint 5: 43 points
Sprint 6: 47 points

**Average Velocity**: 42 points
**Trend**: Increasing (+2 points per sprint)
**Forecast**: Sprint 7 likely 45-50 points

2. Burn-Down Chart

Story Points
50 |●
40 |  ●
30 |    ●
20 |      ●
10 |        ●
0  |__________●
   Day 1  3  5  7  9  10

● Actual
─ Ideal

3. Team Health Metrics

| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| Velocity | 40-45 | 43 | ↗️ |
| Sprint Completion | >90% | 95% | ↗️ |
| Team Happiness | >7/10 | 8/10 | → |
| Code Quality (bugs) | <5 | 3 | ↗️ |
| Cycle Time | <5 days | 4 days | ↗️ |

Best Practices

  1. Focus on trends - Not individual sprint
  2. Use for planning - Not performance reviews
  3. Team-owned metrics - Not imposed
  4. Multiple indicators - Holistic view
  5. Continuous tracking - Regular updates
  6. Visualize data - Charts and dashboards
  7. Act on insights - Drive improvements
  8. Context matters - Consider factors

Resources

  • Agile Metrics: Scrum.org guide
  • Jira/Azure DevOps: Metric dashboards