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 …

Code quality remains an abstract concept that fails to get traction at the business level.
Consequently, software companies keep trading code quality for time-to-market and new …

Context Software startups are immature software organizations that focus on the
development of a single software product or service. This organizational context …

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: The technical debt (TD) metaphor helps to conceptualize the pending issues and
trade-offs made during software development. Knowing TD causes can support in defining …

Context: The presence of technical debt (TD) brings risks to software projects. Managers
must continuously find a cost-benefit balance between the benefits of incurring in TD and the …

Context: The adoption of agile methodologies can bring benefits to software projects, but
such methodologies are also prone to technical debt (TD) accumulation. Knowing the …

Context. Technical debt (TD) monitoring allows software professionals to track the evolution
of debt incurred in their projects. The technical literature has listed several practices used in …

Software development teams need to prioritize the technical debt items payment to improve
the software quality and ensure the new feature and code maintenance development pace …

Technical debt is a financial metaphor describing the trade-off between the short-term
benefits gained and long-term consequences of design and implementation shortcuts taken …