Cognitive biases exert a significant influence on human thinking and decision-making. In order to identify how they influence the occurrence of architectural technical debt, a series of semi-structured interviews with software architects was performed. The results show which classes of architectural technical debt originate from cognitive biases, and reveal the antecedents of technical debt items (classes) through biases. This way, we analysed how and when cognitive biases lead to the creation of technical debt. We also identified a set of debiasing techniques that can be used in order to prevent the negative influence of cognitive biases. The observations of the role of organisational culture in the avoidance of inadvertent technical debt ...
In software-intensive systems, technical debt is a metaphor encompassing design and implementation c...
Technical debt is a metaphor used to describe technical decisions that can give the company a benefi...
Technical debt is a metaphor referring to the consequences of weak software development. Managing te...
Context: During software development, some architectural design decisions incur technical debt, eith...
Background. Companies frequently try to improve the quality of their software by resolving technical...
Context: Architectural decisions are considered one of the most common sources of technical debt (T...
As digital design rapidly expands the disciplinary knowledge-base of related media, methods, and mod...
Background: In order to survive in today's fast-growing and ever fast-changing business environments...
— The negative consequences of Technical Debt is an area of increasing interest, and more specifical...
Abstract One source of software project challenges and failures is the systematic errors introduced...
This dissertation investigates, i) How cognitive biases (or illusions) may lead to errors in design ...
Nowadays, while software industries are aiming to develop their software continuously, their deliver...
A known problem in large software companies is to balance the prioritization of short-term and long-...
Architectural technical debt (ATD) describes the consequences of intentionally or unintentionally ma...
A known problem in large software companies is to balance the prioritization of short-term with long...
In software-intensive systems, technical debt is a metaphor encompassing design and implementation c...
Technical debt is a metaphor used to describe technical decisions that can give the company a benefi...
Technical debt is a metaphor referring to the consequences of weak software development. Managing te...
Context: During software development, some architectural design decisions incur technical debt, eith...
Background. Companies frequently try to improve the quality of their software by resolving technical...
Context: Architectural decisions are considered one of the most common sources of technical debt (T...
As digital design rapidly expands the disciplinary knowledge-base of related media, methods, and mod...
Background: In order to survive in today's fast-growing and ever fast-changing business environments...
— The negative consequences of Technical Debt is an area of increasing interest, and more specifical...
Abstract One source of software project challenges and failures is the systematic errors introduced...
This dissertation investigates, i) How cognitive biases (or illusions) may lead to errors in design ...
Nowadays, while software industries are aiming to develop their software continuously, their deliver...
A known problem in large software companies is to balance the prioritization of short-term and long-...
Architectural technical debt (ATD) describes the consequences of intentionally or unintentionally ma...
A known problem in large software companies is to balance the prioritization of short-term with long...
In software-intensive systems, technical debt is a metaphor encompassing design and implementation c...
Technical debt is a metaphor used to describe technical decisions that can give the company a benefi...
Technical debt is a metaphor referring to the consequences of weak software development. Managing te...