Comparing Requirements Decomposition Within the Scrum, Scrum with Kanban, XP, and Banana Development Processes

Abstract

Context: Eliciting requirements from customers is a complex task. In Agile processes, the customer talks directly with the development team and often reports requirements in an unstructured way. The requirements elicitation process is up to the developers, who split it into user stories by means of different techniques. Objective: We aim to compare the requirements decomposition process of an unstructured process and three Agile processes, namely XP, Scrum, and Scrum with Kanban. Method: We conducted a multiple case study with a replication design, based on the project idea of an entrepreneur, a designer with no experience in software development. Four teams developed the project independently, using four different development processes. The requirements were elicited by the teams from the entrepreneur, who acted as product owner and was available to talk with the four groups during the project. Results: The teams decomposed the requirements using different techniques, based on the selected development process. Conclusion: Scrum with Kanban and XP resulted in the most effective processes from different points of view. Unexpectedly, decomposition techniques commonly adopted in traditional processes are still used in Agile processes, which may reduce project agility and performance. Therefore, we believe that decomposition techniques need to be addressed to a greater extent, both from the practitioners' and the research points of view.

Microservices Anti-patterns: A Taxonomy

“…Moreover, because of their size, they are easier to maintain and more fault-tolerant since a failure of one service will not break the whole system, which could happen in a monolithic system. Since every microservice has its own context and set of code, each microservice can change its entire logic from the inside, but from the outside, it still does the same thing, reducing the need of interaction between teams[32] [33]. Different microservice patterns have been proposed by practitioners [28] and researchers [16].…”

Comparing Communication Effort within the Scrum, Scrum with Kanban, XP, and Banana Development Processes

“…The software factory is the perfect environment for conducting empirical studies with next generation developers, since participants represents the typical developers entering to the job-market [6]. This is also confirmed by the results of several empirical studies conducted in the past [4], [5], [16], [24], [26], [27]). The groups were defined in a random manner without influencing the study results.…”

An Empirical Study on Technical Debt in a Finnish SME

“…The risk of a roadblock through a "TD bankruptcy" increases when new requirements emerge and need attention, leading to the rewriting of existing features, which should be avoided by estimating the costs of TD. Moreover, outsourcing part of the development to consultants, also increase the risk of requirement TD [14] related to misunderstandings [15] and increase the communication overhead [16].…”