Cited by 26Software Engineering Techniques and PracticesInformation Systems Theories and ImplementationOpen Source Software Innovations

The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.

When Prototyping Meets Storytelling: Practices and Malpractices in Innovating Software Firms

Open access
Ciriello, Raffaele Fabio, Richter, Alexander, Schwabe, Gerhard·2017·2017 IEEE/ACM 39th International Conference on Software Engineering: Software Engineering in Practice Track (ICSE-SEIP)

Abstract

Storytelling is an important but often underestimated practice in software engineering. Whereas existing research widely regards storytelling as creating a common understanding between developers and users, we argue that storytelling and prototyping are intertwined practices for innovators to persuade decision makers. Based on a two-year qualitative case study in two innovating software firms, we identify and dialectically examine practices of storytelling and prototyping. Our study implies that storytelling and prototyping should be integrated together into software engineering methods.

Overview

Integrity signals

Registry

Crossref · 10.1109/icse-seip.2017.24

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

  • Prototyping can be used to investigate customer needs, validate and clarify customer requirements and tasks, and thus support a company in designing a solution to address customer problems.

    “Prototyping can be used to investigate customer needs, validate and clarify customer requirements and tasks (Budde and Zullighoven 1990;Ciriello et al. 2017), and thus support a company in designing a solution to address customer problems.”
  • Breadboard prototypes are used to investigate technical aspects and to support system specification and coding.

    “Similarly, breadboard prototypes are used to investigate technical aspects, e.g. in circuit design, and to support system specification and coding (Budde and Zullighoven 1990;Ciriello et al. 2017;Lichter et al. 1994;Lim et al. 2008).”
  • One of the main purposes of prototyping is to validate requirements by testing a solution option with internal and/or external stakeholders for perspectives such as problem-solution fit, product-market fit, technical feasibility, and usability.

    “One of the main purposes of prototyping is to validate requirements by testing a solution option with internal and/or external stakeholders (Ciriello et al. 2017;Tronvoll et al. 2017) for perspectives, such as problem-solution fit, product-market fit, technical feasibility, and usability.”
  • Prototypes can support requirements elicitation by clarifying problems early on.

    “Ciriello et al. note that prototypes can support requirements elicitation by clarifying problems early on (Ciriello et al. 2017).”
  • The use of a live product version as a prototype poses conflicts between the need for quick feedback and a focus on product quality.

    “However, the use of a live product version as a prototype poses conflicts between the need for quick feedback and a focus on product quality (Ciriello et al. 2017).”

Citations

Cites

Flagged first, then by citations

