Refine
Year of publication
- 2022 (4) (remove)
Document Type
- Conference Proceeding (3)
- Bachelor Thesis (1)
Has Fulltext
- yes (4)
Is part of the Bibliography
- no (4)
Keywords
- Agilität <Management> (4) (remove)
Institute
- Fakultät IV - Wirtschaft und Informatik (4) (remove)
Context: Companies adapt agile methods, practices or artifacts for their use in practice since more than two decades. This adaptions result in a wide variety of described agile practices. For instance, the Agile Alliance lists 75 different practices in its Agile Glossary. This situation may lead to misunderstandings, as agile practices with similar names can be interpreted and used differently.
Objective: This paper synthesize an integrated list of agile practices, both from primary and secondary sources.
Method: We performed a tertiary study to identify existing overviews and lists of agile practices in the literature. We identified 876 studies, of which 37 were included.
Results: The results of our paper show that certain agile practices are listed and used more often in existing studies. Our integrated list of agile practices comprises 38 entries structured in five categories. Conclusion: The high number of agile practices and thus, the wide variety increased steadily over the past decades due to the adaption of agile methods. Based on our findings, we present a comprehensive overview of agile practices. The research community benefits from our integrated list of agile practices as a potential basis for future research. Also, practitioners benefit from our findings, as the structured overview of agile practices provides the opportunity to select or adapt practices for their specific needs.
In 2020, the world changed due to the Covid 19 pandemic. Containment measures to reduce the spread of the virus were planned and implemented by many countries and companies. Worldwide, companies sent their employees to work from home. This change has led to significant challenges in teams that were co-located before the pandemic. Agile software development teams were affected by this switch, as agile methods focus on communication and collaboration. Research results have already been published on the challenges of switching to remote work and the effects on agile software development teams. This article presents a systematic literature review. We identified 12 relevant papers for our studies and analyzed them on detail. The results provide an overview how agile software development teams reacted to the switch to remote work, e.g., which agile practices they adapted. We also gained insights on the changes of the performance of agile software development teams and social effects on agile software development teams during the pandemic.
Companies worldwide have enabled their employees to work remotely as a consequence of the Covid 19 pandemic. Software development is a human-centered discipline and thrives on teamwork. Agile methods are focusing on several social aspects of software development. Software development teams in Germany were mainly co-located before the pandemic. This paper aims to validate the findings of existing studies by expanding on an existing multiple-case study. Therefore, we collected data by conducting semi-structured interviews, observing agile practices, and viewing project documents in three cases. Based on the results, we can confirm the following findings: 1) The teams rapidly adapted the agile practices and roles, 2) communication is more objective within the teams, 3) decreased social exchange between team members, 4) the expectation of a combined approach of remote and onsite work after the pandemic, 5) stable or increased (perceived) performance and 6) stable or increased well-being of team members.
Das Konzept der Agilität stiftet insbesondere im Kontext der Softwareentwicklung einen Nutzen. Es stellt sich die Frage, wie auch die öffentliche Verwaltung agiler werden und schlussendlich davon profitieren kann. Bislang liefern nur wenige Schriften eine dedizierte Auseinandersetzung mit dem Thema der agilen Verwaltung. In dieser Arbeit wird untersucht, ob agile Softwareentwicklung Ausgangspunkt einer potenziell agilen Verwaltung in Deutschland sein kann. Im Rahmen einer theorievergleichenden Gegenüberstellung wird ein Zielbild einer agilen Verwaltung ausgehend von den Merkmalen agiler Softwareentwicklung hergeleitet. Anschließend werden mögliche Spannungslinien zwischen dem entwickelten Zielbild und dem von Max Weber beschriebenen Idealtypus einer bürokratischen Verwaltung aufgedeckt. Im Ergebnis kennzeichnet eine agile Verwaltung ein Konglomerat unterschiedlicher Merkmale, die den Dimensionen Strategie, Struktur, Prozesse, Führung, Personal und Kultur zugeordnet werden können. Die öffentliche Verwaltung wird das Konzept der Agilität nicht vollständig, im Sinne der Ausprägung aller herausgearbeiteten Merkmale, organisational etablieren können. Die wesentlichen Spannungslinien ergeben sich aus den Bürokratiemerkmalen Amtshierarchie und Regelgebundenheit. Der Idealtypus einer agilen Verwaltung kann nur insofern eine Alternative zum Idealtypus der bürokratischen Verwaltung sein, als dass diejenigen Merkmale der Bürokratie, die sich mit den wesentlichen Strukturprinzipien des deutschen Staates decken, unberührt bleiben.