“How well is your delivery team doing?” That seems like a straightforward question for an Agile team, but it is more complicated that it might sound at first. Do we know what it means to “do well” or is it one of those things that is different to everyone?
From the perspective of Scrum, metrics and KPI evaluations are a few of the last frontiers in the process for continuous improvement. In this article, Lucas Napoli shares some metrics and KPIs that Agile software development teams should be aware of.
Metrics are an important part of the Agile software development approaches like Scrum. They are however, like velocity, more often focus on the performance of the delivery team. What about the customers? In this article, Fabio Gasparri discusses Key Performance Indicators (KPIs) that will matter for the clients.
Organizations invest in agile processes, tools, training, and coaching, but how much are they getting back? Has product delivery improved? How much happier are users and the business customers? Are employees empowered and enabled? Traditional metrics might give you insight into improvements of operational efficiency, but the real conversation is about the value created for your organization by the improved processes. Without measuring value, the success of any agile initiative is based on nothing more than intuition and assumption.
Following the famous mantra of “you can’t manage what you can’t measure”, Scrum teams have often a set of metrics to monitor their activity. Velocity, the amount of work performed by a team during a single sprint, might be one of the most famous Agile metric. Doc Norton has written an interesting book about the negative sides of velocity and what might be a good metric for an Agile team.
How do we actually know if our Agile teams are doing well? Is gut instinct enough? Furthermore, in a rapidly growing organization such as Spotify, how can we ensure some sort of consistency in our baseline level of Agile knowledge across the technology, product, and design organization?
In an ideal Agile world, the Scrum team can complete all user stories tasks that it planned for the current sprint. The real world is however different. In this article, Scott Lively explains how to use the sprint data to modify the team behavior.