4 ms·
I seem to remember reading somewhere that the "best" team size for maximizing productivity was three or four - enough so that you have some people to bounce ide
by arethuza 15y ago
I seem to remember reading somewhere that the "best" team size for maximizing productivity was three or four - enough so that you have some people to bounce ideas of off and have complementary approaches without introducing the communications overhead that you get with larger teams.
Can't remember where I read that - might have been the MMM.
- ebaysucks 15y agoWould be interested in where you read that if you find it again - below is a link to an article that says the optimal team size is 5 to 8 based on a Dunbar analysis. 3 in unstable as too often 1 person feels left out, 4 is an even number so risk of split vote. http://www.lifewithalacrity.com/2004/03/the_dunbar_numb.html http://www.lifewithalacrity.com/2004/03/the_dunbar_numb.html
- gbog 15y agosplit vote: do you really vote decisions? if it's 50/50, I'd say the real solution hasn't been found yet.
- arethuza 15y agoI read that a long long time ago - but I'll have a think and see if I can recall where it was. I'd agree that a larger team effectively mitigates risks around individuals not fitting in or decision-making being stymied, but in my own personal experience I've definitely preferred, due to a perception of maximising by own personal productivity, that 3 or 4 was best. That is, of course, completely subjective!
- arethuza 15y agoI can't find where I originally read that (although I believe the original research was by IBM). However, here is a more recent article that suggests that "best" team size is 5 plus or minus 2 - which fits into my preferred range: http://www.informit.com/articles/article.aspx?p=1674234&seqNum=7 http://www.informit.com/articles/article.aspx?p=1674234&...
- roguecoder 15y agoTechnical decisions in a 4 person team should really be built on a consensus model rather than a democracy. Otherwise there's a chance of factionalism.
- ken 15y agoProbably not MMM -- he proposes a "surgical team" for programming which has (I think) nine people, though they aren't all programmers, and some are fractional-jobs which can be shared between teams.
- gry 15y agoAnother key MMM point is it naive to expect build large systems on a meaningful schedule with small teams.
- count 15y ago'Nuclear family' teams have to be small - the folks you work every day with on a single topic. In a given large system, you can and should have many small teams working independently. Another small team should act as the 'curator' or 'middleman' for communication between teams.