A Systematic Review of SCRUM in Software Development

Eduard Wonohardjo - Bina Nusantara University, Jakarta Barat, Indonesia
Rizky Sunaryo - Bina Nusantara University, Jakarta Barat, Indonesia
Yusuf Sudiyono - Bina Nusantara University, Jakarta Barat, Indonesia

Citation Format:

DOI: http://dx.doi.org/10.30630/joiv.3.2.167


Scrum is a part of agile software development which also called incremental software development model. Scrum methodology commonly used to overcome uncertain condition and tight deadline. Scrum consists of three roles, they are product owner, development team, and scrum master. Scrum can be implemented on many areas such as development of education mobile application, integration of document management system, strengthen IT development centers, and many others. The successful of Scrum implementation depends on the skill and knowledge of the team members. The Scrum also has several risk factors and therefore needs risk management approaches. A comparison between agile and waterfall model is also discussed. The Scrum performance can also be tested with certain ways.  Scrum used to make sure that all parts of the software can be delivered on time. The other benefits, scrum can make creative and productive workplace, and scrum can also increase business value.


Agile software development; scrum

Full Text:



J. Schild, R. Walter, and M. Masuch, “ABC-Sprints: adapting Scrum to academic game development courses,†Proc. Fifth Int. Conf. Found. Digit. Games, pp. 187–194, 2010.

A. H. W. Chun, “The Agile Teaching / Learning Methodology and its e-Learning Platform,†Lect. Notes Comput. Sci. - Adv. Web-Based Learn., vol. 3143, pp. 11–18, 2004.

A. Mahdi, M. Hamed, and H. Abushama, “Popular Agile Approaches in Software Development : Review and Analysis,†pp. 160–166, 2013.

R. Takahira, L. Laraia, and F. Dias, “Scrum and Embedded Software development for the automotive industry,†… Eng. …, pp. 2664–2672, 2014.

M. R. Jameel Qureshi and N. Alsulami, “Mitigating Coordination Costs in Global Software Development Using Scrum,†Int. J. Inf. Eng. Electron. Bus., vol. 6, no. 3, pp. 16–21, 2014.

S. Overhage, S. Schlauderer, D. Birkmeier, and J. Miller, “What Makes IT personnel adopt scrum? A framework of drivers and inhibitors to developer acceptance,†Proc. Annu. Hawaii Int. Conf. Syst. Sci., 2011.

C. Orłowski, I. Bach-Dąbrowska, P. Kapłański, and W. Wysocki, “Hybrid fuzzy-ontological project framework of a team work simulation system,†Procedia Comput. Sci., vol. 35, no. C, pp. 1175–1184, 2014.

J. Vlietland and H. Van Vliet, “Towards a governance framework for chains of Scrum teams,†Inf. Softw. Technol., vol. 57, no. 1, pp. 52–65, 2015.

R. Mokhtar, N. H. Jaafar, N. F. Tahar, S. A. Sukiman, A. Aris, and N. F. Abu Bakar, “An integrated document management system for managing self programme accreditation using scrum approach,†ISTMET 2014 - 1st Int. Symp. Technol. Manag. Emerg. Technol. Proc., no. Istmet, pp. 102–106, 2014.

A. Wahid and M. Parvez, “An Efficient Model for Mobile Application Regression Test for Agile Scrum Software Development,†Adv. Comput. Sci. its Appl. vol. 2, pp. 339-344, vol. 2, no. 2, pp. 339–344, 2012.

T. Khalane and M. Tanner, “Software quality assurance in Scrum: The need for concrete guidance on SQA strategies in meeting user expectations,†IEEE Int. Conf. Adapt. Sci. Technol. ICAST, 2013.

S. V. Shrivastava and U. Rathod, “Categorization of risk factors for distributed agile projects,†Inf. Softw. Technol., vol. 58, pp. 373–387, 2015.

S. Al Qurashi and M. R. J. Qureshi, “Scrum of scrums solution for large size teams using scrum methodology,†Life Sci. J., vol. 11, no. 8, pp. 443–449, 2014.

V. T. Heikkilla, M. Paasivaara, K. Rautiainen, C. Lassenius, T. Toivola, and J. Jarvinen, “Operational release planning in large-scale scrum with multiple stakeholders - A longitudinal case study at Fsecure corporation,†Inf. Softw. Technol., vol. 57, no. 1, pp. 116–140, 2015.

S. Alyahya, W. K. Ivins, and W. A. Gray, “Co-ordination support for managing progress of distributed agile projects,†Proc. - 2011 6th IEEE Int. Conf. Glob. Softw. Eng. Work. ICGSE Work. 2011, pp. 31–34, 2011.

N. K. Kamaruddin, N. H. Arshad, and A. Mohamed, “Chaos issues on communication in Agile Global Software Development,†BEIAC 2012 - 2012 IEEE Business, Eng. Ind. Appl. Colloq., pp. 394–398, 2012.

J. M. Bass, “Citation Details Agile Method Tailoring in Distributed Enterprises: Product Owner Teams,†Glob. Softw. Eng. (ICGSE). Bari, 2013.

H.-C. Estler, M. Nordio, C. A. Furia, B. Meyer, and J. Schneider, “Agile vs. Structured Distributed Software Development: A Case Study,†2012 IEEE Seventh Int. Conf. Glob. Softw. Eng., pp. 11–20, 2012.

S. Jalali and C. Wohlin, “Agile practices in global software engineering-A systematic map,†5th IEEE Int. Conf. Glob. Softw. Eng., pp. 45–54, 2010.

R. Noordeloos, C. Manteli, and H. Van Vliet, “From RUP to Scrum in Global Software Development: A Case Study,†2