Context: Software startups are an essential source of innovation and software-intensive products. The need to understand product development in startups and to provide relevant support are highlighted in software research. While state-of-the-art literature reveals how startups develop their software, the reasons why they adopt these activities are underexplored. Objective: This study investigates the tactics behind software engineering (SE) activities by analyzing key engineering events during startup journeys. We explore how entrepreneurial mindsets may be associated with SE knowledge areas and with each startup case. Method: Our theoretical foundation is based on causation and effectuation models. We conducted semi-structured interviews with 40 software startups. We used two-round open coding and thematic analysis to describe and identify entrepreneurial software development patterns. Additionally, we calculated an effectuation index for each startup case. Results: We identified 621 events merged into 32 codes of entrepreneurial logic in SE from the sample. We found a systemic occurrence of the logic in all areas of SE activities. Minimum Viable Product (MVP), Technical Debt (TD), and Customer Involvement (CI) tend to be associated with effectual logic, while testing activities at different levels are associated with causal logic. The effectuation index revealed that startups are either effectuation-driven or mixed-logics-driven. Conclusions: Software startups fall into two types that differentiate between how traditional SE approaches may apply to them. Effectuation seems the most relevant and essential model for explaining and developing suitable SE practices for software startups.
翻译:软件启动是创新和软件密集型产品的重要来源; 软件研究中突出强调了理解新开办企业产品开发和提供相关支持的必要性。 虽然最先进的文献揭示了新开办企业如何开发软件,但采用这些活动的原因没有得到充分探讨。 目标:本研究通过分析启动旅程中的关键工程事件来调查软件工程(SE)活动背后的策略; 我们探索创业思维如何与SE知识领域和每个启动案例相联系。 方法: 我们的理论基础基于因果关系模型。 我们与40个软件启动企业进行了半结构性访谈。 我们使用两轮公开编码和专题分析来描述和确定创业软件开发模式。 此外,我们为每个启动案例计算了一个效果指数。 结果:我们从样本中找出了621个事件,在SEE的32个创业逻辑代码中合并了。 我们发现SE活动所有领域的逻辑都有系统性的出现。 最起码的传统产品(MVP)、技术债务(TD)和客户参与(CI)都与效果相关逻辑相关,同时测试了不同层次的SEEUR驱动效果。