Nirnaya Tripathi

University of Oulu · Department of Information Processing Science

Context: Software start-ups have shown their ability to develop and launch innovative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices. Objective: We explore how start-ups use Agile practices and what effects can be associated with the use of those practi...

This chapter aims to explore supporting factors, such as incubators, accelerators, co-working spaces, mentors, and events in the startup ecosystem. To understand these five aspects and to explore their roles in startups, we investigated an Oulu startup ecosystem. In this case study, we conducted research interviews with practitioners working with s...

Context Software startups develop innovative products through which they scale their business rapidly, and thus, provide value to the economy, including job generation. However, most startups fail within two years of their launch because of a poor problem-solution fit and negligence of the learning process during minimum viable product (MVP) develo...

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.

The concept of ‘Minimum Viable Product’ (MVP) is largely adapted in the software industry as well as in academia. Minimum viable products are used to test hypotheses regarding the target audience, save resources from unnecessary development work and guide a company towards a stable business model. As the game industry is becoming an important busin...

Context: Successful startup firms have the ability to create jobs and contribute to economic welfare. A suitable ecosystem developed around startups is important to form and support these firms. In this regard, it is crucial to understand the startup ecosystem, particularly from researchers’ and practitioners’ perspectives. However, a systematic li...

Context: Software startups aim to develop innovative products, grow rapidly, and thus become important in the development of economy and jobs. Requirements engineering (RE) is a key process area in software development, but its effects on software startups are unclear. Objective: The main objective of this study was to explore how RE (elicitation,...

Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precede...

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 proce...

Context: To attain an advantage over competitors, small software companies (SSCs) need to have an efficient software development process. However, systematic review studies that have examined the software development process within the context of SSCs are limited. Objective: Therefore, the objective of this paper is to rigorously assess the current...

Over the past decade, major advancements in software development have occurred in the global context. Global software development (GSD) is an effective strategy, and many higher educational institutions have been offering GSD courses. These courses are usually organized together with another institution situated in a different location. However, co...

In software development organizations, large-scale distributed projects pose many challenges, such as hierarchical requirements, large team size, and managing workflow. Agile methods, like Scrum, seem to have limitations in addressing those issues. Kanban offers an interesting alternative in this concern by setting work-in-progress (WIP) limits to...