Context: Technical debt (TD) refers to non-optimal decisions made in software projects that
may lead to short-term benefits, but potentially harm the system's maintenance in the long …

In software engineering, organizational debt (OD) is a crucial but little-researched
phenomena. OD refers to the accumulation of outdated structures, policies, and processes …

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 …

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 …

Context: Architectural decisions are considered one of the most common sources of
technical debt (TD). Thus, it is necessary to understand how TD is perceived by software …

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 term technical debt (TD) describes the aggregation of sub-optimal solutions
that serve to impede the evolution and maintenance of a system. Some claim that the broken …

Context: Repaying all technical debt (TD) in a system may be unviable, as there is typically a
shortage of resources allocated for TD repayment activities. Therefore, TD prioritization is …

Technical debt (TD) is a term coined by agile software pioneer Ward Cunningham to
account for the added software system effort or cost resulting from taking early software …

The development of software and systems is a complex task that involves social, technical
and organisational factors. Technical debt is a well-known concept that refers to the negative …