--- In
agile-testing@..., "Adam White" <adam_white99@...>
wrote:
>
> I'm wondering how well agile scales as the teams get larger. Does
> anyone have any experiences they can share about using scrum on a team
> of 35-40 developers and testers for an enterprise level product?
I was on a project like this at Thoughtworks.
First we divided the work roughly into 'front end' and 'back end'
teams. We had Architects designing the APIs for communication between
the projects (which were always changing of course).
Stories for each iteration for each team could range fairly widely in
terms of point size. Each large team would reformulate itself
iteration-to-iteration, with larger subgroups handling larger stories
and smaller subgroups handling smaller stories or more specialized
stories.
There was a single Project Manager (who was awesome) to handle overall
burndown charts, project scope, story management, budget, personnel,
etc.
We also had a single Build Guy managing code repositories and test
environments and such.
Also keep in mind that Thoughtworks had been refining their agile
process(es) for more than a decade at that point, so calling what we
did "Scrum" would not really be accurate. It was a sophisticated
process created over a long time by very skilled practitioners.
