The document discusses metrics that can be used for Agile teams. It recommends that metrics should align with Agile values and principles, and cautions that metrics can be misused if not carefully implemented. Example good metrics are listed such as lead time, cycle time, value delivered, and deployment frequency. The document also notes that the team themselves should do the measuring, not managers or Scrum Masters.

1. Metrics
Can’t live with them
Can’t live without them
Joe Jacob

5. • Does the metric align directly with one of the Agile Values or
Principles?
oIf yes, you are on the right track
oIf no, consider a different metric
• Even good metrics can be used in a way that will hurt your team or
organization. Be careful with all communications and be ready to
help the team understand the reason for each metric.

6. • Lead Time
• Cycle Time
• Story Churn
• Predictability
• Value Delivered
• Say / Do Ratio
•Production Outages
•Right First Time
•Mean Time to Recover (MTR)
•Batch Size
•Deployment Frequency

7. • Velocity
• Throughput
• Bugs
• Test Coverage
• Technical Debt

8. • Rework
• Story Points per Team Member
• Hours

9. • NOT your Manager
• NOT your Scrum Master
• The team should do the measuring