Abstract Large Software Companies need to support the continuous and fast delivery of
customer value in both the short and long term. However, this can be impeded if the …

In software engineering, technical debt (TD) has been widely investigated, but debt
regarding social issues, people, and processes has not been explored as much. It should be …

CONTEXT: Whilst technical debt is considered to be detrimental to the long term success of
software development, it appears to be poorly understood in academic literature. The …

Technical debt is a metaphor introduced by Cunningham to indicate" not quite right code
which we postpone making it right". Examples of technical debt are code smells and bug …

An interview study involving 35 practitioners from a variety of domains aimed to characterize
technical debt at the ground level to find out how software practitioners perceive it. The study …

Technical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions
to gain short-term benefit in time-to-market and earlier software release. In this study, one …

Practices designed to expedite the delivery of stakeholder value can paradoxically lead to
unexpected rework costs that ultimately degrade the flow of value over time. This is …

Tough time-to-market constraints and unanticipated integration or evolution issues lead to
design tradeoffs that usually cause flaws in the structure of a software system. Thus …

Technical debt is the consequence of trade-offs made during software development to
ensure speedy releases. The research community lacks rigorously evaluated guidelines to …

Technical debt refers to the phenomena of taking shortcuts to achieve short term gain at the
cost of higher maintenance efforts in the future. Recently, approaches were developed to …