In many IT projects documentation is a difficult topic. In some projects, documentation doesn't seem to happen at all, while others drown themselves in heaps of paper that nobody is ever going to read. In order to maintain a balance, it helps to take a look at the principles of agile development.
The core idea is not to write documentation for its own sake. Documentation should always be justified by the benefits it creates. This way we can avoid to produce what is sometimes referred to as write-only documentation.
Towards Documentation Fit for Purpose
When the process of its production embodies agile principles, documentation can be expected to be fit for purpose. I wrote two books on this topic (one in English, the other in German), and I'm happy to offer consulting in this area:
Support for projects aiming to get more agile with regard to documentation
Documentation fir for purpose in Scrum and Kanban projects
Usage of Wikis for project documentation
Copyright Andreas Rüping, 2004 - 2016. I cannot accept responsibility for materials on other web sites to which external links from my web site may point. The owners of those sites hold the sole responsibility for their content.
Imprint: Dr. Andreas Rüping, Sodenkamp 21 A, 22337 Hamburg, Germany, Tax Id 26/225/34412 (Tax office Hamburg-Nord), VAT identification number DE235918641