Papers
Topics
Authors
Recent
Gemini 2.5 Flash
Gemini 2.5 Flash
119 tokens/sec
GPT-4o
56 tokens/sec
Gemini 2.5 Pro Pro
43 tokens/sec
o3 Pro
6 tokens/sec
GPT-4.1 Pro
47 tokens/sec
DeepSeek R1 via Azure Pro
28 tokens/sec
2000 character limit reached

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups (2312.07106v1)

Published 12 Dec 2023 in cs.SE

Abstract: Context: Software start-ups are emerging as suppliers of innovation and software-intensive products. However, traditional software engineering practices are not evaluated in the context, nor adopted to goals and challenges of start-ups. As a result, there is insufficient support for software engineering in the start-up context. Objective: We aim to collect data related to engineering goals, challenges, and practices in start-up companies to ascertain trends and patterns characterizing engineering work in start-ups. Such data allows researchers to understand better how goals and challenges are related to practices. This understanding can then inform future studies aimed at designing solutions addressing those goals and challenges. Besides, these trends and patterns can be useful for practitioners to make more informed decisions in their engineering practice. Method: We use a case survey method to gather first-hand, in-depth experiences from a large sample of software start-ups. We use open coding and cross-case analysis to describe and identify patterns, and corroborate the findings with statistical analysis. Results: We analyze 84 start-up cases and identify 16 goals, 9 challenges, and 16 engineering practices that are common among start-ups. We have mapped these goals, challenges, and practices to start-up life-cycle stages (inception, stabilization, growth, and maturity). Thus, creating the progression model guiding software engineering efforts in start-ups. Conclusions: We conclude that start-ups to a large extent face the same challenges and use the same practices as established companies. However, the primary software engineering challenge in start-ups is to evolve multiple process areas at once, with a little margin for serious errors.

