Exploring the Prevalence of Anti-patterns in the Application of Scrum in Software Development Organizations

• Autorzy: Wróbel Michał R. , Przała Dorota , Weichbroth Paweł

Identyfikatory

DOI

10.15439/2023F9562

• Języki publikacji: EN

Abstrakty

EN

The paper presents a survey-based study that aimed to determine the prevalence of anti-patterns in the Scrum software development methodology. A total of 35 anti-patterns were selected from the literature review, and 42 respondents indicated whether they had encountered each anti-pattern in their organizations. The study found that``Unfinished Tasks'' was the most prevalent anti-pattern, highlighting the importance of proper planning and task management within sprints. Additionally, several other common anti-patterns were identified, including daily scrums being extended beyond the recommended time, user stories not being fully refined, and the sprint goal not being defined at the sprint planning meeting. The findings of this study provide valuable insights into the current state of Scrum methodology in software development organizations and highlight areas where there is room for improvement.

Słowa kluczowe

EN

industry; organization; software; planning; cultural difference; Scrum

PL

przemysł; organizacja; oprogramowanie; planowanie; różnica kulturowa; Scrum

• Wydawca: Polskie Towarzystwo Informatyczne
• Czasopismo: Annals of Computer Science and Information Systems
• Rocznik: 2023
• Tom: Vol. 35
• Strony: 813--822
• Opis fizyczny: Bibliogr. 14 poz., wykr., tab.

Twórcy

autor

Wróbel Michał R.

• Faculty of Electronics, Telecommunications and Informatics, Gdansk University of Technology, Gabriela Narutowicza 11/12, Gdańsk 80-233, Poland

autor

Przała Dorota

• Faculty of Electronics, Telecommunications and Informatics, Gdansk University of Technology, Gabriela Narutowicza 11/12, Gdańsk 80-233, Poland

autor

Weichbroth Paweł

• Faculty of Electronics, Telecommunications and Informatics, Gdansk University of Technology, Gabriela Narutowicza 11/12, Gdańsk 80-233, Poland

Bibliografia

• 1. T. Raharjo and B. Purwandari, “Agile project management challenges and mapping solutions: A systematic literature review,” in Proceedings of the 3rd International Conference on Software Engineering and Information Management, 2020. http://dx.doi.org/10.1145/3378936.3378949 pp. 123–129.
• 2. K. Beck, M. Beedle, A. Van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries et al., “Manifesto for agile software development,” 2001.
• 3. P. Weichbroth, “A case study on implementing agile techniques and practices: Rationale, benefits, barriers and business implications for hardware development,” Applied Sciences, vol. 12, no. 17, p. 8457, 2022. http://dx.doi.org/10.3390/app12178457
• 4. S. Hassani-Alaoui, A. F. Cameron, and T. Giannelia, “we use scrum, but ...": Agile modifications and project success,” in Hawaii International Conference on System Sciences, 2020. http://dx.doi.org/10.24251/HICSS.2020.765
• 5. “State of agile report,” https://digital.ai/resource-center/analyst-reports/state-of-agile-report/, 2022, accessed: 2023-07-31.
• 6. V.-P. Eloranta, K. Koskimies, T. Mikkonen, and J. Vuorinen, “Scrum anti-patterns–an empirical study,” in 2013 20th Asia-Pacific Software Engineering Conference (APSEC), vol. 1. IEEE, 2013. doi: 10.1109/APSEC.2013.72 pp. 503–510.
• 7. C. Matthies, T. Kowark, K. Richly, M. Uflacker, and H. Plattner, “How surveys, tutors, and software help to assess scrum adoption in a classroom software engineering project,” in Proceedings of the 38th International Conference on Software Engineering Companion, 2016. http://dx.doi.org/10.1145/2889160.2889182 pp. 313–322.
• 8. P. J. Carew and D. Glynn, “Anti-patterns in agile adoption: A grounded theory case study of one irish it organisation,” Global Journal of Flexible Systems Management, vol. 18, pp. 275–289, 2017. http://dx.doi.org/10.1007/s40171-017-0162-8
• 9. M. Mortada, H. M. Ayas, and R. Hebig, “Why do software teams deviate from scrum? reasons and implications,” in Proceedings of the International Conference on Software and System Processes, 2020. http://dx.doi.org/10.1145/3379177.3388899 pp. 71–80.
• 10. E. Çetin and P. Onay Durdu, “Blended scrum model for software development organizations,” Journal of Software: Evolution and Process, vol. 31, no. 2, p. e2147, 2019. http://dx.doi.org/10.1002/smr.2147
• 11. V. T. Heikkilä, M. Paasivaara, and C. Lassenius, “Scrumbut, but does it matter? a mixed-method study of the planning process of a multi-team scrum organization,” in 2013 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. IEEE, 2013. http://dx.doi.org/10.1109/ESEM.2013.27 pp. 85–94.
• 12. T. McKenzie, M. Morales-Trujillo, S. Lukosch, and S. Hoermann, “Is agile not agile enough? a study on how agile is applied and misapplied in the video game development industry,” in 2021 IEEE/ACM Joint 15th International Conference on Software and System Processes (ICSSP) and 16th ACM/IEEE International Conference on Global Software Engineering (ICGSE). IEEE, 2021. http://dx.doi.org/10.1109/ICSSP-ICGSE52873.2021.00019 pp. 94–105.
• 13. T. Perry, “The intermediate customer anti-pattern,” in Agile 2008 Conference. IEEE, 2008. http://dx.doi.org/10.1109/Agile.2008.74 pp. 280–283.
• 14. K. Schwaber and J. Sutherland, “The scrum guide,” https://www.scrum.org/resources/scrum-guide, 2020, accessed: 2023-04-10.

Uwagi

1. Thematic Tracks Regular Papers

2. Opracowanie rekordu ze środków MEiN, umowa nr SONP/SP/546092/2022 w ramach programu "Społeczna odpowiedzialność nauki" - moduł: Popularyzacja nauki i promocja sportu (2024).