3 ms·

They work, but you still need very capable people (developers, managers, product owners, etc). Furthermore, if you have a very capable team, you may not even n

• nbouscal 13y ago
  In other words, they work, but only when you don't need them? Funny definition of "work", that. (This actually perfectly matches my experience. A good team can work in spite of a methodology; a bad team won't work regardless of the methodology.)
• 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 ago
    Exactly. Lots of things "work" for small projects. Try to scale some of those strategies, however, and things break down.
  • huherto 13y ago
    I 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.