All About Agile | Agile Development Made Easy


Stable Teams Really Do Matter

by Mark Levison, 30 September 2013 | The Agile Blogosphere

This content is syndicated from Agile Pain Relief by Mark Levison. To view the original post in full, click here.

 

impact-smallFor years now Rally has been performing a large ongoing experiment on the Agile world. As a side effect of providing one of the better known tools they’ve managed to see a lot of data accumulate about what makes an effective Agile team. In a report called “The Impact of Agile Quantified” they’ve sanitized the data and then run some statistical analysis on it. 

Here’s what they saw:

I was surprised to find that stable teams are less frequent among the Rally customers than my own. Rally noticed that 1 in 4 people changed every 3 months. Experience at my regular clients suggests that it should be less than that. No matter what the frequency, we have to appreciate that every change is expensive; both in terms of the knowledge lost and the consequent slowdown while team members renegotiate their relationships. It’s hard to build the high performance teams that we all seek when we have frequently changing membership.

As with any set of measures, I think the value isn’t so much in the number as the signal regarding what to look at in our teams. In addition, I suspect some high performing teams will probably be doing things that don’t show up well in the larger dataset. For instance, I’ve seen many high performing teams with less WIP than the number of team members. Instead they swarm all work, etc.

The report from Rally is well worth reading, although it’s sixteen pages long. (You will have to give away your email address).

To my friends at Rally, there are many interesting questions to be asked here. If we look only at stable teams – what do we learn about team size? If we look only at mature teams (>1 yr old and stable) – do any of our discoveries around team size and estimation change? What about time to fix defects vs. productivity or quality? What about time to fix defects vs. team size? Story size vs. productivity vs. defects? Distributed teams’ productivity? What about the highest performing teams – what where they doing…? Have you considered releasing your dataset to the rest of the world so we can help you mine it? Two reasons: more eyes will spot more ideas and the Agile ideas have always been developed and evolved in an open fashion. Perhaps you could release with the rule that anything someone else discovers from it has to be shared openly.

Hat tip to Dave Nicolette who first pointed this paper out to me


[1] In the paper this is referred to “Full Scrum” – which is odd since Scrum doesn’t require Estimation at all.

Home



Leave a Reply

What is 10 + 8 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)