Abstract
This paper examines the adoption of Scrum framework within a single software development team operating in a non-technology organization, highlighting the challenges and obstacles encountered throughout the process. Using an action research approach, the authors investigate how targeted interventions influenced the Scrum implementation process. The study focuses specifically on team organization, including the structuring and coordination of the development team, as well as the assignment of the Product Owner and Scrum Master roles. As a single-team case study, the research does not aim for statistical generalization; instead, it offers an in-depth, context-rich account from which transferable insights can be drawn. The findings culminate in a set of practical recommendations for software development teams seeking to adopt Scrum. Rather than universally applicable rules, these recommendations are best understood as lessons grounded in the studied context that may inform other enterprises operating under similar conditions and aiming to leverage Scrum to improve productivity and software product delivery. The study further serves as a basis for future multi-team and comparative research that could test the broader applicability of these findings.
Paper Type
Short Paper
DOI
10.62036/ISD.2026.20
Adoption of Scrum Methodology Within a Software Development Team in a Non-Technology Organization
This paper examines the adoption of Scrum framework within a single software development team operating in a non-technology organization, highlighting the challenges and obstacles encountered throughout the process. Using an action research approach, the authors investigate how targeted interventions influenced the Scrum implementation process. The study focuses specifically on team organization, including the structuring and coordination of the development team, as well as the assignment of the Product Owner and Scrum Master roles. As a single-team case study, the research does not aim for statistical generalization; instead, it offers an in-depth, context-rich account from which transferable insights can be drawn. The findings culminate in a set of practical recommendations for software development teams seeking to adopt Scrum. Rather than universally applicable rules, these recommendations are best understood as lessons grounded in the studied context that may inform other enterprises operating under similar conditions and aiming to leverage Scrum to improve productivity and software product delivery. The study further serves as a basis for future multi-team and comparative research that could test the broader applicability of these findings.
Recommended Citation
Hankiewicz, K. & Hankiewicz, P.(2026). Adoption of Scrum Methodology Within a Software Development Team in a Non-Technology Organization. In M. Valenta, B. Mannová, R. Pergl, A. Przybylek, M. Lang, H. Linger, C. Schneider, N. Iivari, & E. Insfran (Eds.), Making ISD Sustainable: Reloaded with AI and Automation (ISD2026 Proceedings). Prague, Czech Republic: Czech Technical University in Prague. ISBN: 978-80-01-07585-2. https://doi.org/10.62036/ISD.2026.20