SCRUM Retrospective Discussions Support Based on Class-Diagram Redocumentation

Despite the fact that software developers perceive the need for good documentation, it is usually at the tail end of interest in pragmatically oriented approaches. The problem is also the fact that, as the evaluation indicators of the project, the prevailing metrics that follow the aspect of time are more important than the aspect of quality. The solution here can be the re-documentation itself, the automatic generation of documentation in the background of the developers' work from the artifacts created during the development itself. This paper analyses the approaches, documentation tools and forms in any way related to the agile Scrum approach in software development. As a result it offers its own prototype documentation tool integrated into Atlassians' Confluence platform with a link to the GitHub repository and Jira issue tracking system. He evaluates his own solution by a qualitatively controlled interview with the stakeholders.