This is way off,(reply fail?) but interesting, - look at how they
scale in the army, just for a comparison. It doesn’t really apply to
software, but at least is easy to see how they scale at a glance. Of
course, you must think of your basic developer as a basic soldier,
your senior guys as non commissioned officers {hell yeah, those guys
had my respect!}, and your management guys as commissioned officers .
http://en.wikipedia.org/wiki/British_Army#Operational
Company of about 100 soldiers, typically in three platoons, commanded
by a Major.
Platoon of about 30 soldiers, commanded by a Second Lieutenant,
Lieutenant or, for specialist platoons such as recce or anti-tank, a
Captain.
Section of about 8 to 10 soldiers, commanded by a Corporal.
It scales bigger of course.
Also was is interesting is within the basic team (called a Section)
soldiers are assigned pairs/buddies, much like paired programming.
On Mar 4, 2010, at 5:04 PM, Nic Benders wrote:
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
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
