DOI : https://doi.org/10.18517/ijaseit.12.6.14934

Mr. Scrum: A Reference Model to Foster and Facilitate the Adoption of Scrum in the Agile Software Development Companies

César Pardo (1), Omar S. Gómez (2), Hamilton Jojoa (3), Ricardo Zambrano (4), Wilson Ortega (5)
(1) University of Cauca, GTI Research Group, Calle 5 # 4, 70, 19001, Popayán, Colombia
(2) Escuela Superior Politécnica de Chimborazo, GrIISoft Research Group, 060155, Riobamba, Ecuador
(3) University of Cauca, GTI Research Group, Calle 5 # 4, 70, 19001, Popayán, Colombia
(4) University of Cauca, GTI Research Group, Calle 5 # 4, 70, 19001, Popayán, Colombia
(5) University of Cauca, GTI Research Group, Calle 5 # 4, 70, 19001, Popayán, Colombia
Fulltext View | Download
How to cite (IJASEIT) :
Pardo, César, et al. “Mr. Scrum: A Reference Model to Foster and Facilitate the Adoption of Scrum in the Agile Software Development Companies”. International Journal on Advanced Science, Engineering and Information Technology, vol. 12, no. 6, Nov. 2022, pp. 2349-55, doi:10.18517/ijaseit.12.6.14934.
Citation Format :
Scrum is one of the most used agile approaches in the software industry. However, some aspects can hinder its implementation, e.g., the lack of detail of artifacts, meetings, generation of the product backlog, and team composition, among others. This paper presents Mr. Scrum, a Scrum reference model obtained from comparing existing Scrum guides and applying the GQM (Goal-Question-Metric) paradigm. Mr. Scrum proposes a clear and complete set of process elements, as well as: purpose, objectives, phases, activities, roles, satisfactory-expected results, and process flows. The proposed model was evaluated through a focus group where its suitability, clarity, and completeness were evaluated. The findings show that the participants agree with the acceptance of the proposed model and that its use in the industry could motivate and facilitate the adoption, implementation, and evaluation of the Scrum implementation. In this sense, Mr. Scrum would allow professionals and organizations to be guided toward a better understanding of Scrum and minimize the subjectivity and error of its interpretation, adoption, and assessment.

H. Takeuchi and I. Nonaka, “The New New Product Development Game,” Harvard Business Review Journal, vol. 64, no. 1, pp. 1-16, 1Jan. 986.

K. Beck and C. Andres, Extreme Programming Explained: Embrace change (2nd Edition). Boston: Addison-Wesley Professional, 2004.

M. Poppendieck and T. Poppendieck, Lean Software Development: An Agile Toolkit. USA: Addison-Wesley Longman Publishing Co., Inc., 2003.

VersionOne Inc. & Collabnet. (2020) 14th Annual State Of Agile Report, 2020. [Online]. Available: https://bit.ly/3hw5ek3.

L. Silvia and A. Raquel, “Caso de estudio sobre apropiación de scrum en empresas que han adoptado CMMI,” in Proc. CIBSE'14, 2014, p. 350.

C. Mann and F. Maurer, “A case study on the impact of scrum on overtime and customer satisfaction,” in Proc. AGILE'05, 2005, p. 70.

A. Marchenko and P. Abrahamsson, “Scrum in a multiproject environment: An ethnographically-inspired case study on the adoption challenges,” in Proc. Agile'08 Conference, 2008, p. 15.

M. Senapathi and A. Srinivasan, “Sustained agile usage: A systematic literature review,” in Proc. EASE'13, 2013, p. 119.

K. Schwaber and J. Sutherland. (2017) The Definitive Guide to Scrum: The Rules of the Game, 2017. [Online]. Available: https://bit.ly/2RHk64q.

J. F. Abrantes and G. H. Travassos, “Towards pertinent characteristics of agility and agile practices for software processes,” Clei Electronic Journal, vol. 16, no. 1, pp. 1-16, Apr. 2013.

D. Norton. (2008) The Current State of Agile Method Adoption. [Online]. Available: https://bit.ly/35tVbID

K. Schwaber, “SCRUM development process,” in Proc. OOPSLA'95, 1995, p. 117.

A. Menzinsky, G. LoÌpez, and J. Palacio, Scrum Manager v2.6. 2016.

T. Satpathy, “A Guide to the Scrum Body of Knowledge,” USA, 2017.

V. R. Basili, G. Caldiera, and H. D. Rombach, “The Goal, metric, and question Approach,” Encyclopedia of Software Engineering, John Wiley & Sons, 1994, vol. 2.

Y. Lin, V. Hilaire, N. Gaud, and A. Koukam, “Scrum Conceptualization Using K-CRIO Ontology,” in Proc. DDPDA'12, 2012, p. 189.

A. Yin, S. Figueiredo, and M. M. da Silva, “Scrum Maturity Model,” in Proc. ICSEA'11, 2011, p. 20.

H. Kniberg. (2020) Scrum checklist version 2.2. [Online]. Available: https://bit.ly/37wiDDC.

R. van Roosmalen, (2020) Excel Scrum Checklist. [Online]. Available: https://bit.ly/2D4MHIH.

J. Kontio, L. Lehtola, and J. Bragge, “Using the focus group method in software engineering: obtaining practitioner and user experiences,” in Proc. ISESE'04, 2004, p. 271.

D.A. Putri, R. Razali, and Z. Mansor, "Team Formation for Agile Software Development: A Review," International Journal on Advanced Science, Engineering and Information Technology, vol. 10, no. 2, pp. 555-561, 2020.

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.

Authors who publish with this journal agree to the following terms:

    1. Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
    2. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
    3. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).