3 ms·
When reading this summary of "The Mythical Man Month": > The best way to do that is to organize the team like surgical units. In an operating room, there’s a l
by vog 9y ago
When reading this summary of "The Mythical Man Month":
> The best way to do that is to organize the team like surgical units. In an operating room, there’s a large group of support staff, but only one surgeon. One person cuts, not ten. A programming team then has only one programmer, but many other support stuff.
I instantly remembered what I thought when I read the book myself: Why isn't that taught at university? Or mentioned in any other software engineering book?
Many other parts of "The Mythical Man Month" are often cited, but the "Surgical Team" chapter is almost never cited.
Why is that?
Was the "Surgical Team" even unusual back then? Or, has it been tried and failed? If so, how did it fail? If not, why don't we see that pattern implemented in today's software projects?
- dllthomas 9y agoIn my recollection, it's presented as speculative. It'd definitely be interesting to know the experiences of those who've tried it in fullness since.
- vog 9y agoThanks to a3n and dllthomas for your attempts to explain this. I realized that my question is better suited for SE than for HN: https://softwareengineering.stackexchange.com/q/355203/69228 https://softwareengineering.stackexchange.com/q/355203/69228
- dllthomas 9y agoHonestly, I think this setting will get better responses (if it actually gets responses...)