It's a form of documentation, for those of us without documentation sections in our non-existent project plans.
Amen to that brother dragonchild! Although more times than not for us, the "documentation" phase is usually right before/after the "testing" phase, and both of them are in the always nebulous "last few weeks" of the project. I have been thinking about pushing the Test Driven Development Philosophy as a way to avoid this all too common scenario, and get both tested code and (pseudo) documentation in one fell swoop.
-stvn