Pragmatic or not

Warning! Geek's talk ahead!

If "SIT" only means

 "To rest with the torso vertical and the body supported on the buttocks. - dictionary.com" 

to you, then you probably won't be interested in the following article.

Pragmatic or not to be.

I am trying to embrace the pragmatic approach for the current product development, it went on nicely so far, until the point that it needs to be worked with another team.

Additional requirement, behavior and expectation from the product suddenly emerged all together. Documents, documents and documents, every different bits and pieces are requested from the new comer. And all of a sudden, I realised that I simply don't have much to offer.

The old reason why there aren't detail documentation on everything that has been done is plainly because I won't be able to update the documents before implementing anything. Also, the product is still in the work in progress phase, documentation
is simply the lowest priority among everything.

I agreed that there should be details be drawn at some point but is it necessary to have it throughout the whole process? Is it something "Pragmatic"?

I doubt so. Then where's the line should be drawn?

Wiki, it should be a good candidate for requirement tracking and design principal but is it for everyone?

I have no clue, yet. Your thought?