The Process debt management in software development teams: a systematic review of the literature
DOI:
https://doi.org/10.15665/rp.v24i1.3741Keywords:
Software processes, process optimization, strategies, management, process debt, artifactsAbstract
Process debt refers to the occurrence of deficiencies in the design or infrastructure of suboptimal processes that; although they may be beneficial in the short term, can generate a negative impact in the long term for the stakeholders in the process, for example: cost overruns, delays, team demotivation, among others. Several solutions proposed in the literature were analyzed, including evaluation frameworks, automation tools and predictive models, as well as the challenges inherent to process debt management, such as: lack of standardization, difficulty of identification, among others. The interrelationship between process debt and other types of debt, such as: technical, social and documentation debt, was also noted, highlighting the need for more comprehensive approaches. The findings suggest that further development and empirical validation is required, as well as a concerted effort to align industry practices with emerging theoretical models. This review offers researchers and practitioners the opportunity to recognize artifacts, gaps and
research techniques present, which will allow them to analyze, refine, improve or strengthen their own contributions, as well as deepen those already established.
References
Martini, A., Besker, T., & Bosch, J. (2020). Process Debt: A First Exploration. 2020 27th AsiaPacific Software Engineering Conference (APSEC), 316–325.
https://doi.org/10.1109/APSEC51365.2020.00040
Martini, Antonio and Stray, Viktoria and Besker, Terese and Brede Moe, Nils and Bosch, Jan,
Process Debt: Definition, Risks and Management. 2024 Available at SSRN:
https://ssrn.com/abstract=4328073 or http://dx.doi.org/10.2139/ssrn.4328073
Ahmad, M. O., & Gustavsson, T. (2022). The Pandora’s box of social, process, and people debts
in software engineering. Journal of Software: Evolution and Process, 36.
https://doi.org/10.1002/smr.2516
] Saeeda, H., Ahmad, M. O., & Gustavsson, T. (2024). A Multivocal Literature Review on NonTechnical Debt in Software Development: An Insight into Process, Social, People, Organizational,
and Culture Debt. E-Informatica Software Engineering Journal, 18(1), 240101.
https://doi.org/10.37190/e-Inf240101
B. Kitchenham and S. Charters, “Guidelines for performing Systematic Literature Reviews
in Software Engineering,” 2007. Accessed: May 28, 2022. [Online]. Available:
https://www.researchgate.net/publication/302924724.
Wieringa, R., Maiden, N., Mead, N., & Rolland, C. (2006). Requirements engineering paper
classification and evaluation criteria: a proposal and a discussion. Requirements Engineering, 11(1),
–107. https://doi.org/10.1007/s00766-005-0021-6
Goldschmidt, G., & Matthews, B. (2022). Formulating design research questions: A framework.
Design Studies, 78, 101062. https://doi.org/https://doi.org/10.1016/j.destud.2021.101062
Kitchenham, B., Pearl Brereton, O., Budgen, D., Turner, M., Bailey, J., & Linkman, S. (2009).
Systematic literature reviews in software engineering – A systematic literature review. Information
and Software Technology, 51(1), 7–15. https://doi.org/10.1016/j.infsof.2008.09.009
Dybå, T., & Dingsøyr, T. (2008). Strength of evidence in systematic reviews in software
engineering. Proceedings of the Second ACM-IEEE International Symposium on Empirical Software
Engineering and Measurement, 178–187. https://doi.org/10.1145/1414004.1414034
Yang, L., Zhang, H., Shen, H., Huang, X., Zhou, X., Rong, G., & Shao, D. (2021). Quality
Assessment in Systematic Literature Reviews: A Software Engineering Perspective. Information and
Software Technology, 130, 106397. https://doi.org/https://doi.org/10.1016/j.infsof.2020.106397
Castillo, E., & Vásquez, M. L. (2003). El rigor metodológico en la investigación cualitativa.
Colombia Médica, 34(3), 164–167.
Harzing, A.-W. (2010). The publish or perish book. Tarma Software Research Pty Limited
Melbourne, Australia.
Wohlin, C. (2014). Guidelines for snowballing in systematic literature studies and a replication
in software engineering. Proceedings of the 18th International Conference on Evaluation and
Assessment in Software Engineering, 1–10.
Freire, S., Rios, N., Mendonça, M., Falessi, D., Seaman, C., Izurieta, C., & Spínola, R. O. (2020).
Actions and impediments for technical debt prevention: results from a global family of industrial
surveys. Proceedings of the 35th Annual ACM Symposium on Applied Computing, 1548–1555.
https://doi.org/10.1145/3341105.3373912
Rios, N., Oliveira Spinola, R., de Mendonça Neto, M. G., & Seaman, C. (2018). A Study of
Factors that Lead Development Teams to Incur Technical Debt in Software Projects. 2018 44th
Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 429–436.
https://doi.org/10.1109/SEAA.2018.00076
Saeeda, H., Ahmad, M. O., & Gustavsson, T. (2024). Exploring Process Debt in Large-Scale
Agile Software Development For Secure Telecom Solutions. Proceedings of the 7th ACM/IEEE
International Conference on Technical Debt, 11–20. https://doi.org/10.1145/3644384.3644470
Saeeda, H., Ahmad, M. O., & Gustavsson, T. (2023). Multivocal Literature Review on NonTechnical Debt in Software Development : An Exploratory Study. Proceedings of the International
Conference on Evaluation of Novel Approaches to Software Engineering, ENASE : , 2023-April, 89–
https://doi.org/10.5220/0011772300003464
García, G. D., Pardo Calvache, C. J., & Rodríguez, F. J. Á. (2022). Society 5.0 and Soft Skills in
Agile Global Software Development. IEEE Revista Iberoamericana de Tecnologias Del Aprendizaje,
(2), 197–207. https://doi.org/10.1109/RITA.2022.3166966
Berenguer, C., Borges, A., Freire, S., Rios, N., Tausan, N., Ramac, R., Pérez, B., Castellanos, C.,
Correal, D., Pacheco, A., López, G., Falessi, D., Seaman, C., Mandic, V., Izurieta, C., & Spínola, R.
(2021). Technical Debt is not Only about Code and We Need to be Aware about It. Proceedings of the
XX Brazilian Symposium on Software Quality. https://doi.org/10.1145/3493244.3493285
Dargó, Z. (2019). Technical Debt Management: Definition of a Technical Debt Reduction
Software Engineering Methodology for SMEs. https://api.semanticscholar.org/CorpusID:202233439
Doğan, E., & Tüzün, E. (2022). Towards a taxonomy of code review smells. Information and
Software Technology, 142, 106737. https://doi.org/https://doi.org/10.1016/j.infsof.2021.106737
Kruchten, P., Nord, R. L., Ozkaya, I., & Falessi, D. (2013). Technical debt: towards a crisper
definition report on the 4th international workshop on managing technical debt. SIGSOFT Softw. Eng.
Notes, 38(5), 51–54. https://doi.org/10.1145/2507288.2507326
Alves, N. S. R., Ribeiro, L. F., Caires, V., Mendes, T. S., & Spínola, R. O. (2014). Towards an
Ontology of Terms on Technical Debt. 2014 Sixth International Workshop on Managing Technical
Debt, 1–7. https://doi.org/10.1109/MTD.2014.9
Martini, A., Stray, V., & Moe, N. (2019). Technical-, Social- and Process Debt in Large-Scale
Agile: An Exploratory Case-Study (pp. 112–119). https://doi.org/10.1007/978-3-030-30126-2_14
Poliakov, D. (2015). A systematic mapping study on technical debt definition.
https://api.semanticscholar.org/CorpusID:15260409
Rosser, L. A., & Norton, J. H. (2021). A Systems Perspective on Technical Debt. 2021 IEEE
Aerospace Conference (50100), 1–10. https://doi.org/10.1109/AERO50100.2021.9438359
Zabardast, E., Gonzalez-Huerta, J., Gorschek, T., Šmite, D., Alégroth, E., & Fagerholm, F.
(2023). A taxonomy of assets for the development of software-intensive products and services.
Journal of Systems and Software, 202, 111701.
https://doi.org/https://doi.org/10.1016/j.jss.2023.111701
Ahmad, M. O., & Al-Baik, O. (2024). Beyond Technical Debt Unravelling Organisational Debt
Concept. Proceedings of the 39th ACM/SIGAPP Symposium on Applied Computing, 802–809.
https://doi.org/10.1145/3605098.3635913
Alves, N. S. R., Mendes, T. S., de Mendonça, M. G., Spínola, R. O., Shull, F., & Seaman, C.
(2016). Identification and management of technical debt: A systematic mapping study. Information
and Software Technology, 70, 100–121. https://doi.org/https://doi.org/10.1016/j.infsof.2015.10.008
Lahti, J. R., Tuovinen, A.-P., Mikkonen, T., & Capilla, R. (2022). ScrumBut as an Indicator of
Process Debt. 2022 48th Euromicro Conference on Software Engineering and Advanced Applications
(SEAA), 318–321. https://doi.org/10.1109/SEAA56994.2022.00057
Downloads
Published
Issue
Section
License
Copyright (c) 2026 Braian Alexis Bastidas Diaz, Astrid Carolina Cruz Trochez, César Jesús Pardo Calvache
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
The authors to publish in this journal agree to the following conditions:
- The authors transfer the copyright and give the the journal first publication right of the work registered with Creative Commons Attribution License, which allows third parties to use the published work on the condition of always mentioning the authorship and first publication in this journal.
- The authors may perform other independent and additional contractual arrangements for the non-exclusive distribution of the version of the article published in this issue (E.g., Inclusion in an institutional repository or publication in a book), it must be indicated clearly that the work was first published in this journal.
- It allows and encourages the authors to publish their work online (eg institutional or personal pages) before and during the review and publication process. It can lead to productive exchanges and greater and faster dissemination of the published work (see The Effect of Open Access)
Instructions to fill out Certificate of Originality and Copyright Assignment
- Click here and get the forms of Certificate of Originality and Copyright Assignment .
- In each field to fill out, click and complete the corresponding information.
- Once the fields are filled out, at the end of the form copy your scanned signature or digital signature. Please adjust the size of the signature on the form.
- Finally, you can save them as pdf files and send them through the OJS platform as an attachment.
