Philipp Diebold

Lars Struck, Christian Veenaas, Robert Wiedekind et al.

Context: Neurodiversity is increasingly recognized as a valuable dimension of workplace diversity. However, in agile software development teams, the interplay between teamwork practices and the inclusion of neurodivergent employees remains underexplored. Objective: The study aims to explore how teamwork quality in agile software development is currently practiced and discussed in the context of neurodiversity, and to identify organizational barriers that hinder the effective inclusion of neurodivergent developers. Method: We applied a mixed-method approach combining a web content analysis covering Reddit and LinkedIn with 11 semi-structured expert interviews from a corporate neurodiversity network in a German organization. Results: The analysis shows that teamwork practices are highly fragmented and shaped by individual adaptation rather than a shared standard. While agile practices and supportive tools can enable neurodivergent participation, rigid structures, stereotypes, and one-size-fits-all approaches often undermine inclusion. Organizational awareness and tailored adjustments remain insufficient. Conclusion: Agile practices can promote inclusive teamwork, yet their benefits are constrained by rigid organizational structures and limited awareness of neurodiversity. Harnessing neurodiverse strengths demands flexible organizational conditions and tailored support.

Marco Kuhrmann, Philipp Diebold, Stephen MacDonell et al.

Software and system development is complex and diverse, and a multitude of development approaches is used and combined with each other to address the manifold challenges companies face today. To study the current state of the practice and to build a sound understanding about the utility of different development approaches and their application to modern software system development, in 2016, we launched the HELENA initiative. This paper introduces the 2nd HELENA workshop and provides an overview of the current project state. In the workshop, six teams present initial findings from their regions, impulse talk are given, and further steps of the HELENA roadmap are discussed.

Jakob Diebold, Philipp Diebold, Arthur Vetter

Smaller software companies, such as start-ups do not often follow an explicit process, but rather develop in a more or less unstructured way. Especially when they grow or customer involvement increases. This development without any structured process results in problems. Thus, our objective was the improvement of the current development process of one software start-up by introducing appropriate agile practices and eliciting their effects. For this reason, we per-formed a pre and post process assessment using interviews. Based on the initial assessment, agile practices were selected and implemented. Finally, the post assessment and additional code metrics served as controlling mechanism to check whether weak points are addressed. The comparison of the two assessments showed that 13 ISO29110 base practices have been improved by the introduced eight agile practices. Thus, even more aspects have casually been improved than initially planned. Finally, the additional retrospective with company employees showed how the introduced agile practices positively influenced their work.

Sven Theobald, Philipp Diebold

There is the widespread belief that Agile neglects the product quality. This lack of understanding how Agile processes assure the quality of the product prevents especially companies from regulated domains from an adoption of Agile. This work aims to identify which Agile Practices contribute towards product quality. Hence, data from a survey study is analyzed to identify Ag-ile Practices which are beneficial or harmful for the quality of the product. From 49 practices that were used in the survey so far, 36 were perceived to have a positive impact on product quality, while four practices were rated as being harmful. The results enrich understanding of how product quality can be achieved in Agile, and support selection of practices to improve quality.

Philipp Diebold, Jan-Peter Ostberg, Stefan Wagner et al.

Background: Agile software development has become a popular way of developing software. Scrum is the most frequently used agile framework, but it is often reported to be adapted in practice. Objective: Thus, we aim to understand how Scrum is adapted in different contexts and what are the reasons for these changes. Method: Using a structured interview guideline, we interviewed ten German companies about their concrete usage of Scrum and analysed the results qualitatively. Results: All companies vary Scrum in some way. The least variations are in the Sprint length, events, team size and requirements engineering. Many users varied the roles, effort estimations and quality assurance. Conclusions: Many variations constitute a substantial deviation from Scrum as initially proposed. For some of these variations, there are good reasons. Sometimes, however, the variations are a result of a previous non-agile, hierarchical organisation.