I don't quite get the connection to TDD/Agile, but most current Unix projects actually have two files, one ChangeLog (most of them without the DOSism ".txt"), one NEWS. One for the commits, one for user-readable updates since the last release. Always found that preferable to a mixed document, where you have to filter out the major changes (or weren't able to see individual bug fixes)
The point I was trying to make is that big projects can evolve and be managed in a very simple manner, which is the case for many pieces of Unix software. The details regarding changelog nomenclature vary, and of course there may be additional plain text files which are still simply kept in the HEAD.
True. Although, to play devil's advocate, just because you can do projects in other ways doesn't mean that you couldn't do them better in Agile. (Don't get me wrong, I think that Unix projects have a better track record than Agile projects)
Personally I think the biggest benefit of "Agile" is that it's established enough to sell it to customers if you're a consultant. As no two Agile processes/teams look the same (hence the name), you've got a lot of freedom. If you came to a big company without that name brand recognition of "XP", you'd probably be forced to do it with ITIL, the Unified Process or other Godzilla-like monstrosities.
