Please use this identifier to cite or link to this item: https://open.uns.ac.rs/handle/123456789/32433
DC FieldValueLanguage
dc.contributor.authorRamač, Roberten_US
dc.contributor.authorMandić, Vladimiren_US
dc.contributor.authorTaušan, Nebojšaen_US
dc.contributor.authorRios, Nicollien_US
dc.contributor.authorFreire, Sávioen_US
dc.contributor.authorPérez, Borisen_US
dc.contributor.authorCastellanos, Camiloen_US
dc.contributor.authorCorreal, Daríoen_US
dc.contributor.authorPacheco, Alexiaen_US
dc.contributor.authorLopez, Gustavoen_US
dc.contributor.authorIzurieta, Clementeen_US
dc.contributor.authorSeaman, Carolynen_US
dc.contributor.authorSpinola, Rodrigoen_US
dc.date.accessioned2022-01-06T20:44:09Z-
dc.date.available2022-01-06T20:44:09Z-
dc.date.issued2022-
dc.identifier.issn0164-1212en_US
dc.identifier.urihttps://open.uns.ac.rs/handle/123456789/32433-
dc.description.abstractContext: 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.en_US
dc.language.isoen_USen_US
dc.publisherElsevieren_US
dc.relationInsighTD projecten_US
dc.relation.ispartofJournal of Systems and Softwareen_US
dc.subjectTechnical debten_US
dc.subjectSurveyen_US
dc.subjectInsighTDen_US
dc.subjectCauses of technical debten_US
dc.subjectEffects of technical debten_US
dc.titlePrevalence, common causes and effects of technical debt: Results from a family of surveys with the IT industryen_US
dc.typeArticleen_US
dc.identifier.doihttps://doi.org/10.1016/j.jss.2021.111114-
dc.identifier.urlhttps://www.sciencedirect.com/science/article/pii/S0164121221002119-
dc.description.versionPublisheden_US
dc.relation.issue111114en_US
dc.relation.volume184en_US
item.fulltextNo Fulltext-
item.grantfulltextnone-
crisitem.author.deptFakultet tehničkih nauka, Departman za industrijsko inženjerstvo i menadžment-
crisitem.author.orcid0000-0001-6996-2222-
crisitem.author.parentorgFakultet tehničkih nauka-
Appears in Collections:FTN Publikacije/Publications
Show simple item record

Page view(s)

58
Last Week
5
Last month
0
checked on May 10, 2024

Google ScholarTM

Check

Altmetric


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.