Technical Debt Management in Small and Medium-sized Enterprises
Orava, Teemu (2019)
2019
Tietotekniikan DI-ohjelma - Degree Programme in Information Technology
Informaatioteknologian ja viestinnän tiedekunta - Faculty of Information Technology and Communication Sciences
This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Hyväksymispäivämäärä
2019-11-07
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:tuni-201910043700
https://urn.fi/URN:NBN:fi:tuni-201910043700
Tiivistelmä
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.
In this work, we report the experience of a Finnish SME (Small and Medium-sized Enterprise) in managing Technical Debt (TD), investigating the most common types of TD they faced in the past, their causes, and their effects. The case company is a spin-off which sells one product. Its development was outsourced in the beginning and later continued with external developers.
We set up a focus group in the case-company, involving different roles. 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 potential root causes of TD.
TD occurs when time or budget is limited or the amount and content 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 found out that learning from customers, careful estimations and continuous improvement could be potential strategies to mitigate TD.
These strategies include iterative validation with customers, efficient communication with stakeholders, improvement of meta-cognition in estimations, and value orientation in budgeting and scheduling.
In this work, we report the experience of a Finnish SME (Small and Medium-sized Enterprise) in managing Technical Debt (TD), investigating the most common types of TD they faced in the past, their causes, and their effects. The case company is a spin-off which sells one product. Its development was outsourced in the beginning and later continued with external developers.
We set up a focus group in the case-company, involving different roles. 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 potential root causes of TD.
TD occurs when time or budget is limited or the amount and content 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 found out that learning from customers, careful estimations and continuous improvement could be potential strategies to mitigate TD.
These strategies include iterative validation with customers, efficient communication with stakeholders, improvement of meta-cognition in estimations, and value orientation in budgeting and scheduling.