| 2024 | |
| [1] | , "A Multivocal Literature Review on Non-Technical Debt in Software Development: An Insight into Process, Social, People, Organizational, and Culture Debt", In e-Informatica Software Engineering Journal, vol. 18, no. 1, pp. 240101, 2024.
DOI: 10.37190/e-Inf240101. Download article (PDF)Get article BibTeX file |
Authors
Hina Saeeda, Muhammad Ovais Ahmad, Tomas Gustavsson
Abstract
Software development encompasses various factors beyond technical considerations. Neglecting non-technical elements like individuals, processes, culture, and social and organizational aspects can lead to debt-like characteristics that demand attention. Therefore, we introduce the non-technical debt (NTD) concept to encompass and explore these aspects. This indicates the applicability of the debt analogy to non-technical facets of software development. Technical debt (TD) and NTD share similarities and often arise from risky decision-making processes, impacting both software development professionals and software quality. Overlooking either type of debt can lead to significant implications for software development success. The current study conducts a comprehensive multivocal literature review (MLR) to explore the most recent research on NTD, its causes, and potential mitigation strategies. For analysis, we carefully selected 40 primary studies among 110 records published until October 1, 2022. The study investigates the factors contributing to the accumulation of NTD in software development and proposes strategies to alleviate the adverse effects associated with it. This MLR offers a contemporary overview and identifies prospects for further investigation, making a valuable contribution to the field. The findings of this research highlight that NTD’s impacts extend beyond monetary aspects, setting it apart from TD. Furthermore, the findings reveal that rectifying NTD is more challenging than addressing TD, and its consequences contribute to the accumulation of TD. To avert software project failures, a comprehensive approach that addresses NTD and TD concurrently is crucial. Effective communication and coordination play a vital role in mitigating NTD, and the study proposes utilizing the 3C model as a recommended framework to tackle NTD concerns.
Keywords
Systematic reviews and mapping studies, Software quality
References
1. M.O. Ahmad and T. Gustavsson, “The pandora’s box of social, process, and people debts in software engineering,” Journal of Software: Evolution and Process, 2022, p. e2516.
2. J. Yli-Huumo, The role of technical debt in software development, Ph.D. dissertation, 2017.
3. D.A. Tamburri, P. Kruchten, P. Lago, and H.v. Vliet, “Social debt in software engineering: insights from industry,” Journal of Internet Services and Applications, Vol. 6, 2015, pp. 1–17.
4. Z. Li, P. Avgeriou, and P. Liang, “A systematic mapping study on technical debt and its management,” Journal of Systems and Software, Vol. 101, 2015, pp. 193–220.
5. A. Melo, R. Fagundes, V. Lenarduzzi, and W.B. Santos, “Identification and measurement of requirements technical debt in software development: A systematic literature review,” Journal of Systems and Software, 2022, p. 111483.
6. P. Kruchten, R.L. Nord, and I. Ozkaya, “Technical debt: From metaphor to theory and practice,” Ieee software, Vol. 29, No. 6, 2012, pp. 18–21.
7. A. Martini and J. Bosch, “The danger of architectural technical debt: Contagious debt and vicious circles,” in 2015 12th Working IEEE/IFIP Conference on Software Architecture. IEEE, 2015, pp. 1–10.
8. P. Avgeriou, P. Kruchten, I. Ozkaya, and C. Seaman, “Managing technical debt in software engineering (dagstuhl seminar 16162),” in Dagstuhl reports, Vol. 6, No. 4. Schloss Dagstuhl-Leibniz-Zentrum fuer Informatik, 2016.
9. W. Cunningham, “The wycash portfolio management system,” ACM SIGPLAN OOPS Messenger, Vol. 4, No. 2, 1992, pp. 29–30.
10. N. Rios, R.O. Spínola, M. Mendonça, and C. Seaman, “The most common causes and effects of technical debt: first results from a global family of industrial surveys,” in Proceedings of the 12th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, 2018, pp. 1–10.
11. D.A. Tamburri, “Software architecture social debt: Managing the incommunicability factor,” IEEE Transactions on Computational Social Systems, Vol. 6, No. 1, 2019, pp. 20–37.
12. J. Yli-Huumo, A. Maglyas, and K. Smolander, “How do software development teams manage technical debt?–an empirical study,” Journal of Systems and Software, Vol. 120, 2016, pp. 195–218.
13. A. Chen, “Cultural debt = http://www.address.org/, year = 2022.”
14. T. Klinger, P. Tarr, P. Wagstrom, and C. Williams, “An enterprise perspective on technical debt,” in Proceedings of the 2nd Workshop on managing technical debt, 2011, pp. 35–38.
15. J. Yli-Huumo, A. Maglyas, and K. Smolander, “The effects of software process evolution to technical debt—perceptions from three large software projects,” Managing Software Process Evolution: Traditional, Agile and Beyond–How to Handle Process Change, 2016, pp. 305–327.
16. A. Martini, V. Stray, and N.B. Moe, “Technical-, social-and process debt in large-scale agile: an exploratory case-study,” in Agile Processes in Software Engineering and Extreme Programming–Workshops: XP 2019 Workshops, Montréal, QC, Canada, May 21–25, 2019, Proceedings 20. Springer, 2019, pp. 112–119.
17. Z. Li, P. Liang, and P. Avgeriou, “Architectural debt management in value-oriented architecting,” in Economics-Driven Software Architecture. Elsevier, 2014, pp. 183–204.
18. D. Tamburri, From Technical to Social Debt: Analyzing Software Development Communities using social networks analysis, 2015. [Online]. https://www.slideshare.net/DamianTamburri/from-technical-to-social-debt-analyzing-software-development-communities-using-socialnetworks-analysis
19. T. Mejía, Social Debt the difficult commitment= https://www.socialwatch.org/book/export/html/10623 , 1998
20. D.A. Tamburri and E. Di Nitto, “When software architecture leads to social debt,” in 2015 12th Working IEEE/IFIP Conference on Software Architecture. IEEE, 2015, pp. 61–64.
21. C.B. Jaktman, “The influence of organizational factors on the success and quality of a product-line architecture,” in Proceedings 1998 Australian Software Engineering Conference (Cat. No. 98EX233). IEEE, 1998, pp. 2–11.
22. B. Sutton, “Overcoming cultural and technical debt,” 2019. [Online]. https://sloanreview.mit.edu/audio/overcoming-cultural-and-technical-debt/
23. V. Garousi, M. Felderer, and M.V. Mäntylä, “Guidelines for including grey literature and conducting multivocal literature reviews in software engineering,” Information and software technology, Vol. 106, 2019, pp. 101–121.
24. B. Kitchenham, O.P. Brereton, D. Budgen, M. Turner, J. Bailey et al., “Systematic literature reviews in software engineering–a systematic literature review,” Information and software technology, Vol. 51, No. 1, 2009, pp. 7–15.
25. M.C. Davis, R. Challenger, D.N. Jayewardene, and C.W. Clegg, “Advancing socio-technical systems thinking: A call for bravery,” Applied ergonomics, Vol. 45, No. 2, 2014, pp. 171–180.
26. V. Lenarduzzi, T. Besker, D. Taibi, A. Martini, and F.A. Fontana, “A systematic literature review on technical debt prioritization: Strategies, processes, factors, and tools,” Journal of Systems and Software, Vol. 171, 2021, p. 110827.
27. T. Dybå and T. Dingsøyr, “Empirical studies of agile software development: A systematic review,” Information and software technology, Vol. 50, No. 9-10, 2008, pp. 833–859.
28. V. Braun and V. Clarke, “Using thematic analysis in psychology,” Qualitative research in psychology, Vol. 3, No. 2, 2006, pp. 77–101.
29. L. Mcguire, “What is process debt, and why is it a problem= https://sloanreview.mit.edu/audio/overcoming cultural and technical debt/,” 2022.
30. I. Sommerville, “Software engineering (ed.),” America: Pearson Education Inc, 2011.
31. S.W. Wenger E, McDermott RA, Cultivating Communities of Practice: a Guide to Managing Knowledge. Harvard Business School Publishing, 2002. [Online]. https://hbswk.hbs.edu/archive/cultivating-communities-of-practice-a-guide-to-managing-knowledge-seven-principles-for-cultivating-communities-of-practice
32. C. Bird, N. Nagappan, H. Gall, B. Murphy, and P. Devanbu, “Putting it all together: Using socio-technical networks to predict failures,” in 2009 20th International Symposium on Software Reliability Engineering. IEEE, 2009, pp. 109–119.
33. A. Martini, T. Besker, and J. Bosch, “Process debt: A first exploration,” in 2020 27th Asia-Pacific Software Engineering Conference (APSEC). IEEE, 2020, pp. 316–325.
34. D. Blomstrom, “How to recognise and reduce humandebt =https://www.infoq.com/articles/human-debt,” 2022.
35. P. Vinayak, “Everything you need to know about cultural debt,” https://e2ehiring.com/blogs/everything-you-needto-know-about-cultural-debt,” 2021.
36. M. Bellotti, “Hunting tech debt via org charts. knowing where to look for problems =. https://bellmar.medium.com/hunting-tech-debt-via-org-charts-92df0b253145,” 2021.
37. L. Pirzadeh, “Human factors in software development: A systematic literature review,” 2010.
38. INSEAD, “Company strategic planning — interviews — insead,” 2015.
39. G. Marlow, “People debt is like technical debt – eqsystems.io.” = https://eqsystems.io/2017/04/people-debt-like-technical-debt,” 2017.
40. B. Coleman, Culture Debt Is One of the Most Toxic Threats to Business, and Your Startup Is Probably Victim to It, 2019. [Online]. https://www.inc.com/bernard-coleman/culture-debt-is-one-of-most-toxic-threats-to-business-your-startup-is-probably-victim-to-it.html
41. M. Hosking, Transformation troubles and non-technical debt, 2017. [Online]. https://www.linkedin.com/pulse/transformation-troubles-non-technical-debt-matt-hosking/
42. E.A.C. Espinosa, Understanding Social Debt in Software Engineering, Ph.D. dissertation, The University of Alabama, 2021.
43. T. Dreesen, P. Hennel, C. Rosenkranz, and T. Kude, ““the second vice is lying, the first is running into debt.” antecedents and mitigating practices of social debt: An exploratory study in distributed software development teams,” in Proceedings of the 54th Hawaii International Conference on System Sciences, 2021, p. 6826.
44. J. Trouw, Organisational debt an analogy= https://www.linkedin.com/pulse/organisational debt analogy, 2021. [Online]. https://www.linkedin.com/pulse/organisational-debt-analogy-jaap-trouw
45. S. Blank, “Organizational debt is like technical debt -but worse = https://www.forbes.com/sites/steveblank/2015/05/18/organizational debt is like technical debt but worse-2/?sh=75a9a0787b35,” 2015.
46. S. Priestnall, “What is process debt? = https://www.linkedin.com/pulse/what-process-debt-stevepriestnall.” 2020.
47. J.A. Miko, Collaboration strategies to reduce technical debt, Ph.D. dissertation, Walden University, 2017.
48. M. Eaden, When Testers Deal With Process Debt: Ideas to Manage It And Get Back To Testing Faster, 2017. [Online]. https://www.ministryoftesting.com/articles/8d79968d?s_id=15650023
49. L.P. Gates, “Are we creating organizational debt= https://insights sei cmu.edu/blog/are we creating organizational debt.” 2017.
50. R. Kazman, “Managing social debt in large software projects,” in 2019 IEEE/ACM 7th International Workshop on Software Engineering for Systems-of-Systems (SESoS) and 13th Workshop on Distributed Software Development, Software Ecosystems and Systems-of-Systems (WDES). IEEE, 2019, pp. 1–1.
51. S. Ladewig, “The dark side of working from home — the startup,” 2019. [Online]. https://medium.com/swlh/social-debt-17bf03a269a
52. S. Vinsennau, Decouple To Innovate How Federal agencies can unlock IT value and agility by remediating technical debt, 2016. [Online]. https://www.accenture.com/_acnmedia/PDF-85/Accenture-Decoupling-to-Innovate.pdf
53. B. Falchuk, “What’s the greatest threat to your organization? culture debt = https://bryanfalchuk.com/blog/culture-debt.” 2019.
54. B. Coleman, Culture Debt Is One of the Most Toxic Threats to Business, and Your Startup Is Probably Victim to It, 2019. [Online]. https://www.inc.com/bernard-coleman/culture-debt-is-one-of-most-toxic-threats-to-business-your-startup-is-probably-victim-to-it.html
55. F. Palomba, D.A. Tamburri, F.A. Fontana, R. Oliveto, A. Zaidman et al., “Beyond technical aspects: How do community smells influence the intensity of code smells?” IEEE transactions on software engineering, Vol. 47, No. 1, 2018, pp. 108–129.
56. D. O’Keeffe, “An empirical case study of technical debt management: A software services provider perspective,” 2017.
57. A. Dignan, How to Eliminate Organizational Debt – Building Strong Organizations, 2017. [Online]. https://culturestars.com/how-to-eliminate-organizational-debt
58. N. Nagappan, B. Murphy, and V. Basili, “The influence of organizational structure on software quality: an empirical case study,” in Proceedings of the 30th international conference on Software engineering, 2008, pp. 521–530.
59. J. Cusick and A. Prasad, “A practical management and engineering approach to offshore collaboration,” IEEE software, Vol. 23, No. 5, 2006, pp. 20–29.
60. C.R. De Souza and D.F. Redmiles, “The awareness network, to whom should i display my actions? and, whose actions should i monitor?” IEEE Transactions on Software Engineering, Vol. 37, No. 3, 2011, pp. 325–340.
61. K. Casey, “What causes technical debt – and how to minimize it — the enterprisers project,” 2020. https://enterprisersproject.com/article/2020/6/technical-debt-what-causes,” 2020.
62. L.M. Hilty and B. Aebischer, “Ict for sustainability: An emerging research field,” ICT innovations for Sustainability, 2015, pp. 3–36.