> A lot has been written about "hyperproductive teams". ... there’s one thing in common between all the stories I’ve heard and the successes experienced first h

> A lot has been written about "hyperproductive teams". ... there’s one thing in common between all the stories I’ve heard and the successes experienced first hand: small teams Funny because I don't think its small teams or a particular programming language that leads to great productivity. You don't have to look very far or far back to see teams, of various sizes, pulling off some amazing stuff with assembler and C. The key to productivity is a lot simpler, and independent of software development. Its a sense of responsibility, interest, and dedication. In a small team that is using small talk the responsibility might come from being on a small team with a lot of lifting to do, the interest might come from having fun using a language that you like (regardless of the language), and the dedication might come from the promise of getting in early on a promising venture - hence the small team. All of these things add up to hyper-production. If you can establish those three things, somehow, with a large team I don't see why hyper-production can't be achieved. Unfortunately modern project management for large teams seems to rely heavily on techniques that rob developers of all three qualities mentioned above in the name of so called "agile" and in pursuit of some fictitious software assembly line.