Well, there are often external dependencies and integration challenges, regardless of team size. But I agree with you that smaller teams are better- teams with a max size of about 7 or 8 are ideal.
In my world, TDD is not necessarily dependent on customer specifications; the point of TDD is to formalize intent, sure, but the path there is a process of discovery about the problem space. It's also a nice way to be able to automate and to quantify your testing. It can be tedious, however, when refactoring code and you question whether some of the mundane failures are worth fixing.
In my world, TDD is not necessarily dependent on customer specifications; the point of TDD is to formalize intent, sure, but the path there is a process of discovery about the problem space. It's also a nice way to be able to automate and to quantify your testing. It can be tedious, however, when refactoring code and you question whether some of the mundane failures are worth fixing.