Still documents are part of the product. We have to improve its quality as much as code
Why it is simpler with code?
It is text, we are supported by VCS... … we spend a lot of time dealing with layout...
And we do a lot of errors in docs. We often forget small updates because we are in an hurry...
As an engineer working on a small update of the system, I want the documentation I have to update just few click away from actual system.
And I don't want to deal with layouts
And I want to trace modification and easy see what changed
So, why we don't use some text based format and put it under VCS? Requirements and all the docs will be right in the same place as code. I've eared of something, look at how bigs do it. There is this pretty readable and easy to customize formats that can also produce cutting edge PDF. For requirements there is also that Gherkin language: Why don't we put our user stories in features files? I know there is also some way to link those with tests and finally get runnable specs. It is the holy grail of tracability!
Well… not so fast… but those feature file seem a good try. Let try to have docs on VCS then we will prepare the very final version in the release sprint.