Technical debt is a metaphor which is used to characterize the compromise between short-term benefit and long-term health of a software system. Technical debt is created when software engineers knowingly or unknowingly introduce shortcuts in the development or maintenance of the software system. Therefore, it is crucial to manage the established debt. The aim of this paper is to establish an outline of what we know about Technical Debt Management, the methods applied to gain this knowledge and what we need to know from future studies. This is accomplished through a systematic literature review, which focuses on the concept technical debt management. We identify and analyze 31 papers, which were published from 2017 to April 2019. Our primary analytical focus is on the research approach and setting of the data collection. We identify several gaps in the existing literature: an absence of theory explaining the relation of events, a lack of techniques, such as observation, thus study actual technical debt management behavior, and the unavailability of studies conducted in the public sector. Finally, we offer suggestions for how these gaps can be addressed.
|Publikationsdato||29 jan. 2020|
|Status||Udgivet - 29 jan. 2020|
|Begivenhed||Scandinavian Workshop on E-government - Gothenburg University, Gothenburg, Sverige|
Varighed: 29 jan. 2020 → 30 jan. 2020
|Workshop||Scandinavian Workshop on E-government|
|Periode||29/01/2020 → 30/01/2020|