IMPLEMENTING CONTINUOUS CODE QUALITY FOR CODE QUALITY DEVELOPMENT IN THE SCRUM TEAM

Ilham Izzul Hadyan
Dana Sulistyo Kusumo
Jati Hiliamsyah Husen


DOI: https://doi.org/10.29100/jipi.v7i3.3066

Abstract


There are challenges and drawbacks that will be faced in implementing a Scrum method. One of the problems is in Code Quality because the team only has a short time in each sprint. This causes the team to not be able to conduct a thorough code review, resulting in the team having to increase their workload and pressure. Code review is necessary to identify defects in the code before it goes into the core of the project. But the cumbersome, time-consuming and labor-intensive nature of code review causes a barrier in adopting code review practices properly. To simplify and speed up code review, the researcher will try to implement Continuous Code Quality (CCQ) with the Scrum process by conducting empirical experiments. By examining the effect on the speed of the process and knowing the point of view of the development team. Based on the experiments conducted, the CCQ automation system helps the development team in speeding up the code review process and maintaining good code quality. The biggest influence on the speed of the process remains in the complexity of the system built in a running sprint. Even with an automated code review system, a manual code review process is still needed to ensure there are no errors that cannot be detected by the automated system.

Keywords


Automation; Agile; Code Review; Code Quality

Full Text:

PDF

Article Metrics :

References


W. Mahmood, N. Usmani, M. Ali, and S. Farooqui, Benefits to organizations after migrating to Scrum, Proc. 29th Int. Bus. Inf. Manag. Assoc. Conf. - Educ. Excell. Innov. Manag. through Vis. 2020 From Reg. Dev. Sustain. to Glob. Econ. Growth, no. May, pp. 38153828, 2017.

M. Mahalakshmi and M. Sundararajan, Traditional SDLC Vs Scrum Methodology A Comparative Study, Int. J. Emerg. Technol. Adv. Eng., vol. 3, no. 6, pp. 26, 2013.

R. Akif and H. Majeed, Issues and Challenges in Scrum Implementation, Int. J. Sci. Eng. Res., vol. 3, no. 8, pp. 14, 2012, [Online]. Available: http://www.ijser.org/researchpaper%5CIssues-and-Challenges-in-Scrum-Implementation.pdf.

P. Adi, Scrum Method Implementation in a Software Development Project Management, Int. J. Adv. Comput. Sci. Appl., vol. 6, no. 9, pp. 198204, 2015, doi: 10.14569/ijacsa.2015.060927.

M. Beller, A. Bacchelli, A. Zaidman, and E. Juergens, Modern code reviews in open-source projects: Which problems do they fix?, 11th Work. Conf. Min. Softw. Repos. MSR 2014 - Proc., pp. 202211, 2014, doi: 10.1145/2597073.2597082.

V. Balachandran, Reducing human effort and improving quality in peer code reviews using automatic static analysis and reviewer recommendation, Proc. - Int. Conf. Softw. Eng., pp. 931940, 2013, doi: 10.1109/ICSE.2013.6606642.

C. Vassallo, A. Bacchelli, F. Palomba, and H. C. Gall, Continuous code quality: Are we (really) doing that?, ASE 2018 - Proc. 33rd ACM/IEEE Int. Conf. Autom. Softw. Eng., pp. 790795, 2018, doi: 10.1145/3238147.3240729.

R. Plsch, H. Gruber, C. Krner, and M. Saft, A method for continuous code quality management using static analysis, Proc. - 7th Int. Conf. Qual. Inf. Commun. Technol. QUATIC 2010, pp. 370375, 2010, doi: 10.1109/QUATIC.2010.68.

M. Topan and X. B. N. Najoan, Perancangan Sistem Informasi Manajemen Rumah sakit berbasis web, J. Tek. Inform., vol. 6, no. 1, pp. 16, 2015, doi: 10.35793/jti.6.1.2015.9968.

K. Schwaber and J. Sutherland, Scrum Guide V7, no. November, pp. 133152, 2015.

C. Sadowski, E. Sderberg, L. Church, M. Sipko, and A. Bacchelli, Modern code review: A case study at google, Proc. - Int. Conf. Softw. Eng., no. May 2018, pp. 181190, 2018, doi: 10.1145/3183519.3183525.

Code Quality and Code Security | SonarQube. https://www.sonarqube.org/ (accessed Oct. 31, 2021).

R. K. Mallidi and M. Sharma, Study on Agile Story Point Estimation Techniques and Challenges, Int. J. Comput. Appl., vol. 174, no. 13, pp. 914, 2021, doi: 10.5120/ijca2021921014.

V. Mahnic and T. Hovelja, On using planning poker for estimating user stories, J. Syst. Softw., vol. 85, no. 9, pp. 20862095, 2012, doi: 10.1016/j.jss.2012.04.005.

V. Mahnic and T. Hovelja, On using planning poker for estimating user stories, J. Syst. Softw., vol. 85, no. 9, pp. 20862095, 2012, doi: 10.1016/j.jss.2012.04.005.

A. Raza, M. Tayyab, D. Shahid, D. Abdullah, and D. Muhammad, Impact of Story Point Estimation on Product using Metrics in Scrum Development Process, Int. J. Adv. Comput. Sci. Appl., vol. 8, no. 4, 2017, doi: 10.14569/ijacsa.2017.080452.

F. Albero Pomar, J. A. Calvo-Manzano, E. Caballero, and M. Arcilla-Cobin, Understanding sprint velocity fluctuations for improved project plans with Scrum: a case study, J. Softw. Evol. Process, vol. 26, no. 9, pp. 776783, 2014, doi: 10.1002/smr.1661.

M. Skjott Linneberg and S. Korsgaard, Coding qualitative data: a synthesis guiding the novice, Qual. Res. J., vol. 19, no. 3, pp. 259270, 2019, doi: 10.1108/QRJ-12-2018-0012.