How do software development teams manage technical debt? – An empirical study

Yli-Huumo, Jesse; Maglyas, Andrey; Smolander, Kari

doi:10.1016/j.jss.2016.05.018

Cited by 118 publications

(59 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Other scholars introduced a maturity model for technical debt management, where they identified three levels of awareness in software factories; see for instance [20]. Still, a proposal for a strategic management model is missing.…”

Section: The Technical Debt Trianglementioning

confidence: 99%

The Strategic Technical Debt Management Model: An Empirical Proposal

Ciancarini¹,

Russo²

2020

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Increasing development complexity in software applications raises major concerns about technical debt management, also in Open Source environments. A strategic management perspective provides organizations with an action map to pursue business' targets with limited resources. This article presents the Strategic Technical Debt Management Model (STDMM) to provide practitioners with an actionable roadmap to manage their technical debt properly, considering both social and technical aspects. To do so, we pursued a theoretical mapping, exploiting a set of interviews of 124 carefully selected and well-informed domain experts of the IT financial sector.

show abstract

Section: The Technical Debt Trianglementioning

confidence: 99%

The Strategic Technical Debt Management Model: An Empirical Proposal

Ciancarini¹,

Russo²

2020

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

show abstract

“…However, some similarities remain. Similar to financial debt, strategical, controlled decisions that opt to postpone some tasks to obtain short-term gains such as shortening time-to-delivery can be decisive for a product's success (Yli-Huumo et al 2016).…”

Section: Theoretical Backgroundmentioning

confidence: 99%

“…Those sections follow the structure briefly presented below, for each activity. All activities subsections included a question to obtain which tools or techniques were adopted to conduct that particular activity, based mainly on a list obtained mainly from Li et al (2015) and Yli-Huumo et al (2016).…”

Section: Tdm Activities Sectionsmentioning

confidence: 99%

A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil

Silva

Jeronimo

Travassos

2019

JSERD

View full text Add to dashboard Cite

Technical debt (TD) is receiving more and more attention to software engineering. Although it was initially used as a communication tool for technical and non-technical stakeholders, nowadays this concept supports the improvement of the software’s internal quality. Despite the increasing number of studies regarding TD and its management, only a few are concerned with the industry. Therefore, this primary study aims to characterize TD and its management under the perspective of Brazilian software organizations using their practitioners as proxies. A survey was performed with 62 practitioners, representing around 12 organizations and 30 software projects. The analysis of 40 valid questionnaires indicates that TD is still unknown to a considerable fraction of the participants, and only a small group of organizations adopt TD management activities in their projects. The survey package is available and can be used to support further investigations on TD management in software organizations.

show abstract

“…Other studies have reported the use of TD backlogs (e.g. [6,10,11]). However, existing tools do not use TD cost of refactoring and interest as key parameters.…”

Section: Background Of Anacondebtmentioning

confidence: 99%

“…Also, it is worth understanding when the interest is going to be paid (for example in a few months or many years), to decide when to repay the debt [7]. It is useful to understand where in the system the issues are, and what Technical Debt items are related to each other [5,11]. However, tool support for such analysis is missing at the moment.…”

Section: Introductionmentioning

confidence: 99%

Anacondebt

Martini

2018

Proceedings of the 2018 International Conference on Technical Debt

View full text Add to dashboard Cite

It is challenging to assess and manage Technical Debt. Technical Debt is avoided or refactored if the long-term benefits, such as preventing extra-costs, exceed the cost of repaying the debt.Some tools have been recently proposed for the identification of Technical Debt, but most of them do not help in assessing the cost-benefits of repaying the Debt. Besides, it is challenging to track, visualize and plan Technical Debt refactoring systematically. Although practitioners might use simple tracking tools, calculating and communicating Technical Debt is currently not supported.Based on the results of previous research, combined with several practical experiences in collaboration with large software companies, we have developed and evaluated a lightweight tool, AnaCon-Debt, to track and assess Technical Debt.

show abstract

How do software development teams manage technical debt? – An empirical study

Cited by 118 publications

References 22 publications

The Strategic Technical Debt Management Model: An Empirical Proposal

The Strategic Technical Debt Management Model: An Empirical Proposal

A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil

Anacondebt

Contact Info

Product

Resources

About