Definition Search Book Streamline Icon: https://streamlinehq.com
References (89)
  1. S. M. Sutton, E. C. Cubed, and M. Andretti, “The Role of Process in a Software Start-up,” IEEE Software, vol. 17, no. 4, pp. 33–39, 2000.
  2. N. Paternoster, C. Giardino, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson, “Software development in startup companies: A systematic mapping study,” Information and Software Technology, vol. 56, no. 10, pp. 1200–1218, oct 2014.
  3. V. Berg, J. Birkeland, A. Nguyen-Duc, I. Pappas, and L. Jaccheri, “Software startup engineering: A systematic mapping study,” Journal of Systems and Software, 2018.
  4. C. Giardino, M. Unterkalmsteiner, N. Paternoster, T. Gorschek, and P. Abrahamsson, “What Do We Know about Software Development in Startups?” IEEE Software, vol. 31, no. 5, pp. 28–32, sep 2014.
  5. R. Baskerville, B. Ramesh, L. Levine, J. Pries-Heje, and S. Slaughter, “Is internet-speed software development different?” IEEE Software, vol. 20, no. November 2015, pp. 70–77, 2003.
  6. M. Crowne, “Why software product startups fail and what to do about it,” in Engineering Management Conference.   Cambridge, UK: IEEE, 2002, pp. 338–343.
  7. G. Carmine, N. Paternoster, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson, “Software Development in Startup Companies: The Greenfield Startup Model,” IEEE Transactions on Software Engineering, vol. X, no. September, p. 233, 2016.
  8. Y. Wijngaarde, D. Paliksha, J. Puls, M. Squarci, and I. Anihimovskaya, “Annual European Venture Capital Report, 2017,” Dealroom.co, Tech. Rep. February, 2018.
  9. C. Giardino, S. S. Bajwa, and X. Wang, “Key Challenges in Early-Stage Software Startups,” in Agile Processes, in Software Engineering, and Extreme Programming, vol. 212, 2015, pp. 52–63.
  10. J. Melegati, A. Goldman, and S. Paulo, “Requirements Engineering in Software Startups : a Grounded Theory approach,” in 2nd International Workshop on Software Startups, Trondheim, Norway, 2016.
  11. C. Gralha, D. Damian, A. I. T. Wasserman, M. Goulão, and J. Araújo, “The evolution of requirements practices in software startups,” pp. 823–833, 2018.
  12. N. Tripathi, E. Klotins, R. Prikladnicki, M. Oivo, L. B. Pompermaier, A. S. Kudakacheril, M. Unterkalmsteiner, K. Liukkunen, and T. Gorschek, “An anatomy of requirements engineering in software startups using multi-vocal literature and case survey,” Journal of Systems and Software, 2018.
  13. E. Klotins, M. Unterkalmsteiner, T. Gorschek, and R. Prikladinicki, “Exploration of Technical Debt in Start-ups,” in International Conference of Software Engineering, 2018.
  14. L. Hokkanen and K. Väänänen-Vainio-Mattila, “Ux work in startups: Current practices and future needs,” in Agile Processes in Software Engineering and Extreme Programming, C. Lassenius, T. Dingsøyr, and M. Paasivaara, Eds.   Cham: Springer International Publishing, 2015, pp. 81–92.
  15. M. Unterkalmsteiner, R. Feldt, and T. Gorschek, “A taxonomy for requirements engineering and software test alignment,” ACM Transactions on …, vol. V, no. 212, pp. 1–39, 2014.
  16. M. Unterkalmsteiner, P. Abrahamsson, X. Wang, A. Nguyen-Duc, S. Shah, S. S. Bajwa, G. H. Baltes, K. Conboy, E. Cullina, D. Dennehy et al., “Software startups–a research agenda,” e-Informatica Software Engineering Journal, vol. 10, no. 1, 2016.
  17. E. Klotins, M. Unterkalmsteiner, and T. Gorschek, “Software-intensive product engineering in start-ups: a taxonomy,” IEEE Software, vol. 35, no. 4, 2018.
  18. K. Petersen, D. Badampudi, S. Shah, K. Wnuk, T. Gorschek, E. Papatheocharous, J. Axelsson, S. Sentilles, I. Crnkovic, and A. Cicchetti, “Choosing Component Origins for Software Intensive Systems: In-house, COTS, OSS or Outsourcing? – A Case Survey,” IEEE Transactions on Software Engineering, vol. 44, no. 2, pp. 237–261, 2017. [Online]. Available: http://ieeexplore.ieee.org/document/7870688/
  19. N. Churchill and V. Lewis, “Five Stages of Small Business Growth,” Harvard Business Review, vol. 61, no. 3, pp. 30–40, 1983.
  20. E. Carmel, “Rapid development in software package startups,” in Proc. 27th Hawaii Int’l Conf. System Sciences, 1994.
  21. Atomico/SLUSH, “The State of European Tech 2017,” Atomico, Tech. Rep., 2017. [Online]. Available: https://2017.stateofeuropeantech.com/
  22. S. Blank, “Embrace failure to start up success.” Nature, vol. 477, no. 7363, p. 133, sep 2011.
  23. E. Klotins, M. Unterkalmsteiner, and T. Gorschek, “Software Engineering Anti-patterns in start-ups,” In review by IEEE Software, 2017.
  24. ——, “Software Engineering Knowledge Areas in Startup Companies : a mapping study,” in Lecture Notes in Business Information Processing.   Springer, 2015, pp. 245–257.
  25. A. Yau and C. Murphy, “Is a Rigorous Agile Methodology the Best Development Strategy for Small Scale Tech Startups?” University of Pennsylvania Department of Computer and Information Science, Tech. Rep., 2013.
  26. D. Leonard-Barton, “Wellsprings of knowledge: Building and sustaining the sources of innovation,” 1995.
  27. L. Hokkanen, K. Kuusinen, and K. Väänänen, “Minimum viable user experience: A framework for supporting product design in startups,” in International Conference on Agile Software Development.   Springer, 2016, pp. 66–78.
  28. S. Blank, “Why the Lean Start Up Changes Everything,” Harvard Business Review, vol. 91, no. 5, p. 64, 2013.
  29. W. S. Junk, “The Dynamic Balance Between Cost, Schedule, Features, and Quality in Software Development Projects,” Computer Science Dept., University of Idaho, vol. SEPM-001, 2000.
  30. S. S. Bajwa, X. Wang, A. N. Duc, and P. Abrahamsson, “How do software startups pivot? empirical results from a multiple case study,” in International Conference of Software Business.   Springer, 2016, pp. 169–176.
  31. R. Larsson, “Case Survey Methodology: Quantitative Analysis of Patterns Across Case Studies.” Academy of Management Journal, vol. 36, no. 6, pp. 1515–1546, 1993.
  32. K. M. Eisenhardt, “Building Theories from Case Study Research,” vol. 14, no. 4, pp. 532–550, 1989.
  33. K. Petersen, D. Badampudi, S. Shah, K. Wnuk, T. Gorschek, E. Papatheocharous, J. Axelsson, S. Sentilles, I. Crnkovic, and A. Cicchetti, “Choosing component origins for software intensive systems: In-house, cots, oss or outsourcing?–a case survey,” IEEE Transactions on Software Engineering, 2017.
  34. D. Kirk and S. G. MacDonell, “Categorising software contexts,” 20th Americas Conference on Information Systems, AMCIS 2014, no. April, 2014.
  35. J. M. Corbin and A. Strauss, “Grounded theory research: Procedures, canons, and evaluative criteria,” Qualitative Sociology, vol. 13, no. 1, pp. 3–21, 1990.
  36. S. J. Haberman, “The analysis of residuals in cross-classified tables,” Biometrics, pp. 205–220, 1973.
  37. A. C. Hope, “A simplified monte carlo significance test procedure,” Journal of the Royal Statistical Society. Series B (Methodological), pp. 582–598, 1968.
  38. J. Cohan, “Statistical power analysis for the behaviour sciences,” 1988.
  39. S. Sheppard, A. Colby, K. Macatangay, and W. Sullivan, “What is engineering practice?” International Journal of Engineering Education, vol. 22, no. 3, p. 429, 2007.
  40. T. Dingsøyr, T. E. Fægri, T. Dybå, B. Haugset, and Y. Lindsjørn, “Team performance in software development: research results versus agile principles,” IEEE Software, vol. 33, no. 4, pp. 106–110, 2016.
  41. M. Shermer, “How the survivor bias distorts reality,” Scientific American, vol. 1, 2014.
  42. T. Chow and D.-B. Cao, “A survey study of critical success factors in agile software projects,” Journal of Systems and Software, vol. 81, no. 6, pp. 961–971, 2008.
  43. D. Politis, “Does prior start-up experience matter for entrepreneurs’ learning? a comparison between novice and habitual entrepreneurs,” Journal of small business and Enterprise Development, vol. 15, no. 3, pp. 472–489, 2008.
  44. J. Kruger and D. Dunning, “Unskilled and unaware of it: How difficulties in recognizing one’s own incompetence lead to inflated self-assessments.” pp. 1121–1134, 1999.
  45. C. Wohlin, D. Šmite, and N. B. Moe, “A general theory of software engineering: Balancing human, social and organizational capitals,” Journal of Systems and Software, vol. 109, pp. 229–242, 2015.
  46. P. Seppänen, K. Liukkunen, and M. Oivo, “Little big team: Acquiring human capital in software startups,” in International Conference on Product-Focused Software Process Improvement.   Springer, 2017, pp. 280–296.
  47. M. S. Krishnan, “The role of team factors in software cost and quality: An empirical analysis,” Information Technology & People, vol. 11, no. 1, pp. 20–35, 1998.
  48. A. Gopal, J. A. Espinosa, S. Gosain, and D. P. Darcy, “Coordination and performance in global software service delivery: The vendor’s perspective,” IEEE Transactions on Engineering Management, vol. 58, no. 4, pp. 772–785, 2011.
  49. B. R. Staats, K. L. Milkman, and C. R. Fox, “The team scaling fallacy: Underestimating the declining efficiency of larger teams,” Organizational Behavior and Human Decision Processes, vol. 118, no. 2, pp. 132–142, 2012.
  50. K. Boies, J. Fiset, and H. Gill, “Communication and trust are key: Unlocking the relationship between leadership and team performance and creativity,” The Leadership Quarterly, vol. 26, no. 6, pp. 1080–1094, 2015.
  51. D. D. Tippett and J. F. Peters, “Team building and project management: How are we doing?”   Project Management Institute, 1995.
  52. A. A. Bubshait and G. Farooq, “Team building and project success,” Cost engineering, vol. 41, no. 7, pp. 34–38, 1999.
  53. I. Hadar, P. Soffer, and K. Kenzi, “The role of domain knowledge in requirements elicitation via interviews: an exploratory study,” Requirements Engineering, vol. 19, no. 2, pp. 143–159, 2014.
  54. M. J. Eppler and O. Sukowski, “Managing team knowledge: core processes, tools and enabling factors,” European Management Journal, vol. 18, no. 3, pp. 334–341, 2000.
  55. A. Cockburn and J. Highsmith, “Agile software development, the people factor,” Computer, vol. 34, no. 11, pp. 131–133, 2001.
  56. Å. G. Dahlstedt, L. Karlsson, A. Persson, J. Natt och Dag, and B. Regnell, “Market-Driven Requirements Engineering Processes for Software Products - a Report on Current Practices,” in International Workshop on COTS and Product Software, RECOTS 2003, 2003.
  57. C. Alves, S. Pereira, and J. Castro, “A study in market-driven requirements engineering,” Workshop em Engenharia de Requisitos WER06, pp. 2–3, 2006.
  58. T. Chow and D.-B. Cao, “A survey study of critical success factors in agile software projects,” Journal of Systems and Software, vol. 81, no. 6, pp. 961–971, jun 2008.
  59. L. Karlsson, Å. G. Dahlstedt, B. Regnell, J. N. och Dag, and A. Persson, “Requirements engineering challenges in market-driven software development–an interview study with practitioners,” Information and Software technology, vol. 49, no. 6, pp. 588–604, 2007.
  60. W. D. Hoyer, R. Chandy, M. Dorotic, M. Krafft, and S. S. Singh, “Consumer cocreation in new product development,” Journal of service research, vol. 13, no. 3, pp. 283–296, 2010.
  61. A. La Rocca, P. Moscatelli, A. Perna, and I. Snehota, “Customer involvement in new product development in b2b: The role of sales,” Industrial Marketing Management, vol. 58, pp. 45–57, 2016.
  62. B. Elliott, “Anything is possible: Managing feature creep in an innovation rich environment,” in Engineering Management Conference, 2007 IEEE International.   IEEE, 2007, pp. 304–307.
  63. H. H. Olsson and J. Bosch, “From opinions to data-driven software r&d: A multi-case study on how to close the’open loop’problem,” in Software Engineering and Advanced Applications (SEAA), 2014 40th EUROMICRO Conference on.   IEEE, 2014, pp. 9–16.
  64. J. D. K. J. M. P. Azoulay, B. Jones, “Research: The average age of a successful startup founder is 45,” Harvard Business Review, Jul 2018.
  65. J. R. F. Dos Santos, A. B. Albuquerque, and P. R. Pinheiro, “Requirements prioritization in market-driven software: A survey based on large numbers of stakeholders and requirements,” in Quality of Information and Communications Technology (QUATIC), 2016 10th International Conference on the.   IEEE, 2016, pp. 67–72.
  66. M. Khurum, T. Gorschek, and M. Wilson, “The software value map—an exhaustive collection of value aspects for the development of software intensive products,” JOURNAL OF SOFTWARE-EVOLUTION AND PROCESS, no. July 2010, pp. 481–491, 2012.
  67. A. S. Cui and F. Wu, “Utilizing customer knowledge in innovation: antecedents and impact of customer involvement on new product performance,” Journal of the academy of marketing science, vol. 44, no. 4, pp. 516–538, 2016.
  68. J. Buchman and C. H. Ekadharmawan, “Barriers to sharing domain knowledge in software development practice in smes,” in Proceedings of the 3rd international workshop on knowledge collaboration in software development (KCSD2009).   Citeseer, 2009, pp. 2–16.
  69. E. Bjarnason, K. Wnuk, and B. Regnell, “Overscoping: Reasons and consequences—a case study on decision making in software product management,” in Software Product Management (IWSPM), 2010 Fourth International Workshop on.   IEEE, 2010, pp. 30–39.
  70. B. Boehm, “Value-based software engineering: reinventing,” SIGSOFT Softw. Eng. Notes, vol. 28, no. 2, pp. 3–, 2003.
  71. H. Alahyari, R. B. Svensson, and T. Gorschek, “A study of value in agile software development organizations,” Journal of Systems and Software, vol. 125, pp. 271–288, 2017.
  72. B. Regnell, R. B. Svensson, and T. Olsson, “Supporting roadmapping of quality requirements,” IEEE Software, vol. 25, pp. 42–47, 2008.
  73. L. Chen, “Continuous delivery: Huge benefits, but challenges too,” IEEE Software, vol. 32, no. 2, pp. 50–54, 2015.
  74. R. Pham, S. Kiesling, L. Singer, and K. Schneider, “Onboarding inexperienced developers: struggles and perceptions regarding automated testing,” Software Quality Journal, vol. 25, no. 4, pp. 1239–1268, 2017.
  75. E. F. Collins et al., “Software test automation practices in agile development environment: An industry experience report,” in Proceedings of the 7th International Workshop on Automation of Software Test.   IEEE Press, 2012, pp. 57–63.
  76. P. Ralph and P. Kelly, “The dimensions of software engineering success,” in Proceedings of the 36th International Conference on Software Engineering.   ACM, 2014, pp. 24–35.
  77. D. Badampudi, C. Wohlin, and K. Petersen, “Software component decision-making: In-house, oss, cots or outsourcing-a systematic literature review,” Journal of Systems and Software, vol. 121, pp. 105–124, 2016.
  78. S. Maranville, “Entrepreneurship in the business curriculum,” Journal of Education for Business, vol. 68, no. 1, pp. 27–31, 1992.
  79. L. Hokkanen and K. Väänänen-Vainio-Mattila, “Ux work in startups: current practices and future needs,” in International Conference on Agile Software Development.   Springer, 2015, pp. 81–92.
  80. C. S. Snyder, “A guide to the project management body of knowledge: Pmbok (®) guide,” Project Management Institute: Newtown Square, PA, USA, 2014.
  81. A. Shahin and M. A. Mahbod, “Prioritization of key performance indicators,” International Journal of Productivity and Performance Management, vol. 56, no. 3, pp. 226–240, 2007.
  82. J. Bosch, H. Olsson, J. Björk, and J. Ljungblad, “The early stage software startup development model: A framework for operationalizing lean principles in software startups,” in Lean Enterprise Software and Systems, 2013, ch. The Early, pp. 1–15.
  83. F. Fagerholm, A. S. Guinea, H. Mäenpää, and J. Münch, “The right model for continuous experimentation,” Journal of Systems and Software, vol. 123, pp. 292–305, 2017.
  84. J. S. Reel, “Critical success factors in software projects,” IEEE software, vol. 16, no. 3, pp. 18–23, 1999.
  85. M. H. N. Nasir and S. Sahibuddin, “Critical success factors for software projects: A comparative study,” Scientific research and essays, vol. 6, no. 10, pp. 2174–2186, 2011.
  86. K. Molokken and M. Jorgensen, “A review of software surveys on software effort estimation,” in Empirical Software Engineering, 2003. ISESE 2003. Proceedings. 2003 International Symposium on.   IEEE, 2003, pp. 223–230.
  87. N. Bocken, “Sustainable venture capital–catalyst for sustainable start-up success?” Journal of Cleaner Production, vol. 108, pp. 647–658, 2015.
  88. A. Suominen, S. Hyrynsalmi, K. Still, and L. Aarikka-stenroos, “Software Start-up failure An exploratory study on the impact of investment,” pp. 55–64, 2017.
  89. T. Dybå, T. Dingsøyr, and N. B. Moe, “Agile project management,” in Software project management in a changing world.   Springer, 2014, pp. 277–300.
User Edit Pencil Streamline Icon: https://streamlinehq.com
Authors (7)
  1. Eriks Klotins (18 papers)
  2. Michael Unterkalmsteiner (73 papers)
  3. Panagiota Chatzipetrou (7 papers)
  4. Tony Gorschek (38 papers)
  5. Rafael Prikladnicki (16 papers)
  6. Nirnaya Tripathi (3 papers)
  7. Leandro Bento Pompermaier (3 papers)
Citations (48)
View on Semantic Scholar

Summary

We haven't generated a summary for this paper yet.

Ai Sparkles Streamline Icon: https://streamlinehq.com Summarize Now