3 ms·
Depends on the size of the team. If you have a 5 or even 10 person team, then maybe. If you have 100? You need methodology. Once you break a project down into
by beat 13y ago
Depends on the size of the team. If you have a 5 or even 10 person team, then maybe. If you have 100? You need methodology.
Once you break a project down into subcomponents that interact, you need to coordinate release of any changes to interfaces, so the work of one team doesn't break the work of another.
- jasonwocky 13y agoExactly. Lots of things "work" for small projects. Try to scale some of those strategies, however, and things break down.
- huherto 13y agoI still think it is the capability of the people what makes the difference. I actually have had the experience of leading a team of 50 developers in a 120 people project. We all were the new on the project and didn't know each other, I basically picked the most qualified 7 developers and formed teams. We broke the project into modules and look for smart ways to work and not stepping over each other.