Preview Mode Links will not work in preview mode

Agile Coaches' Corner shares practical concepts in an approachable way. It is for agile practitioners and business leaders seeking expert advice on improving the way they work to achieve their desired outcomes. If you have a topic you'd like discussed, email it to podcast@agilethought.com, or tweet it with #agilethoughtpodcast.

Aug 18, 2020

In this episode, Professional Scrum Trainer Eric Landes addresses the questions: "How do you measure a Scrum Team's Performance?"

What Does the Scrum Guide say About Measuring Performance?

In many of our Scrum classes, the issue of measuring performance is asked about how can we measure a Scrum team's performance. It is a good question that the Scrum guide does give some information on the guide states that one of the inputs of Sprint planning is past performance of the development team. It also States that the daily Scrum optimizes team collaboration and performance by inspecting work. In these two statements, we learn that Scrum does want to help optimize team's performance. So how do we measure that though? When we go back to our question, let's talk about why we should measure a Scrum team's performance as the Scrum Guide mentions, we do need that as an input to Sprint planning.

Velocity is not the Best Measure

For this input, many teams use a velocity chart. A team's velocity chart to understand past performance. And this is a complimentary practice to Scrum. It's not actually asked for in the Scrum Guide or prescribed. But it is one well-established way to measure performance along with Sprint burndown charts and release burndown charts. I find that velocity may not be the best measure.

Use Kanban Metrics to Measure and Forecast

If this question is more about helping the team understand and communicate delivery performance, there are tools like cumulative flow charts and throughput that could be used. These metrics come from a Kanban perspective and these tools help teams understand their flow and can be used to communicate forecasts.

For instance, your team may have a throughput of one PBI done each day. Just as an example, as a for instance, while using the past metrics are never one hundred percent accurate. It can help teams as they go into Sprint planning and Kanban even gives you a forecasting method called Monte Carlo simulations that can help with this. Now this is a complex topic for sure, but the main purpose of this Trainer Talk is to introduce you to concepts beyond team velocity charts, and burndown charts.

Many Kanban metrics can be used to help teams understand their delivery capabilities better and achieve a flow that many mature teams are hallmarks of many mature teams. Scrum.org even has a class called Professional Scrum with Kanban that teaches participants to get to that flow and to help measure that flow.

Find What Works for Your Team

If you are interested in different ways to measure a Scrum team's performance, I urge you to check out some of these other metrics. There is no one size fits all. So, make sure it works for your team and self-organize around the way your team measures performance.

Want to Learn More or Get in Touch?

Register for our upcoming web meetings by visiting agilethought.com/events

See available training courses at agilethought.com/training.

Visit the website and catch up with all the episodes at AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!