8 ms·
"That is, again, why I hired them." That's easy to say when there's only five. The problem is, that doesn't scale. At some point you need to proactively implem
by chiefalchemist 7y ago
"That is, again, why I hired them."
That's easy to say when there's only five. The problem is, that doesn't scale. At some point you need to proactively implement a culture (and M&Ps) that does scale. If you wait til you need then you run the risk of having waited too long. Veteran team members will be put off, new hires will be updating their CV.
- abraae 7y agoI've experienced the office of about 6 people (mentioned in a post on Epic Games) as an ideal environment for software development, better than cube farms or single person offices. Maybe instead of struggling to apply management concepts to the development process, companies would achieve more by breaking things up into 6-person sized teams.
- akeck 7y agoI've always considered 5 the max, because each person tracks four [1] others. [1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2864034/#!po=1.66667 https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2864034/#!po=1....
- dodobirdlord 7y agoThis reminds me of Amazon's beloved 'two pizza team' idea. https://zurb.com/word/two-pizza-team https://zurb.com/word/two-pizza-team
- fredsir 7y agoHopefully that is family-sized pizzas.
- madhadron 7y ago> Maybe instead of struggling to apply management concepts to the development process, companies would achieve more by breaking things up into 6-person sized teams. How do you coordinate the six person teams, prevent them from ending up in contention, etc.?
- downrightmike 7y agouser stories and delegation
- madhadron 7y agoAh, the innocence that thinks that is enough.
- downrightmike 7y agoThe title is minimal :)
- dodobirdlord 7y agoThe Amazon model to addressing this problem is to minimize to the greatest extent possible both team size and inter-team communication. The ideal team is characterized by 5-8 engineers who collectively design, build, test, deploy, and own in production a service exposed to the rest of the company only through API calls over the network. This mostly addresses the coordination problem because teams shouldn't need to coordinate, and it mostly addresses the contention problem because almost every decision is entirely owned within a particular team with no expectation that they consider external input.
- paulcole 7y agoThis also caught my eye, “Developers with nothing to do become disruptive or lazy.” So the trick is to pat yourself on the back for being so good at hiring (but please recognize that if your genius hires aren’t worked to 100% capacity they will suddenly become a problem) and then make sure they never have any downtime. Seems easy enough.