Recommendation for Scrum-Based Software Development Process with Scrum at Scale: A Case Study of Software House XYZ
Abstract
Software House XYZ employs Scrum as one of its software development processes. However, the company faces several challenges in the implementation of Scrum, leading to delays in its product releases. Two specific problems are the control of a large-scale Scrum team and the management of team commitments. To address these issues, the Scrum at Scale framework has been chosen as a solution. Before implementing Scrum at Scale, an assessment of the current Scrum maturity level at Software House XYZ is deemed necessary. The Scrum Maturity Model, adapted to the Scrum Guide 2020, is selected as the method to evaluate how effectively the company is implementing Scrum. A questionnaire comprising 81 practices was distributed to development teams, with 10 valid responses collected. Based on the assessment using the Scrum Maturity Model, the current Scrum implementation maturity at Software House XYZ is rated at level 1, Initial. A total of 61 practices are proposed for improvement in the Scrum process. Scrum at Scale can be implemented once the suggested Scrum process improvements have been made. These recommendations are structured following the framework outlined in the Scrum at Scale Guide 2022. The validation of the Scrum-at-Scale recommendations was conducted by us through interviews with representatives from Software House XYZ. From the validation results, the company expresses interest in trying to implement Scrum at Scale. However, the company agrees to enhance the existing Scrum process within the organization before fully adopting Scrum at Scale.
Downloads
References
K. S. Rubin, Essential Scrum: A Practical Guide to the Most Popular Agile Process, 1st ed. Addison-Wesley Professional, 2012.
K. Schwaber and J. Sutherland, “The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game,” 2020. [Online]. Available: http://www.scrumguides.org/docs/scrumguide/v1/Scrum-Guide-US.pdf.
Y. Shastri, R. Hoda, and R. Amor, “Does the ‘Project Manager’ Still Exist in Agile Software Development Projects?,” Sep. 2016. doi: 10.1109/APSEC.2016.019.
M. Coccia, “The Fishbone diagram to identify, systematize and analyze the sources of general purpose technologies,” 2017, doi: 10.1453/jsas.v4i4.1518.
Marchewka, “Information Technology Project Management Providing Measurable Organizational Value - Fifth Edition,” 2015.
J. C. Wood and M. C. Wood, Joseph M. Juran : Critical Evaluations in Business and Management. Routledge, 2005.
V. Pareto, Cours d’Economie Politique Professe a l’Universite de Lausanne, no. v. 1. F. Rouge, 1896.
I. Sommerville, Software Engineering, 10th ed. Pearson, 2016.
O. Uludag, M. Kleehaus, N. Dreymann, C. Kabelin, and F. Matthes, “Investigating the Adoption and Application of Large-Scale Scrum at a German Automobile Manufacturer,” Proceedings - 2019 ACM/IEEE 14th International Conference on Global Software Engineering, ICGSE 2019, pp. 22–29, 2019, doi: 10.1109/ICGSE.2019.00019.
A. M. AlMutairi and M. R. J. Qureshi, “The Proposal of Scaling the Roles in Scrum of Scrums for Distributed Large Projects,” International Journal of Information Technology and Computer Science, vol. 7, no. 8, pp. 68–74, 2015, doi: 10.5815/ijitcs.2015.08.10.
A. Putta, O. Uludag, S. L. Hong, M. Paasivaara, and C. Lassenius, “Why do organizations adopt agile scaling frameworks?-A Survey of practitioners,” in International Symposium on Empirical Software Engineering and Measurement, IEEE Computer Society, Oct. 2021. doi: 10.1145/3475716.3475788.
J. Sutherland, “The Scrum At Scale® Guide. The Definitive Guide to the Scrum@Scale Framework: Scaling that Works,” 2022, [Online]. Available: https://www.scrumatscale.com/wp-content/uploads/2020/12/official-scrum-at-scale-guide.pdf
K. C. Abimaulana, E. K. Budiardjo, K. Mahatma, and A. Hidayati, “Evaluation of Scrum-Based Software Development Process Maturity using the SMM and AMM: A Case of Education Technology Startup,” 2021 International Conference on Advanced Computer Science and Information Systems, ICACSIS 2021, no. October 2021, 2021, doi: 10.1109/ICACSIS53237.2021.9631308.
P. Leavy, “Research Design: Quantitative, Qualitative, Mixed Methods, Arts-Based, and Community-Based Participatory Research Approaches,” 2017.
J. W. Creswell and J. David Creswell, “Research Design: Qualitative, Quantitative, and Mixed Methods Approaches,” 2018.
A. Yin, S. Figueiredo, and M. da Silva, “Scrum Maturity Model,” Aug. 2011.
A. Hidayati, E. Budiardjo, B. Purwandari, and H. Edison, “MATURITY MODEL OF SCRUM TEAM’S COMPETENCIES IN GLOBAL SOFTWARE DEVELOPMENT.” Sep. 2023. doi: 10.22541/au.168014883.36849555/v1.
M. B. Chrissis, M. Konrad, and S. Shrum, CMMI for Development: Guidelines for Process Integration and Product Improvement, 3rd ed. Addison-Wesley Professional, 2011.
C. Patel and M. Ramachandran, “Agile Maturity Model (AMM) Agile Maturity Model (AMM): A Software Process Improvement framework for Agile Software Development Practices,” 2009.
P. Salant and D. A. Dillman, “How to conduct your own survey,” John Wiley and Sons, 1994.
K. Dikert, M. Paasivaara, and C. Lassenius, “Challenges and success factors for large-scale agile transformations: A systematic literature review,” Journal of Systems and Software, vol. 119, pp. 87–108, Sep. 2016, doi: 10.1016/j.jss.2016.06.013.
F. Almeida and E. Espinheira, “Large-Scale Agile Frameworks: A Comparative Review,” Journal of Applied Sciences, Management and Engineering Technology, vol. 2, pp. 16–29, Aug. 2021, doi: 10.31284/j.jasmet.2021.v2i1.1832.
J. R. Hackman, Leading teams: Setting the stage for great performances. Harvard Business Press, 2002.
Copyright (c) 2024 Jurnal RESTI (Rekayasa Sistem dan Teknologi Informasi)
This work is licensed under a Creative Commons Attribution 4.0 International License.
Copyright in each article belongs to the author
- The author acknowledges that the RESTI Journal (System Engineering and Information Technology) is the first publisher to publish with a license Creative Commons Attribution 4.0 International License.
- Authors can enter writing separately, arrange the non-exclusive distribution of manuscripts that have been published in this journal into other versions (eg sent to the author's institutional repository, publication in a book, etc.), by acknowledging that the manuscript has been published for the first time in the RESTI (Rekayasa Sistem dan Teknologi Informasi) journal ;
