TDD is a means to an end, not an end in itself. I think some TDDers lose sight of that fact.

The end is well-tested code. Developers often lack the discipline to write tests after writing what appears to be working code. The point of TDD is to force that discipline by making it part of the process of writing the code in the first place.

It's a good technique that many use to great effect, but it is just that, a technique, not a goal in itself.

What matters is that, when you're checking in new code and pushing it upstream, that code has tests along with it. Whether you wrote the tests right before the check-in, or as part of a TDD cycle, is immaterial to everyone else.