Learn More
Scrum-of-Scrums meeting is mentioned in the literature as the mech- anism for handling inter-team coordination in large-scale Scrum. However, how to implement it in projects with tens of teams is not explained. In this paper, we present a multiple case study on how Scrum-of-Scrum meetings were applied in two large-scale, globally distributed Scrum projects(More)
In this paper, we present a LEGO-based Scrum simulation game that we used twice with Master’s level students at Aalto University. The game was initially developed as an internal training tool in F-Secure Corporation, a Finnish security software company, to support their agile adoption. In the game, student teams learn the Scrum roles, events and(More)
Context: Proponents of the Scrum software development method use the term "Scrum But" to refer to harmful changes to Scrum. Scrum has been increasingly adopted in large software development organizations. This has led to changes to Scrum practices, but it is not known if these changes are harmful. Objective: We studied how the requirements were planned and(More)
Transforming a large organization from a plan-driven process to agile development is challenging. Despite this, large organizations are increasingly adopting agile development and lean thinking. However, there is little research on how to conduct a successful transformation in large organizations, which often are globally distributed. In this paper we(More)
Agile software development (ASD) methods have gained popularity in the industry and been the subject of an increasing amount of academic research. Although requirements engineering (RE) in ASD has been studied, the overall understanding of RE in ASD as a phenomenon is still weak. We conducted a mapping study of RE in ASD to review the scientific literature.(More)
A way to scale up agile release planning to meet the requirements of multi-team agile development is a practice called joint release planning. A software product company piloted the joint release planning method. The aim of the company was to improve coordination of work of multiple agile development teams who develop a large legacy software product.(More)
1. RQ: What was the release planning process? 2. RQ: What were the challenges related to the release planning process? 3. RQ: What were the benefits of the continous release planning process? Feature team Feature team Feature team Feature team Technical product area Technical product area Developmen Scrum team Developmen Scrum team Developmen Scrum team(More)
The Product Owner in Scrum is a crucial role responsible for managing customer requirements in the form of prioritized backlog items and communicating them to the Scrum team. When scaling Scrum to large projects consisting of tens of teams, one Product Owner is not able to work with all the teams; thus the role needs to be scaled. While the literature(More)