This is part 3 of the short video series on Agile metrics where we will talk about how to measure the effectiveness of a Scrum Team.
If you haven’t watched the previous videos, I encourage you to check the part 1 on delivering Done Increment every Sprint and then part 2 on measuring the quality of Scrum.
The latest version of the Scrum Guide is very specific about this one: “The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.”
How can we use metrics to help us keep track of our progress? Where do you even start measuring effectiveness?
Watch the video to get some ideas on the Agile metrics you can use:
Measuring effectiveness of a Scrum team
First thing that comes to mind when we talk about effectiveness is productivity or performance. But we know all too well that not all performance metrics are helpful and most of them are not aligned with agile principles.
Another controvercy with measuring performance is that if a Scrum Master is responsible for it, does it mean they need to manage the team in a position of a manager? How does self-management fit into this?
So when we talk about the effectiveness of a Scrum Team we need to use different types of metrics that would not lead us to traditional performance metrics.
Tools that can help you
You don’t need to conduct fancy assessments to help you. Here are a few things I mentioned in the video:
- Team happiness index.
- Tuckman’s Stages of Group Development.
- 5 dysfunctions of a team by Patrick Lencioni.
- Skills Matrix Survey to determine the Bus Factor.
- Teamwork Factor.
In the end, metrics are there to help us start meaningful conversations about how we can get better at what we do and how we do it. When a metric reveals new information and encourages action for continuous improvement, it was used right.
What are some of the metrics that you used to measure your Scrum Team’s effectiveness and how did they help you?