How Are Product Ideas Validated?

The Process from Innovation to Requirements Engineering in Software Startups
  • Pertti Seppänen
  • Nirnaya Tripathi
  • Markku Oivo
  • Kari Liukkunen
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 304)


Although software startups are considered important for economic development due to their ability to quickly create cutting-edge technologies and their potential to scale to a wide market, contextual knowledge about the product idea development process of startups is poorly understood in the literature. This study explores the idea validation process of software startups in an attempt to understand the practices used for idea validation, discover how the process is affected by the founder’s prior competencies, and determine the effect of those practices on requirement gathering. We conducted an exploratory multiple case study in nine software startups to determine the kind of practices they used for idea validation. We identified ten practices used as elements of the idea validation process. Our results show that idea validation is a highly non-linear process in which several validation practices are used in varying combinations and timing. The most frequently used practices included copying existing products, prototyping, utilizing expert support, and cooperating closely with customers. The founder’s prior competencies also influenced the selected practices. Copying and prototyping were common practices when the founders had prior competencies in the application area, while utilizing expert support was a widespread practice to compensate for the founder’s missing competencies. We also observed that the idea validation practices identified in the study serve requirement gathering at different levels of abstraction, varying from business-related requirements down to design-level requirements.


Software startup Initial team Idea validation Competency needs Requirement gathering Lean startup Product development Product development process 



This study was partly funded by TEKES as a part of the HILLA program. We thank the members of Software Startups Global Research Network, which supported this study, especially Anh Nguyen Duc and Pekka Abrahamsson, for their help in gathering the empirical data.


  1. 1.
    Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T., Abrahamsson, P.: Software development in startup companies: a systematic mapping study. Inf. Softw. Technol. 56, 1200–1218 (2014)CrossRefGoogle Scholar
  2. 2.
    Blank, S.A.: The four steps to the epiphany: Successful Strategies for Products that Win CafePress. com, (2005)Google Scholar
  3. 3.
    Giardino, C., Unterkalmsteiner, M., Paternoster, N., Gorschek, T., Abrahamsson, P.: What do we know about software development in startups? IEEE Softw. 31, 28–32 (2014)CrossRefGoogle Scholar
  4. 4.
    Giardino, C., Wang, X., Abrahamsson, P.: Why early-stage software startups fail: a behavioral framework. In: Lassenius, C., Smolander, K. (eds.) ICSOB 2014. LNBIP, vol. 182, pp. 27–41. Springer, Cham (2014). doi: 10.1007/978-3-319-08738-2_3 Google Scholar
  5. 5.
    Ries, E.: The lean startup: How today’s entrepreneurs use continuous innovation to create radically successful businesses. Random House LLC (2011)Google Scholar
  6. 6.
    Steinert, M., Leifer, L.J.: “Finding One”s Way’: Re-Discovering a Hunter-Gatherer Model based on Wayfaring. Int. J. Eng. Educ. 28, 251 (2012)Google Scholar
  7. 7.
    Bosch, J., Holmström Olsson, H., Björk, J., Ljungblad, J.: The early stage software startup development model: a framework for operationalizing lean principles in software startups. In: Fitzgerald, B., Conboy, K., Power, K., Valerdi, R., Morgan, L., Stol, K.-J. (eds.) LESS 2013. LNBIP, vol. 167, pp. 1–15. Springer, Heidelberg (2013). doi: 10.1007/978-3-642-44930-7_1 CrossRefGoogle Scholar
  8. 8.
    Coleman, G., O’Connor, R.V.: An investigation into software development process formation in software start-ups. J. Enterp. Inf. Manag. 21, 633–648 (2008)CrossRefGoogle Scholar
  9. 9.
    Crowne, M.: Why software product startups fail and what to do about it. Evolution of software product development in startup companies. In: IEEE International Engineering Management Conference, vol. 1, pp. 338–343 (2002)Google Scholar
  10. 10.
    Björk, J., Ljungblad, J., Bosch, J.: Lean Product development in early stage startups. In: IW-LCSP@ ICSOB. pp. 19–32 (2013)Google Scholar
  11. 11.
    Marmer, M., Herrmann, B.L., Dogrultan, E., Berman, R., Eesley, C., Blank, S.: The startup ecosystem report 2012. Technical report, Startup Genome (2012)Google Scholar
  12. 12.
    Lauesen, S.: Software Requirements: Styles and Techniques. Pearson Education, Upper Saddle River (2002)Google Scholar
  13. 13.
    Seppänen, P., Oivo, M., Liukkunen, K.: The initial team of a software startup, Narrow-shouldered innovation and broad-shouldered implementation. In: To be published in 22nd ICE/IEEE International Technology Management Conference (2016)Google Scholar
  14. 14.
    Runeson, P., Höst, M.: Guidelines for conducting and reporting case study research in software engineering. Empir. Softw. Eng. 14, 131–164 (2009)CrossRefGoogle Scholar
  15. 15.
    Cruzes, D.S., Dyba, T.: Recommended steps for thematic synthesis in software engineering. In: 2011 International Symposium on Empirical Software Engineering and Measurement (ESEM), pp. 275–284. IEEE (2011)Google Scholar
  16. 16.
    Giardino, C., Paternoster, N., Unterkalmsteiner, M., Gorschek, T., Abrahamsson, P.: Software development in startup companies: the greenfield startup model. IEEE Trans. Softw. Eng. 42, 585–604 (2016)CrossRefGoogle Scholar
  17. 17.
    Wang, X., Edison, H., Bajwa, S.S., Giardino, C., Abrahamsson, P.: Key challenges in software startups across life cycle stages. In: Sharp, H., Hall, T. (eds.) XP 2016. LNBIP, vol. 251, pp. 169–182. Springer, Cham (2016). doi: 10.1007/978-3-319-33515-5_14 Google Scholar
  18. 18.
    Klotins, E., Unterkalmsteiner, M., Gorschek, T.: Software engineering knowledge areas in startup companies: a mapping study. In: Fernandes, João M., Machado, Ricardo J., Wnuk, K. (eds.) ICSOB 2015. LNBIP, vol. 210, pp. 245–257. Springer, Cham (2015). doi: 10.1007/978-3-319-19593-3_22 CrossRefGoogle Scholar
  19. 19.
    Selecting empirical methods for software engineering research. In: Shull F., Singer J., Sjøberg D.I.K. (eds.) Guide to Advanced Empirical Software Engineering, pp. 285–311. Springer, London (2008)Google Scholar
  20. 20.
    Marshall, M.N.: The key informant technique. Fam. Pract. 13, 92–97 (1996)CrossRefGoogle Scholar
  21. 21.
    Lethbridge, T.C., Sim, S.E., Singer, J.: Studying software engineers: data collection techniques for software field studies. Empir. Softw. Eng. 10, 311–341 (2005)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Pertti Seppänen
    • 1
  • Nirnaya Tripathi
    • 1
  • Markku Oivo
    • 1
  • Kari Liukkunen
    • 1
  1. 1.M3S/M GroupUniversity of OuluOuluFinland

Personalised recommendations