The DOI matches its Crossref record.
Prototyping Practices in Software Startups: Initial Case Study Results
Abstract
Software startups use prototyping to develop and test business ideas and to validate market viability. While prototyping is emphasized in agile methods, there is little research on how startups can best utilise scarce resources to effectively use prototypes in their dynamic business context. We performed a case study of four startups and investigated how startups currently use prototyping to elicit, validate and communicate requirements through semi-structured interviews. Our initial results indicate that prototyping is a commonly applied practice that is implicitly required to obtain funding for early stage startups, that software engineering competence is required to produce interactive and fully functioning prototypes, and that it is a challenge to balance prototype scope against expected gains.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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?
In an earlier publication, prototyping is commonly used within early-stage startups as a natural part of developing and validating a product, but also that prototyping is implicitly required to ensure funding of the startup venture.
“In that study (Bjarnason 2021), we found that prototyping is commonly used within early-stage startups as a natural part of developing and validating a product, but also that prototyping is implicitly required to ensure funding of the startup venture.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
For startups, prototyping plays a vital role in market validation and in obtaining paying customers.
“Thus, for startups, prototyping plays a vital role in market validation and in obtaining paying customers.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Many startups prefer using more refined prototypes instead of prototyping using simpler media such as paper sketches or mock-ups.
“Despite this, our case study found that many startups prefer using these more refined prototypes instead of prototyping using simpler media such as paper sketches or mock-ups.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Internally, prototyping is used to explore and communicate detailed product requirements, while prototypes are used externally to communicate and validate product-market fit.
“Internally, prototyping is used to explore and communicate detailed product requirements, while prototypes are used externally to communicate and validate product-market fit.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Prototyping instances tend to be gradually refined from sketches and interactive mock-ups to fully functioning software versions, often MVPs.
“Prototyping instances tend to be gradually refined from sketches and interactive mock-ups to fully functioning software versions, often MVPs.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
The more refined prototype versions (realistic mock-ups and early versions of production software) are more costly to produce and require software engineering expertise.
“The more refined prototype versions (realistic mock-ups and early versions of production software) are more costly to produce and require software engineering expertise.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Very few startups work with parallel exploration and prototyping, and those who did work with parallel prototypes tended to have a background in usability and human-interaction design.
“In our previous research on the use of prototyping in startups, we found that very few startups work with parallel exploration and prototyping, and that those who did work with parallel prototypes tended to have a background in usability and human-interaction design (Bjarnason 2021).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
For startups, prototypes play a vital role in sales & marketing and in obtaining funding for their venture.
“In addition, for startups prototypes play a vital role in sales & marketing and in obtaining funding for their venture (Bjarnason 2021).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Our previous research indicates that some startups tend to prefer and strive to use source code software for prototyping since they believe this enables them to demonstrate ability and build trust with customers and investors.
“However, our previous research indicates that some startups tend to prefer and strive to use source code software for prototyping since they believe this enables them to demonstrate ability and build trust with customers and investors (Bjarnason 2021).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason 2021
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 18
- unterkalmsteiner, 2016, Software Startups - A Research Agenda, eInformatica Softw Engineering J, 10
- 10.1016/j.jss.2018.06.043 · DOI
- 10.1007/978-3-319-19593-3_22 · DOI
- 10.1016/j.jss.2018.08.059 · DOI · Paper page
- 10.1109/RE48521.2020.00041 · DOI · Paper page
- 10.1109/TSE.2019.2900213 · DOI
- 10.1007/978-3-319-49094-6_42 · DOI · Paper page
- 10.1007/978-3-319-57633-6_2 · DOI
- 10.1145/3475716.3475772 · DOI
- block, 0, Milestones for Successful Venture Planning, Harvard Business Review
- 10.1007/978-3-319-18612-2_5 · DOI · Paper page
- lauesen, 2005, User interface design: a software engineering perspective, Pearson/Addison Wesley
- ries, 2011, The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Currency
- nielsen, 1993, Usability engineering, AP Professional
- 10.1109/MS.2014.129 · DOI · Paper page
- 10.1016/j.infsof.2014.04.014 · DOI · Paper page
- shepherd, 2020, The Lean Startup Framework: Closing the Academic-Practitioner Divide - Dean A. Shepherd, Marc Gruber, Entrepreneurship Theory and Practice
- 10.1002/9781118181034 · DOI
Cited by
Sorted by citations
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
Self-citation
Metadata
- Authors
- Bjarnason, E.
- Affiliations
- Lund University (SE)
- Corresponding author
- Bjarnason, Elizabeth
- ORCID
- Bjarnason, Elizabeth
- Venue
- 2021 IEEE 29th International Requirements Engineering Conference Workshops (REW)
- Publisher
- IEEE
- Published
- 2021-09
- Pages
- 206-211
- OpenAlex
- W3193800164
- Cited by
- 14
- References
- 0
- Citations by year
- 2025: 4 · 2024: 4 · 2023: 5 · 2022: 1
- FWCI
- 1.68
- Type
- conference paper
- Language
- en
- Open access
- closed
- Licence
- Locations
- IEEE International Requirements Engineering Conference Workshops (REW) (publishedVersion)
- Lund University Publications (Lund University) (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Business, Management and Accounting › Strategy and Management › Business Strategies and Innovation
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Keywords
- prototype development, software startups, requirements analysis, requirements validation, requirements communication, agile methods, startup financing, resource constraints
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