Research works printed but not linked: 47

  1. rosson, 2002, Usability Engineering Scenario-Based Development of Human-Computer Interaction
  2. clausen, 1994, Designing Computer Systems from a Human Perspective: The Use of Narratives, Scand J Inf Syst, 6
  3. 10.1109/MS.2013.59 · DOI
  4. 10.1145/381641.381653 · DOI
  5. oaks, 1995, Storytelling a natural mnemonic
  6. schreyögg, 2005, Knowledge management and narratives: Organizational effectiveness through storytelling, Erich Schmidt Verlag GmbH
  7. wende, 0, Exploring Storytelling as a Knowledge Transfer Technique in Offshore Outsourcing, ICIS 2014 Proceedings
  8. 10.1080/07421222.2001.11045668 · DOI
  9. meyer, 2005, A narrative approach to knowledge exchange an empirical investigation in two contrasting settings
  10. hayne, 2009, Using Storytelling to Enhance Information Systems Knowledge Transfer, LAS VEGAS
  11. lichter, 0, Prototyping in industrial software projects, Proc ICSE 1993, 221
  12. urban, 1992, Software Prototyping and Requirements Engineering, Rome Laboratory
  13. 10.4135/9781412984249 · DOI · Paper page
  14. schneider, 0, Prototypes as assets, not toys, Proc ICSE 1996, 522
  15. 10.1145/1375761.1375762 · DOI · Paper page
  16. 10.1016/B978-044481862-1.50082-0 · DOI
  17. 10.1145/572020.572032 · DOI
  18. ciriello, 0, Communicating Ideas Purposefully - Toward a Design Theory of Innovation Artifacts, ECIS2014 Proc
  19. 10.2307/2393701 · DOI · Paper page
  20. partridge, 1991, Origins: A short etymological dictionary of modern English, Routledge
  21. desouza, 2011, Intrapreneurship managing ideas within your organization
  22. 10.1109/TSE.2002.1033222 · DOI
  23. 10.1145/67450.67499 · DOI
  24. overmyer, 1991, Revolutionary vs. evolutionary rapid prototyping: balancing software productivity and HCI design concerns, Cent Excell Command Control Commun Intell C3I George Mason Univ, 4400
  25. blank, 2013, Why the lean start-up changes everything, Harv Bus Rev, 91, 63
  26. 10.1111/j.1948-7169.2001.tb00551.x · DOI
  27. 10.1016/0737-6782(85)90007-4 · DOI
  28. 10.1109/CMPEUR.1990.113653 · DOI
  29. 10.1007/978-3-8349-8390-9 · DOI
  30. carleton, 0, The power of prototypes in foresight engineering, ICED 09
  31. 10.1109/TSE.1986.6312940 · DOI
  32. 10.1109/ICSE.1996.493447 · DOI
  33. hickey, 1998, Prototyping for requirements elicitation and validation, Proc AMC 1998, 268
  34. yanow, 2013, Interpretation and method: Empirical research methods and the interpretive turn, ME Sharpe
  35. ciriello, 2015, Idea Hubs as Nexus of Collective Creativity in Digital Innovation, Proceedings of ICIAS2015
  36. vom brocke, 2009, Reconstructing the giant: On the importance of rigour in documenting the literature search process, ECIS 2009 Proceedings
  37. beck, 2001, Manifesto for Agile Software Development
  38. holmlid, 2007, Prototyping and enacting services: Lessons learned from human-centered methods, Proceedings from the 10th Quality in Services conference QUIS, 10
  39. ciriello, 0, PowerPoint Use and Misuse in Digital Innovation, ECIS2015 Proceedings
  40. schatzki, 2001, The Practice Turn in Contemporary Theory
  41. 10.2307/249410 · DOI · Paper page
  42. 10.1145/223500.223514 · DOI · Paper page
  43. 10.1007/978-3-642-69796-8_1 · DOI
  44. 10.1177/1525822X10388468 · DOI · Paper page
  45. schlachtbauer, 2013, Do Prototypes Hamper Innovative Behavior in Developing IT-based Services?, ICIS2013 Proceedings
  46. silverman, 2006, Interpreting qualitative data: Methods for analyzing talk, text and interaction, Sage
  47. 10.1109/52.156899 · DOI

Cited by

Sorted by citations

Metadata

Authors
Ciriello, R. F., Richter, A., & Schwabe, G.
Affiliations
University of Zurich (CH)
Venue
2017 IEEE/ACM 39th International Conference on Software Engineering: Software Engineering in Practice Track (ICSE-SEIP)
Publisher
IEEE
Published
2017-05
Pages
163-172
OpenAlex
W2728705211
Cited by
26
References
1
Citations by year
2026: 2 · 2025: 2 · 2024: 4 · 2023: 3 · 2022: 5 · 2021: 5 · 2020: 1 · 2019: 1 · 2018: 2 · 2017: 1
FWCI
0.90
Type
conference paper
Language
en
Open access
Licence
other-oa
Locations
  • IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) (publishedVersion)
  • IT University Of Copenhagen (IT University of Copenhagen) (publishedVersion, other-oa)
  • Zurich Open Repository and Archive (University of Zurich) (acceptedVersion, other-oa)
  • Zurich Open Repository and Archive (University of Zurich) (submittedVersion, other-oa)
  • Zurich Open Repository and Archive (University of Zurich)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Information Systems Theories and Implementation
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
Keywords
storytelling, prototype development, software innovation, software companies, software engineering methods, innovation practices

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