Re: [scrumdevelopment] Scaling Scrum
- I've had more success with a single 10-person team than with two 4-5 person teams. Ten is the awkward number where it's either too big or too small. I work with one team that has 13 people. None of us like it but they've looked at, the ScrumMaster has looked at it, and so have I. None of us has found an organization for that team that we think would be an improvement. Does that mean I want to go around advocating 13 as a common team size? No, but in this case it seems the best but we're constantly thinking in the backs of our minds about how to split them up.As you grow beyond 10 I suspect you'll find ways to split up but I wouldn't worry about them right now if 10 is working for you.Regards,On Oct 31, 2006, at 6:15 AM, Ragnar Birgisson wrote:
Jeff Sutherland and I are concerned. Many organizations are now trying to scale Scrum to larger projects and to entire organizational units, reaping the benefits they have seen in smaller Scrum initiatives.
Unfortunately, there isn't a lot of guidance on how to do this. This has given rise to IBM's methodological response to DevOps, and to commercial one-size-fits all methodologies like SAFe and DAD.
To read more about how we intend to fill this need in a manner consonant with the Agile Manifesto and the principles of Scrum, I refer you to a blog I wrote at Scaling Scrum.