A Domino Effect: Interdependencies among Different Types of Technical Debt

Netta Mäki, Esko Penttinen, Tapani Rinta-Kahila

Research output: Chapter in Book/Report/Conference proceedingConference article in proceedingsScientificpeer-review

1 Citation (Scopus)
20 Downloads (Pure)

Abstract

The paper examines the accrual of technical debt, which represents an increasingly pressing concern for many organizations. To advance understanding of how this debt-accumulation process unfolds, an in-depth case study was conducted with a large manufacturing firm for identifying particular types of technical debt and potential interdependencies among them. The findings point to architecture debt being "the root of all evil" at the case company, setting in motion dynamics that led to the development of other types of technical debt. Scholarship should benefit from this nuanced articulation and illustration of interdependencies across the various types of technical debt.

Original languageEnglish
Title of host publicationProceedings of the 56th Annual Hawaii International Conference on System Sciences
EditorsTung X. Bui
PublisherHawaii International Conference on System Sciences
Pages5949-5958
Number of pages10
ISBN (Electronic)978-0-9981331-6-4
Publication statusPublished - 2023
MoE publication typeA4 Conference publication
EventAnnual Hawaii International Conference on System Sciences - Maui, United States
Duration: 3 Jan 20236 Jan 2023
Conference number: 56

Publication series

NameProceedings of the Annual Hawaii International Conference on System Sciences
Volume2023-January
ISSN (Print)1530-1605

Conference

ConferenceAnnual Hawaii International Conference on System Sciences
Abbreviated titleHICSS
Country/TerritoryUnited States
CityMaui
Period03/01/202306/01/2023

Keywords

  • architectural debt
  • case study
  • legacy systems
  • manufacturing
  • technical debt

Fingerprint

Dive into the research topics of 'A Domino Effect: Interdependencies among Different Types of Technical Debt'. Together they form a unique fingerprint.

Cite this