I'm a big fan of "two pizza" teams. So each team has one lead, and the entire team can be fed by ordering two pizzas. I found that a group of 4-5 is perfect for just about anything, you'll find it's the common smallest fighting unit in a lot of millitaries as well.

As for project managers, I think a lot had to do with how many different projects your oranization is doing, perhaps more than how many people are doing it.

On Mar 4, 2010, at 4:41 PM, <[email protected]> wrote:

You will get a lot of feedback on this topic I'm sure but it depends on the size of the project or projects you are working on. I will list some ratios and roles that have worked for me in the past.

1 Project Manger
3 Team leaders
4 developers per team
So this would be a total of 13 people unless you want to ware multiple hats.
---------
Teams are:
Infrastructure and Architecture Team
Configuration Management, Testing, Build, Deploy Team
Design and Development Team
---------
Use pair programming, BDD, and an iterative development methodology (Agile is fine)
---------
Don't skimp on monitors - at least two large monitors per developer.











--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to