Dokumentation in agilen Projekten

In many projects, documentation occurs in one of its two extreme forms: either almost nothing is documented, resulting in the loss of important knowledge, or there is an excess of poorly structured documents that are completely unsuitable for knowledge transfer. We can learn from agile software development methods how a needs-based documentation can look. It makes sense to create only documents that have a clearly recognizable benefit, for example, for later project phases or follow-up projects. Furthermore, it is important to understand documentation as one of several possible forms of knowledge exchange within the team. Ultimately, the usability of the documentation also depends on its design. Concise and well-structured documents offer high readability and targeted access to information.