Exploration of technical debt in start-ups
arXiv:2309.12434 · doi:10.1145/3183519.3183539
Abstract
Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precedents, dimensions and outcomes associated with technical debt are prevalent in start-ups. Method: We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups. Results: By analyzing responses from 86 start-up cases we found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing. Furthermore, we found that start-up team size and experience is a leading precedent for accumulating technical debt: larger teams face more challenges in keeping the debt under control. Conclusions: This study highlights the necessity to monitor levels of technical debt and to preemptively introduce practices to keep the debt under control. Adding more people to an already difficult to maintain product could amplify other precedents, such as resource shortages, communication issues and negatively affect decisions pertaining to the use of good engineering practices.
ICSE-SEIP '18: Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice
References in corpus (6)
- Software development in startup companies: A systematic mapping study
- What do we know about software development in startups?
- Software Development in Startup Companies: The Greenfield Startup Model
- Software engineering in start-up companies: An analysis of 88 experience reports
- Software Engineering Antipatterns in Start-Ups
- How Do Software Startups Pivot? Empirical Results from a Multiple Case Study