The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
What Do We Know about Software Development in Startups?
Open accessAbstract
An impressive number of new startups are launched every day as a result of growing new markets, accessible technologies, and venture capital. New ventures such as Facebook, Supercell, Linkedin, Spotify, WhatsApp, and Dropbox, to name a few, are good examples of startups that evolved into successful businesses. However, despite many successful stories, the great majority of them fail prematurely. Operating in a chaotic and rapidly evolving domain conveys new uncharted challenges for startuppers. In this study, the authors characterize their context and identify common software development startup practices.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Software startups typically perform light-weight, informal and ad-hoc requirements engineering, in particular during the early stages of the startup venture due to limited resources.
“Software startups typically perform light-weight, informal and ad-hoc requirements engineering, in particular during the early stages of the startup venture due to limited resources (Giardino et al. 2014;Klotins et al. 2019;Nguyen-Duc et al. 2017;Terho et al. 2016).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Giardino et al. 2014
The section “Software development is driven by customers, who act as designers” says startups define a minimal set of functional requirements while learning the needs of their first customers. “Practical takeaways” describes ad-hoc agile and lean methods, and “Lack of resources” says resources are extremely limited. The paper does not specifically say that requirements engineering is informal or ad hoc because of limited resources, particularly in the venture’s early stages. (LLM, conf=0.84)
Experimental — accuracy not yet measuredThis cost-benefit aspects is especially important to software startups who operate under very uncertain and resource-constraint conditions with the aim of exploring new business opportunities and develop innovative products.
“This cost-benefit aspects is especially important to software startups who operate under very uncertain and resource-constraint conditions with the aim of exploring new business opportunities and develop innovative products (Giardino et al. 2014;Paternoster et al. 2014).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Giardino et al. 2014
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Systematic Mapping Studies in Software Engineering
Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008) · Electronic Workshops in Computing · doi:10.14236/ewic/ease2008.8 · Cited by 3,239 · cited 1×
“Empirical body of evidence (SIDEBAR) A Systematic Mapping Study is a method to structure the empirical evidence in a particular field of interest [5].”
Method
Flagged first, then by citations
Research works printed but not linked: 13
- crowne, 0, Why Software Product Startups Fail and What to Do about It, Proc Int’l Eng Management Conf, 338
- 10.1109/52.854066 · DOI
- 10.1147/sj.423.0462 · DOI
- 10.1109/52.991334 · DOI
- 10.1109/HICSS.1994.323468 · DOI
- 10.1109/IMIS.2012.148 · DOI
- 10.1109/PICMET.2007.4349435 · DOI
- blank, 2013, Why the Lean Start-Up Changes Everything, Harvard Business Rev, 91, 64
- 10.1109/IEMC.2002.1038356 · DOI
- 10.1016/j.infsof.2014.04.014 · DOI · Paper page
- ries, 2011, The Lean Startup How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
- 10.1108/17410390810911221 · DOI
- 10.1007/s10664-010-9146-4 · DOI
Cited by
Sorted by citations
Garousi, V., Felderer, M., & Mäntylä, M. V. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.09.006 · Cited by 831
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
Metadata
- Authors
- Giardino, C., Unterkalmsteiner, M., Paternoster, N., Gorschek, T., & Abrahamsson, P.
- Affiliations
- NTT (Japan) (JP)
- Venue
- IEEE Software
- Published
- 2014-09
- Volume
- 31
- Issue
- 5
- Pages
- 28-32
- ISSN
- 0740-7459 (ISSN-L)
- 1937-4194
- OpenAlex
- W1992410613
- Cited by
- 223
- References
- 1
- Citations by year
- 2026: 18 · 2025: 13 · 2024: 18 · 2023: 21 · 2022: 28 · 2021: 21 · 2020: 25 · 2019: 17 · 2018: 28 · 2017: 15 · 2016: 14 · 2015: 5
- FWCI
- 19.60
- Type
- journal article
- Language
- en
- Open access
- green
- arxiv.org
- Licence
- Locations
- IEEE Software (publishedVersion)
- arXiv (Cornell University) (submittedVersion, cc-by-nc-sa)
- KTH Publication Database DiVA (KTH Royal Institute of Technology) (submittedVersion, other-oa)
- Lund University Publications (Lund University) (submittedVersion)
- Chalmers Publication Library (Chalmers University of Technology) (submittedVersion)
- Chalmers Research (Chalmers University of Technology) (submittedVersion)
- Open Research (University of Surrey) (submittedVersion)
- arXiv (Cornell University)
- IEEE Software
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Keywords
- startups, software development practices, startup failure
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
