The DOI matches its Crossref record.
The use of prototypes within agile product development explorative case study of a Makeathon
Open accessAbstract
Due to rapid technology change and increased innovation dynamic, product development is related with high uncertainty and complexity [2]. As a consequence of the shortened product life-cycles, agile development becomes more important. It fosters cross-functional project work and enables a team to react fast and flexible to a continuously changing environment. Central aspect of the agile approach within physical product development is prototyping. This work identifies criteria to analyze the use of physical prototypes within an agile set up. Therefore, a Makeathon has been analyzed. In contrast to plan-driven development, prototypes are used to explore, design, verify, test the usability or communicate product aspects. They support the learning process by providing important insights about the solution space on which the planning of the next iteration is based. The data also support the assumption that there is not “one” approach in agile product development. It is much more likely to be unique to each product, which is also one of the strengths of agile product development, as it allows you to react flexibly to changes.
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?
Usability testing was reported as the least common singular purpose for prototyping though it is often combined with other purposes.
“Usability testing was reported by Zink et al. as the least common singular purpose for prototyping though it is often combined with other purposes (Zink et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Zink et al. 2017
Prototyping can be used to explore a product's business potential from the customer perspective, and to assess the value of the product and likeliness of purchase and the product's ability to fit within time and budget constraints.
“Prototyping can be used to explores a product's business potential from the customer perspective, and to assess the value of the product and likeliness of purchase (McCurdy et al. 2006;Zink et al. 2017) and the product's ability to fit within time and budget constraints (Zink et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Zink et al. 2017
Feasibility testing requires a high share of the time invested in a project.
“Finally, Zink et al. found that feasibility testing requires a high share of the time invested in a project (Zink et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Zink et al. 2017
As the prototype representation of the (future) product becomes more concrete with each iteration, the product requirements thereby gradually become more specific.
“As the prototype representation of the (future) product becomes more concrete with each iteration, the product requirements thereby gradually become more specific (Zink et al. 2017).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Zink et al. 2017
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 27
- smith, 2007, Flexible Product Development Building Agility for Changing Markets
- 10.1115/DETC2016-60225 · DOI
- beaudouin-lafon, 2009, Prototyping tools and techniques, Human-computer Interaction Development Process, 122
- 10.1016/j.jengtecman.2015.09.003 · DOI
- hallgrimsson, 2012, Prototyping and Modelmaking for Product Design
- 10.1007/978-3-642-01423-9 · DOI
- 10.1007/BF03341189 · DOI
- 10.1007/978-3-658-01284-7_5 · DOI
- hallgrimsson, 2012, Prototyping and modelmaking for product design (Portfolio skills)
- jessica, 2016, The Prototype for X (PFX) Framework: Assessing the Impact of PFX on Desirability, Feasibility, and Viability of End Designs, ASME 2016 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference
- 10.1007/BF03160222 · DOI
- möller, 2011, Handbuch Konstruktionswerkstoffe - Auswahl Anwendung Eigenschaften
- oestereich, 2008, Agiles Projektmanagement APM erfolgreiches time-boxing für IT-Projekte
- beck, 0, Manifesto for Agile Software Development
- klein, 2016, Agiles Engineering im Maschinen-und Anlagenbau
- ulrich, 2003, Product Design and Development
- 10.1145/1375761.1375762 · DOI · Paper page
- link, 2014, Agile Methods in a new area of innovtion management, Sciente-To-Business Markting Conference
- 10.1007/978-3-8349-6968-2 · DOI
- 10.1007/978-3-658-01284-7_5 · DOI
- beaudouin-lafon, 2007, Prototyping tools and techniques, Human-Computer Interaction Handbook Fundamentals Evolving Technologies and Emerging Applications, 1017
- gürtler, 2016, Innovationsmanagement, 483
- 10.1016/j.jengtecman.2015.09.003 · DOI
- 10.3139/9783446431621.004 · DOI
- hallgrimsson, 2012, Prototyping and Modelmaking for Product Design
- ulrich, 2008, Product Design and Development
- 10.1177/154193120204600513 · 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
Metadata
- Authors
- Zink, L., Hostetter, R., Bohmer, A. I., Lindemann, U., & Knoll, A.
- Affiliations
- Technical University of Munich (DE)
- ORCID
- Knoll, Alois
- Venue
- 2017 International Conference on Engineering, Technology and Innovation (ICE/ITMC)
- Publisher
- IEEE
- Published
- 2017-06
- Pages
- 68-77
- OpenAlex
- W2787143714
- Cited by
- 15
- References
- 0
- Citations by year
- 2026: 1 · 2024: 1 · 2023: 3 · 2022: 2 · 2021: 1 · 2020: 3 · 2019: 3 · 2018: 1
- FWCI
- 1.26
- Type
- conference paper
- Language
- en
- Open access
- green
- mediatum.ub.tum.de
- Licence
- other-oa
- Locations
- IEEE International Conference on Engineering, Technology and Innovation (ICE/ITMC) (publishedVersion)
- mediaTUM (Technical University of Munich) (submittedVersion, other-oa)
- Funders
- European Commission (720270, HORIZON2020)
- Technische Universität München
- Horizon 2020 Framework Programme (720270)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Business, Management and Accounting › Management of Technology and Innovation › Product Development and Customization
- Physical Sciences › Engineering › Mechanical Engineering › Design Education and Practice
- Keywords
- agile product development, physical prototypes, rapid prototyping, cross-functional teams
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
