Back to Details

agile-metrics

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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

1. 速度（Velocity）

Definition: Story points completed per sprint
markdown
undefined
定义：每个冲刺完成的故事点数
markdown
undefined

Velocity Trend

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
undefined
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
undefined

2. Burn-Down Chart

2. 燃尽图（Burn-Down Chart）

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

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

● Actual
─ Ideal

3. Team Health Metrics

3. 团队健康指标

markdown
| 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 | ↗️ |
markdown
| 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
  1. 关注趋势 - 而非单个冲刺
  2. 用于规划 - 而非绩效评估
  3. 团队自主拥有指标 - 而非强制施加
  4. 多指标结合 - 全面视角
  5. 持续追踪 - 定期更新
  6. 数据可视化 - 图表和仪表盘
  7. 基于洞察行动 - 推动改进
  8. 结合上下文 - 考虑相关因素

Resources

资源

  • Agile Metrics: Scrum.org guide
  • Jira/Azure DevOps: Metric dashboards
  • 敏捷指标：Scrum.org 指南
  • Jira/Azure DevOps：指标仪表盘