Context. Technical debt (TD) prevention allows software practitioners to apply practices to
avoid potential TD items in their projects. Aims. To uncover and prioritize, from the point of …

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 …

Poor design choices, bad coding practices, or the need to produce software quickly can
stand behind technical debt. Unfortunately, manually identifying and managing technical …

Context: Technical debt (TD) payment refers to the activity of expending maintenance effort
and resources to make up for the effects of previous technical compromises. Aims: To …

Background: The concept of technical debt (TD) describes a phenomenon that impacts
software projects and makes them difficult to manage. In recent years, various techniques …

Background. Software engineering is one of the engineering fields with the highest inflow of
junior engineers. Tools that utilize source code analysis to provide feedback on internal …

Scaling agile approaches in large company context is prone to technical debt due to large
number of teams of different size, level of expertise and their need for management and …

The rapid development of information technologies and the increase in client demands in
the sphere of software product production create motivation for the development and …

Technical debt (TD) poses a significant risk in the software industry, representing the
compromises made during software development that result in long-term consequences. To …

Technical Debt (TD) is a metaphor reflecting technical compromises that can yield short-term
benefits but might hurt the long-term health of a software system. Although several research …