Is it better to have a team, or the solo, maverick developer?Â It depends.Â The solo developer can work unimpeded by others, but doesn't have anyone to work with to overcome obstacles.Â Teams have meetings and have to coordinate their work.Â Slowing them down.Â As teams grow the problem gets worse.
Sometimes resource planning and project management pressure encourages us to allocate additional engineering resources to development projects.Â And there are definitely times when having a team is the best way to work quickly.
However, on integration projects more than a couple people slows the progress of the project.
I was once involved in a merger of companies.Â The acquiring company had a large team of developers working on replacing the functionality of my company, the acquired one.Â I became a team of one and the plan was that I would maintain the systems until the migration.
Management soon became frustrated as new feature development stagnated.Â So they called me and asked how long it would take to produce a specific new integration feature.Â My estimate, 40hr over two weeks.Â Then they called a meeting and asked the leader of the development team how long.Â His estimate, 6 months or more.
This wasn't solely a matter of competence.Â Sure, I was still there because I was the best on my technology.Â But the other team was not populated with slouches.Â There were just too darn many of them.Â They got in each others way.
I, on the other hand, had no one to coordinate with.Â No one to slow me down.
Teams of one are not always the best, but teams of 50 are never the best.
Or as a friend of mine likes to say, "It takes one woman nine months to have one baby, but putting nine women on the job doesn't get you a baby in only one months."