Towards understanding startup product development as effectual entrepreneurial behaviors

Software startups face with multiple technical and business challenges, which could make the startup journey longer, or even become a failure. Little is known about entrepreneurial decision making as a direct force to startup development outcome. In this study, we attempted to apply a behaviour theory of entrepreneurial firms to understand the root-cause of some software startup s challenges. Six common challenges related to prototyping and product development in twenty software startups were identified. We found the behaviour theory as a useful theoretical lens to explain the technical challenges. Software startups search for local optimal solutions, emphasise on short-run feedback rather than long-run strategies, which results in vague prototype planning, paradox of demonstration and evolving throw-away prototypes. The finding implies that effectual entrepreneurial processes might require a more suitable product development approach than the current state-of-practice.Comment: This is the author's version of the work. Copyright owner's version can be accessed at https://doi.org/10.1007/978-3-319-69191-6_15, 8th ICSOB 2017, Essen, German

Understanding Barriers to Internal Startups in Large Organizations: Evidence from a Globally Distributed Company

Large global companies need to speed up their innovation activities to increase competitive advantage. However, such companies' organizational structures impede their ability to capture trends they are well aware of due to bureaucracy, slow decision-making, distributed departments, and distributed processes. One way to strengthen the innovation capability is through fostering internal startups. We report findings from an embedded multiple-case study of five internal startups in a globally distributed company to identify barriers for software product innovation: late involvement of software developers, executive sponsor is missing or not clarified, yearly budgeting and planning, unclear decision-making authority, lack of digital infrastructure for experimentation and access to data from external actors. Drawing on the framework of continuous software engineering proposed by Fitzgerald and Stol, we discuss the role of BizDev in software product innovation. We suggest that lack of continuity, rather than the lack of speed, is an ultimate challenge for internal startups in large global companies.acceptedVersio

When Teams Go Crazy:An Environment to Experience Group Dynamics in Software Project Management Courses

Software development consists to a large extend of humanbased processes with continuously increasing demands regarding interdisciplinary team work. Understanding the dynamics of software teams can be seen as highly important to successful project execution. Hence, for future project managers, knowledge about non-technical processes in teams is significant. In this paper, we present a course unit that provides an environment in which students can learn and experience the impact of group dynamics on project performance and quality. The course unit uses the Tuckman model as theoretical framework, and borrows from controlled experiments to organize and implement its practical parts in which students then experience the effects of, e.g., time pressure, resource bottlenecks, staff turnover, loss of key personnel, and other stress factors. We provide a detailed design of the course unit to allow for implementation in further software project management courses. Furthermore, we provide experiences obtained from two instances of this unit conducted in Munich and Karlskrona with 36 graduate students. We observed students building awareness of stress factors and developing counter measures to reduce impact of those factors. Moreover, students experienced what problems occur when teams work under stress and how to form a performing team despite exceptional situations

Guidelines for using empirical studies in software engineering education

Software engineering education is under constant pressure to provide students with industry-relevant knowledge and skills. Educators must address issues beyond exercises and theories that can be directly rehearsed in small settings. Industry training has similar requirements of relevance as companies seek to keep their workforce up to date with technological advances. Real-life software development often deals with large, software-intensive systems and is influenced by the complex effects of teamwork and distributed software development, which are hard to demonstrate in an educational environment. A way to experience such effects and to increase the relevance of software engineering education is to apply empirical studies in teaching. In this paper, we show how different types of empirical studies can be used for educational purposes in software engineering. We give examples illustrating how to utilize empirical studies, discuss challenges, and derive an initial guideline that supports teachers to include empirical studies in software engineering courses. Furthermore, we give examples that show how empirical studies contribute to high-quality learning outcomes, to student motivation, and to the awareness of the advantages of applying software engineering principles. Having awareness, experience, and understanding of the actions required, students are more likely to apply such principles under real-life constraints in their working life.Peer reviewe

Achieving agility and quality in product development -an empirical study of hardware startups

acceptedVersio

Customer Involvement in Continuous Deployment: A Systematic Literature Review

Abstract. [Context and motivation] In order to build successful software products and services, customer involvement and an understanding of customers' requirements and behaviours during the development process are essential. [Question/Problem] Although continuous deployment is gaining attention in the software industry as an approach for continuously learning from customers, there is no common overview of the topic yet. [Principal ideas/results] To provide a common overview, we conduct a secondary study that explores the state of reported evidence on customer input during continuous deployment in software engineering, including the potential benefits, challenges, methods and tools of the field. [Contribution] We report on a systematic literature review covering 25 primary studies. Our analysis of these studies reveals that although customer involvement in continuous deployment is highly relevant in the software industry today, it has been relatively unexplored in academic research. The field is seen as beneficial, but there are a number of challenges related to it, such as misperceptions among customers. In addition to providing a comprehensive overview of the research field, we clarify the gaps in knowledge that need to be studied further

User research in product development in business to business software as a service

Customers are more empowered to make purchasing decisions than ever before, and customer experience has become a critical decision factor. Business to business (B2B) software as a service (SaaS) companies are changing their strategies and ways of working to become more customer-centric and stay competitive. To understand users, their needs, motivations and the problems that they are facing, companies do user research and involve users in product development. This thesis explores how B2B SaaS organizations utilize user research when developing products. It aims to answer some of the most fundamental questions: which user research methods companies use, how they involve internal stakeholders in user research and how they select the users and motivate them to take part in product development. A qualitative multiple case study approach was used in this thesis to answer the research questions. The literature review aims to provide a broad overview of the topic. Six B2B SaaS companies and two service design companies were interviewed to learn about user research in B2B SaaS field. The results of the thesis show that less customer-centric organizations do ad-hoc user research. More customer-centric companies incorporate user research into the development process. Both approaches are valuable for developing a product that fits customer needs but incorporated user involvement is necessary for achieving a better outcome. Customer-centric organizations include various stakeholders in user research to increase the transparency of findings and create empathy towards users. Furthermore, qualitative user research is essential for customer-centric product development. Regarding the users, while they are motivated to take part in product development, it was discovered that in the B2B field the process of approaching users can be challenging. This thesis compares how different B2B SaaS companies do user research. It reveals the best practices, challenges and opportunities of user involvement. This information can be useful for organizations that aim to become customer-centric. The findings contribute to the literature by providing insights into successful examples and the challenges of user involvement in product development in B2B SaaS organizations

Exploring Software Development as an Experiment System : An Interview-Based Qualitative Survey

An experiment-driven approach to software product and service development is getting increasing attention as a way to channel limited resources to the efficient creation of customer value. In this approach, software functionalities are developed incrementally and validated in continuous experiments with stakeholders such as customers and users. The experiments provide factual feedback for guiding subsequent development. Although case studies on experimentation conventions in the industry exist, an understanding of the state of the practice is incomplete. Furthermore, the obstacles and success factors of continuous experimentation have been little discussed. To these ends, an interview-based qualitative survey was conducted, exploring the experimentation experiences of ten software development companies. The study found that although the principles of continuous experimentation resonated with industry practitioners, the state of the practice was not mature. In particular, experimentation was rarely systematic and continuous. Key challenges related to changing organizational culture, accelerating development cycle speed, measuring customer value and product success, and securing resources. Success factors included an empowered organizational culture and deep customer and domain knowledge. There was also a good availability of technical tools and competence to support experimentation