Tampere University of Technology

TUTCRIS Research Portal

An Empirical Study on Technical Debt in a Finnish SME

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

Standard

An Empirical Study on Technical Debt in a Finnish SME. / Lenarduzzi, Valentina; Orava, Teemu; Systä, Kari; Taibi, Davide.

An Empirical Study on Technical Debt in a Finnish SME. IEEE, 2019. (Edit International Symposium on Empirical Software Engineering and Measurement; Vol. 2019-Septemer).

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

Harvard

Lenarduzzi, V, Orava, T, Systä, K & Taibi, D 2019, An Empirical Study on Technical Debt in a Finnish SME. in An Empirical Study on Technical Debt in a Finnish SME. Edit International Symposium on Empirical Software Engineering and Measurement, vol. 2019-Septemer, IEEE, ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, Porto de Galinhas, Pernambuco, Brazil, 19/09/19.

APA

Lenarduzzi, V., Orava, T., Systä, K., & Taibi, D. (2019). An Empirical Study on Technical Debt in a Finnish SME. In An Empirical Study on Technical Debt in a Finnish SME (Edit International Symposium on Empirical Software Engineering and Measurement; Vol. 2019-Septemer). IEEE.

Vancouver

Lenarduzzi V, Orava T, Systä K, Taibi D. An Empirical Study on Technical Debt in a Finnish SME. In An Empirical Study on Technical Debt in a Finnish SME. IEEE. 2019. (Edit International Symposium on Empirical Software Engineering and Measurement).

Author

Lenarduzzi, Valentina ; Orava, Teemu ; Systä, Kari ; Taibi, Davide. / An Empirical Study on Technical Debt in a Finnish SME. An Empirical Study on Technical Debt in a Finnish SME. IEEE, 2019. (Edit International Symposium on Empirical Software Engineering and Measurement).

Bibtex - Download

@inproceedings{d35f3f6bb59c452e8890602af5b92342,
title = "An Empirical Study on Technical Debt in a Finnish SME",
abstract = "Background. The need to release our products under tough time constraints has required us to take shortcuts during the implementation of our products and to postpone the correct implementation, thereby accumulating Technical Debt. Objective. In this work, we report the experience of a Finnish SME in managing Technical Debt (TD), investigating the most common types of TD they faced in the past, their causes, and their effects. Method. We set up a focus group in the case-company, involving different roles. Results. The results showed that the most significant TD in the company stems from disagreements with the supplier and lack of test automation. Specification and test TD are the most significant types of TD. Budget and time constraints were identified as the most important root causes of TD. Conclusion. TD occurs when time or budget is limited or the amount of work are not understood properly. However, not all postponed activities generated 'debt'. Sometimes the accumulation of TD helped meet deadlines without a major impact, while in other cases the cost for repaying the TD was much higher than the benefits. From this study, we learned that learning, careful estimations, and continuous improvement could be good strategies to mitigate TD These strategies include iterative validation with customers, efficient communication with stakeholders, meta-cognition in estimations, and value orientation in budgeting and scheduling.",
author = "Valentina Lenarduzzi and Teemu Orava and Kari Syst{\"a} and Davide Taibi",
year = "2019",
month = "9",
language = "English",
series = "Edit International Symposium on Empirical Software Engineering and Measurement",
publisher = "IEEE",
booktitle = "An Empirical Study on Technical Debt in a Finnish SME",

}

RIS (suitable for import to EndNote) - Download

TY - GEN

T1 - An Empirical Study on Technical Debt in a Finnish SME

AU - Lenarduzzi, Valentina

AU - Orava, Teemu

AU - Systä, Kari

AU - Taibi, Davide

PY - 2019/9

Y1 - 2019/9

N2 - Background. The need to release our products under tough time constraints has required us to take shortcuts during the implementation of our products and to postpone the correct implementation, thereby accumulating Technical Debt. Objective. In this work, we report the experience of a Finnish SME in managing Technical Debt (TD), investigating the most common types of TD they faced in the past, their causes, and their effects. Method. We set up a focus group in the case-company, involving different roles. Results. The results showed that the most significant TD in the company stems from disagreements with the supplier and lack of test automation. Specification and test TD are the most significant types of TD. Budget and time constraints were identified as the most important root causes of TD. Conclusion. TD occurs when time or budget is limited or the amount of work are not understood properly. However, not all postponed activities generated 'debt'. Sometimes the accumulation of TD helped meet deadlines without a major impact, while in other cases the cost for repaying the TD was much higher than the benefits. From this study, we learned that learning, careful estimations, and continuous improvement could be good strategies to mitigate TD These strategies include iterative validation with customers, efficient communication with stakeholders, meta-cognition in estimations, and value orientation in budgeting and scheduling.

AB - Background. The need to release our products under tough time constraints has required us to take shortcuts during the implementation of our products and to postpone the correct implementation, thereby accumulating Technical Debt. Objective. In this work, we report the experience of a Finnish SME in managing Technical Debt (TD), investigating the most common types of TD they faced in the past, their causes, and their effects. Method. We set up a focus group in the case-company, involving different roles. Results. The results showed that the most significant TD in the company stems from disagreements with the supplier and lack of test automation. Specification and test TD are the most significant types of TD. Budget and time constraints were identified as the most important root causes of TD. Conclusion. TD occurs when time or budget is limited or the amount of work are not understood properly. However, not all postponed activities generated 'debt'. Sometimes the accumulation of TD helped meet deadlines without a major impact, while in other cases the cost for repaying the TD was much higher than the benefits. From this study, we learned that learning, careful estimations, and continuous improvement could be good strategies to mitigate TD These strategies include iterative validation with customers, efficient communication with stakeholders, meta-cognition in estimations, and value orientation in budgeting and scheduling.

M3 - Conference contribution

T3 - Edit International Symposium on Empirical Software Engineering and Measurement

BT - An Empirical Study on Technical Debt in a Finnish SME

PB - IEEE

ER -