Endre søk
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Exploration of technical debt in start-ups
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
Vise andre og tillknytning
2018 (engelsk)Inngår i: Proceedings - International Conference on Software Engineering, IEEE Computer Society , 2018, s. 75-84Konferansepaper, Publicerat paper (Fagfellevurdert)
Abstract [en]

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. © 2018 ACM.

sted, utgiver, år, opplag, sider
IEEE Computer Society , 2018. s. 75-84
Serie
Proceedings - International Conference on Software Engineering, ISSN 0270-5257
Emneord [en]
Software start-ups, Technical debt, Commerce, Case surveys, Contextual information, Engineering practices, Good engineering practices, Product engineering, Resource shortage, Technical debts, Time to market, Software engineering
HSV kategori
Identifikatorer
URN: urn:nbn:se:bth-16893DOI: 10.1145/3183519.3183539Scopus ID: 2-s2.0-85049673180ISBN: 9781450356596 (tryckt)OAI: oai:DiVA.org:bth-16893DiVA, id: diva2:1239996
Konferanse
40th ACM/IEEE International Conference on Software Engineering: Software Engineering in Practice, ICSE-SEIP 2018; Gothenburg
Tilgjengelig fra: 2018-08-20 Laget: 2018-08-20 Sist oppdatert: 2019-09-26bibliografisk kontrollert
Inngår i avhandling
1. Software Engineering in Start-up Companies
Åpne denne publikasjonen i ny fane eller vindu >>Software Engineering in Start-up Companies
2019 (engelsk)Doktoravhandling, med artikler (Annet vitenskapelig)
Abstract [en]

Start-up companies have emerged as suppliers of innovation and software-intensive products. Small teams, lack of legacy products, experimental nature, and absence of any organizational processes enable start-ups to develop and market new products and services quickly. However, most start-ups fail before delivering any value. Start-up failures can be attributed to market factors, shortcomings in business models, lack of motivation, or self-destruction, among other reasons. However, inadequacies in product engineering precede any market or business-related challenges and could be a significant contributing factor to start-up failures. At the same time, state-of-the-art software engineering (SE) practices are often neglected by start-ups as inadequate. At the beginning of this work, SE in start-ups had attracted very little attention from researchers. Thus, there was no coherent view of SE state-of-practice in start-ups and no starting point for a focused investigation.

 

In this thesis, we explore how start-ups practice SE, what specific SE challenges should be addressed, and what new SE practices are needed to support the engineering of innovative software-intensive products and services.

 

A substantial part of this work is exploratory and aimed to explore SE state-of-practice in start-ups. Our initial findings suggest that start-ups overlook the best SE practices. Teams of a few people working on relatively experimental and straightforward software see no upside of following the best practices. However, late start-ups face substantial challenges as their teams grow, and products become more complex. The key difficulties concern installing adequate SE practices supporting collaboration, coordination of work, and management of accumulated technical debt. To support the evolution of engineering practices in start-ups, we propose the start-up progression model outlining engineering goals, common challenges, and useful practices with regards to the start-up life-cycle phases. Further findings suggest inadequate support for market-driven requirements engineering (MDRE). Specifically, on how to aggregate needs and wishes of a large and loosely defined set of stakeholders who may not be able to articulate their needs and expectations. To address this challenge, we propose a method for the identification and prioritization of data sources and stakeholders in MDRE. Analyzing SE context in start-ups and other organizations developing innovative and market-driven products, we have found many similarities. While start-ups have challenges, they do not appear to be unique. Thus, most start-up challenges can be addressed by transferring the best practices from other engineering contexts.

 

We conclude that there is a little need for start-up specific engineering practices. Best software engineering practices are relevant to address challenges in start-ups. The key engineering challenge in start-ups is the management of the evolution of SE practices to match the growing complexity of the product and the organization. Our work also highlights the need for better MDRE practices to support new market-driven product development in both start-ups and other types of organizations. 

sted, utgiver, år, opplag, sider
Karlskrona: Blekinge Tekniska Högskola, 2019
Serie
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 12
Emneord
start-ups, software engineering, practices, models
HSV kategori
Identifikatorer
urn:nbn:se:bth-18694 (URN)978-91-7295-384-0 (ISBN)
Disputas
2019-12-16, J1516, Campus Grasvik, Karlskrona, 09:00 (engelsk)
Opponent
Veileder
Tilgjengelig fra: 2019-10-21 Laget: 2019-09-26 Sist oppdatert: 2019-11-05bibliografisk kontrollert

Open Access i DiVA

Fulltekst mangler i DiVA

Andre lenker

Forlagets fulltekstScopus

Personposter BETA

Klotins, EriksUnterkalmsteiner, MichaelChatzipetrou, PanagiotaGorschek, Tony

Søk i DiVA

Av forfatter/redaktør
Klotins, EriksUnterkalmsteiner, MichaelChatzipetrou, PanagiotaGorschek, Tony
Av organisasjonen

Søk utenfor DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric

doi
isbn
urn-nbn
Totalt: 106 treff
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf