Scrum Team Metrics
This post is from Agile Complexification Inverter by David Koontz. Click here to see the original post in full.
What metrics would a great Scrum team want to generate and track the trend?
Is the necessary and sufficient set of metrics just velocity? No - I don't think that is enough. Can you help me define a short list of metrics, and the reasons for tracking them?
First let's lay out some ground rules. Who is responsible for generating the metrics? Are all metrics treated the same, e.g. should each metric have the same visibility? I'll state the the team is responsible for generating the metrics. This ensures that the metric has some minimun level of veracity. When the team believes that the metric does not tell the truth, they should make that visible and change how it is generated. This is process improvement. However not all metrics need be treated the same. Some should be published, some could stay internal to the team. As the level of trust and autonomy of the team increases the visibility of metrics should naturally become more transparent.
Here's a rough draft list - to get the conversation started. Add your comments and additional metrics. We will see if we can crowd source a great list.Metrics for the Team
- Story point velocity per sprint
- Projected capacity (in person-days) of next sprint
- Projected capability (in story points range) of next sprint
- Planned...read more
Leave a Reply