skip to main content
10.1145/3183519.3183539acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

Exploration of technical debt in start-ups

Published: 27 May 2018 Publication History

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.

References

[1]
Alan Agresti. 1996. An introduction to categorical data analysis. Vol. 135. Wiley New York.
[2]
Nicolli SR Alves, Thiago S Mendes, Manoel G de Mendonça, Rodrigo O Spínola, Forrest Shull, and Carolyn Seaman. 2016. Identification and management of technical debt: A systematic mapping study. Information and Software Technology 70 (2016), 100--121.
[3]
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguven Duc, and Pekka Abrahamsson. 2016. How do software startups pivot? empirical results from a multiple case study. In International Conference of Software Business. Springer, 169--176.
[4]
Steve Blank. 2013. Why the Lean Start Up Changes Everything. Harvard Business Review 91, 5 (2013), 64.
[5]
Giardino Carmine, Nicolò Paternoster, Michael Unterkalmsteiner, Tony Gorschek, and Pekka Abrahamsson. 2016. Software Development in Startup Companies: The Greenfield Startup Model. IEEE Transactions on Software Engineering X, September (2016), 233.
[6]
J Cohan. 1988. Statistical power analysis for the behaviour sciences. (1988).
[7]
Mark Crowne. 2002. Why software product startups fail and what to do about it. In Engineering Management Conference. IEEE, Cambridge, UK, 338--343.
[8]
Åsa G Dahlstedt, Lena Karlsson, Anne Persson, J Natt och Dag, and Björn Regnell. 2003. Market-Driven Requirements Engineering Processes for Software Products - a Report on Current Practices. In International Workshop on COTS and Product Software, RECOTS 2003.
[9]
Claudia O. De Melo, Daniela S. Cruzes, Fabio Kon, and Reidar Conradi. 2013. Interpretative case studies on agile team productivity and management. Information and Software Technology 55, 2 (2013), 412--427.
[10]
Carmine Giardino, Sohaib Shahid Bajwa, and Xiaofeng Wang. 2015. Key Challenges in Early-Stage Software Startups. In Agile Processes, in Software Engineering, and Extreme Programming, Vol. 212. 52--63.
[11]
Carmine Giardino, Michael Unterkalmsteiner, Nicolo Paternoster, Tony Gorschek, and Pekka Abrahamsson. 2014. What Do We Know about Software Development in Startups? IEEE Software 31, 5 (sep 2014), 28--32.
[12]
Shelby J Haberman. 1973. The analysis of residuals in cross-classified tables. Biometrics (1973), 205--220.
[13]
Geoffrey Hecht, Omar Benomar, Romain Rouvoy, Naouel Moha, and Laurence Duchien. 2015. Tracking the Software Quality of Android Applications Along Their Evolution (T). In Automated Software Engineering (ASE), 2015 30th IEEE/ACM International Conference on. IEEE, 236--247.
[14]
Adery CA Hope. 1968. A simplified Monte Carlo significance test procedure. Journal of the Royal Statistical Society. Series B (Methodological) (1968), 582--598.
[15]
Clemente Izurieta and James M Bieman. 2013. and rot in evolving software systems. (2013), 289--323.
[16]
Mona Erfani Joorabchi, Ali Mesbah, and Philippe Kruchten. 2013. Real challenges in mobile app development. In Empirical Software Engineering and Measurement, 2013 ACM/IEEE International Symposium on. IEEE, 15--24.
[17]
Eriks Klotins. 2017. Using the case survey method to explore engineering practices in software start-ups. In Proceedings of the 1st International Workshop on Software Engineering for Startups. IEEE Press, 24--26.
[18]
Eriks Klotins, Michael Unterkalmsteiner, and Tony Gorschek. 2015. Software Engineering in Start-up companies : an Exploratory Study of 88 Start-ups. 13, 9 (2015), 1--19.
[19]
E Klotins, M Unterkalmsteiner, and T Gorschek. 2017. Software Engineering Anti-patterns in start-ups. In review by IEEE Software (2017).
[20]
Pavneet Singh Kochhar, Ferdian Thung, Nachiappan Nagappan, Thomas Zimmermann, and David Lo. 2015. Understanding the test automation culture of app developers. In Software Testing, Verification and Validation (ICST), 2015 IEEE 8th International Conference on. IEEE, 1--10.
[21]
Philippe Kruchten, Robert L. Nord, and Ipek Ozkaya. 2012. Technical Debt: From Metaphor. IEEE Software (2012), 18--22.
[22]
R. Larsson. 1993. Case Survey Methodology: Quantitative Analysis of Patterns Across Case Studies. Academy of Management Journal 36, 6 (1993), 1515--1546.
[23]
Zengyang Li, Paris Avgeriou, and Peng Liang. 2015. A systematic mapping study on technical debt and its management. Journal of Systems and Software 101 (2015), 193--220.
[24]
Mika Mantyla, Jari Vanhanen, and Casper Lassenius. 2003. A taxonomy and an initial empirical study of bad smells in code. International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. OCTOBER (2003), 381--384.
[25]
Andreas Metzger and Klaus Pohl. 2014. Software product line engineering and variability management: achievements and challenges. In Proceedings of the on Future of Software Engineering. ACM, 70--84.
[26]
Fabio Palomba, Gabriele Bavota, Massimiliano Di Penta, Rocco Oliveto, and Andrea De Lucia. 2014. Do they really smell bad? A study on developers' perception of bad code smells. Proceedings - 30th International Conference on Software Maintenance and Evolution, ICSME 2014 November 2016 (2014), 101--110.
[27]
Nicolò Paternoster, Carmine Giardino, Michael Unterkalmsteiner, Tony Gorschek, and Pekka Abrahamsson. 2014. Software development in startup companies: A systematic mappingstudy. Information and Software Technology 56, 10 (oct 2014), 1200--1218.
[28]
Kai Petersen, Deepika Badampudi, Syed Shah, Krzysztof Wnuk, Tony Gorschek, Efi Papatheocharous, Jakob Axelsson, Severine Sentilles, Ivica Crnkovic, and Antonio Cicchetti. 2017. Choosing Component Origins for Software Intensive Systems: In-house, COTS, OSS or Outsourcing?-A Case Survey. IEEE Transactions on Software Engineering (2017).
[29]
Inc. PitchBook Data. 2015. European Middle Market Report 2H 2015. (2015).
[30]
Inc. PitchBook Data. 2015. U.S. Middle market report Q4 2015. Technical Report.
[31]
Randall W Rice, CSTE CSQA, and LLC Rice Consulting Solutions. 2003. Surviving the top ten challenges of software test automation. CrossTalk: The Journal of Defense Software Engineering (2003), 26--29.
[32]
Per Runeson, Martin Höst, Austen Rainer, and Björn Regnell. 2012. Case study research in software engineering. John Wiley & Sons, Inc., Hoboken, NJ, USA.
[33]
Bran Selic. 2009. Agile documentation, anyone? IEEE software 26, 6 (2009).
[34]
Dag I K Sjoberg, Aiko Yamashita, Bente C D Anda, Audris Mockus, and Tore Dyba. 2013. Quantifying the effect of code smells on maintenance effort. IEEE Transactions on Software Engineering 39, 8 (2013), 1144--1156.
[35]
Bradley R Staats, Katherine L Milkman, and Craig R Fox. 2012. The team scaling fallacy: Underestimating the declining efficiency of larger teams. Organizational Behavior and Human Decision Processes 118, 2 (2012), 132--142.
[36]
Christoph Johann Stettina and Egbert Kroon. 2013. Is there an agile handover? an empirical study of documentation and project handover practices across agile software teams. In Engineering, Technology and Innovation (ICE) & IEEE International Technology Management Conference, 2013 International Conference on. IEEE, 1--12.
[37]
Stanley M Sutton, E C Cubed, and Mario Andretti. 2000. The Role of Process in a Software Start-up. IEEE Software 17, 4 (2000), 33--39.
[38]
Henri Terho, Sampo Suonsyrjä, Aleksi Karisalo, and Tommi Mikkonen. 2015. Ways to cross the rubicon: pivoting in software startups. In International Conference on Product-Focused Software Process Improvement. Springer, 555--568.
[39]
Edith Tom, Aybüke Aurum, and Richard Vidgen. 2013. An exploration of technical debt. Journal of Systems and Software 86, 6 (jun 2013), 1498--1516.
[40]
Je Voas, Ridgetop Circle, Lora Kassab, and College William. {n. d.}. Using Assertions to Make Untestable Software More Testable Keywords 1 Introduction. 1 ({n. d.}), 1--16.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE-SEIP '18: Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice
May 2018
336 pages
ISBN:9781450356596
DOI:10.1145/3183519
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 27 May 2018

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. software start-ups
  2. technical debt

Qualifiers

  • Research-article

Conference

ICSE '18
Sponsor:

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)42
  • Downloads (Last 6 weeks)13
Reflects downloads up to 01 Jan 2025

Other Metrics

Citations

Cited By

View all

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media