TY - JOUR
T1 - Prevalence, common causes and effects of technical debt
T2 - Results from a family of surveys with the IT industry
AU - Ramač, Robert
AU - Mandić, Vladimir
AU - Taušan, Nebojša
AU - Rios, Nicolli
AU - Freire, Sávio
AU - Pérez, Boris
AU - Castellanos, Camilo
AU - Correal, Darío
AU - Pacheco, Alexia
AU - Lopez, Gustavo
AU - Izurieta, Clemente
AU - Seaman, Carolyn
AU - Spinola, Rodrigo
N1 - Publisher Copyright:
© 2021 Elsevier Inc.
PY - 2022/2
Y1 - 2022/2
N2 - Context: The technical debt (TD) metaphor describes actions made during various stages of software development that lead to a more costly future regarding system maintenance and evolution. According to recent studies, on average 25% of development effort is spent, i.e. wasted, on TD caused issues in software development organizations. However, further research is needed to investigate the relations between various software development activities and TD. Objective: The objective of this study is twofold. First, to get empirical insight on the understanding and the use of the TD concept in the IT industry. Second, to contribute towards precise conceptualization of the TD concept through analysis of causes and effects. Method: In order to address the research objective a family of surveys was designed as a part of an international initiative that congregates researchers from 12 countries—InsighTD. At country level, national teams ran survey replications with industry practitioners from the respective countries. Results: In total 653 valid responses were collected from 6 countries. Regarding the prevalence of the TD concept 22% of practitioners have only theoretical knowledge about it, and 47% have some practical experiences with TD identification or management. Further analysis indicated that senior practitioners who work in larger organizations, larger teams, and on larger systems are more likely to be experienced with TD management. Time pressure or deadlinewas the single most cited cause of TD. Regarding the effects of TD: delivery delay, low maintainability, and rework were the most cited. Conclusion: InsighTD is the first family of surveys on technical debt in software engineering. It provided a methodological framework that allowed multiple replication teams to conduct research activities and to contribute to a single dataset. Future work will focus on more specific aspects of TD management.
AB - Context: The technical debt (TD) metaphor describes actions made during various stages of software development that lead to a more costly future regarding system maintenance and evolution. According to recent studies, on average 25% of development effort is spent, i.e. wasted, on TD caused issues in software development organizations. However, further research is needed to investigate the relations between various software development activities and TD. Objective: The objective of this study is twofold. First, to get empirical insight on the understanding and the use of the TD concept in the IT industry. Second, to contribute towards precise conceptualization of the TD concept through analysis of causes and effects. Method: In order to address the research objective a family of surveys was designed as a part of an international initiative that congregates researchers from 12 countries—InsighTD. At country level, national teams ran survey replications with industry practitioners from the respective countries. Results: In total 653 valid responses were collected from 6 countries. Regarding the prevalence of the TD concept 22% of practitioners have only theoretical knowledge about it, and 47% have some practical experiences with TD identification or management. Further analysis indicated that senior practitioners who work in larger organizations, larger teams, and on larger systems are more likely to be experienced with TD management. Time pressure or deadlinewas the single most cited cause of TD. Regarding the effects of TD: delivery delay, low maintainability, and rework were the most cited. Conclusion: InsighTD is the first family of surveys on technical debt in software engineering. It provided a methodological framework that allowed multiple replication teams to conduct research activities and to contribute to a single dataset. Future work will focus on more specific aspects of TD management.
KW - Causes of technical debt
KW - Effects of technical debt
KW - InsighTD
KW - Survey
KW - Technical debt
UR - http://www.scopus.com/inward/record.url?scp=85118545933&partnerID=8YFLogxK
UR - https://www.mendeley.com/catalogue/100e8c25-e20c-3311-9f8f-ee479b8408ce/
U2 - 10.1016/j.jss.2021.111114
DO - 10.1016/j.jss.2021.111114
M3 - Article
AN - SCOPUS:85118545933
SN - 0164-1212
VL - 184
JO - Journal of Systems and Software
JF - Journal of Systems and Software
M1 - 111114
ER -