TY - GEN
T1 - SCRUM Framework Extended with Clean Architecture Practices for Software Maintainability
AU - Arango, Eduardo C.
AU - Loaiza, Omar L.
N1 - Publisher Copyright:
© 2021, The Author(s), under exclusive license to Springer Nature Switzerland AG.
PY - 2021
Y1 - 2021
N2 - This study consisted of the extension of the Scrum framework with Clean Architecture practices (Scrum-CA) to improve software maintainability. Methodologically, in this study: i) the requirements that Scrum-CA had to satisfy were identified; ii) identification of Scrum aspects (artifacts and/or activities) to be extended, iii) specify the extended framework; and, iv) validate the proposal through a pilot project. At the extended framework level, this proposal considers the formulation of a business context as an input to the Product Backlog. The specification of tasks in the Sprint backlog diversifies them into 4 spaces (infrastructure, controllers, application and domain) so that in the development of the Sprint the achievement of a maintainable architecture is allowed, an issue that Scrum teams must define empirically a priori. SOLID principles are added in the implementation of the product within the Sprints and coherence is maintained between the planning of the requirements and the achievement of the product architecture. Scrum-CA was validated through an implementation project in a Peruvian State entity nationwide. The results show an improvement in the maintainability of the project software, from Sprint1 to Sprint2, reducing code duplication from 4.8% to 3.5%, from 31 duplicated blocks to 9, a technical debt from 6.3% to 1.3%. Also, it is necessary to repeat Scrum-CA in other projects to generate a standard.
AB - This study consisted of the extension of the Scrum framework with Clean Architecture practices (Scrum-CA) to improve software maintainability. Methodologically, in this study: i) the requirements that Scrum-CA had to satisfy were identified; ii) identification of Scrum aspects (artifacts and/or activities) to be extended, iii) specify the extended framework; and, iv) validate the proposal through a pilot project. At the extended framework level, this proposal considers the formulation of a business context as an input to the Product Backlog. The specification of tasks in the Sprint backlog diversifies them into 4 spaces (infrastructure, controllers, application and domain) so that in the development of the Sprint the achievement of a maintainable architecture is allowed, an issue that Scrum teams must define empirically a priori. SOLID principles are added in the implementation of the product within the Sprints and coherence is maintained between the planning of the requirements and the achievement of the product architecture. Scrum-CA was validated through an implementation project in a Peruvian State entity nationwide. The results show an improvement in the maintainability of the project software, from Sprint1 to Sprint2, reducing code duplication from 4.8% to 3.5%, from 31 duplicated blocks to 9, a technical debt from 6.3% to 1.3%. Also, it is necessary to repeat Scrum-CA in other projects to generate a standard.
KW - Clean architecture
KW - Scrum
KW - Scrum extended
KW - Software maintainability
UR - http://www.scopus.com/inward/record.url?scp=85113402634&partnerID=8YFLogxK
U2 - 10.1007/978-3-030-77442-4_56
DO - 10.1007/978-3-030-77442-4_56
M3 - Conference contribution
AN - SCOPUS:85113402634
SN - 9783030774417
T3 - Lecture Notes in Networks and Systems
SP - 667
EP - 681
BT - Software Engineering and Algorithms - Proceedings of 10th Computer Science On-line Conference, 2021
A2 - Silhavy, Radek
PB - Springer Science and Business Media Deutschland GmbH
T2 - 10th Computer Science Online Conference, CSOC 2021
Y2 - 1 April 2021 through 1 April 2021
ER -