Documentation Fit for Purpose
Documentation is still a difficult topic in many IT projects. In some projects, documentation doesn't seem to happen at all. Others produce documents on end — documents that are hardly ever used and become outdated easily. One approach is about as bad as the other.
Agile methods demand that documentation not be written for its own sake. Documentation should always be justified by the benefits it creates. This way we can avoid producing what is sometimes referred to as write-only documentation, but will create documentation that is truly fit for purpose.
Integration into Agile Processes
There are more questions than just what exactly needs to be documented. What should the documentation look like? And how can its production be integrated into agile processes?
Documentation fit for purpose in Scrum and Kanban projects
Usage of Wikis for project documentation
Copyright Andreas Rüping, 2004 - 2018. 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