Agile Elicitation of Scalability Requirements for Open Systems: A Case Study
This addresses the problem of poorly described scalability requirement elicitation for agile developers, particularly in open systems like banking, but it is incremental as it builds on existing coordination theory and design science.
The paper tackles the challenge of eliciting scalability requirements in agile software development by introducing the ScrumScale model, a lightweight spreadsheet artifact, and demonstrates its application in an open banking case study where stakeholders spent 55 hours to systematically produce requirements.
Eliciting scalability requirements during agile software development is complicated and poorly described in previous research. This article presents a lightweight artifact for eliciting scalability requirements during agile software development: the ScrumScale model. The ScrumScale model is a simple spreadsheet. The scalability concepts underlying the ScrumScale model are clarified in this design science research, which also utilizes coordination theory. This paper describes the open banking case study, where a legacy banking system becomes open. This challenges the scalability of this legacy system. The first step in understanding this challenge is to elicit the new scalability requirements. In the open banking case study, key stakeholders from TietoEVRY spent 55 hours eliciting TietoEVRY's open banking project's scalability requirements. According to TietoEVRY, the ScrumScale model provided a systematic way of producing scalability requirements. For TietoEVRY, the scalability concepts behind the ScrumScale model also offered significant advantages in dialogues with other stakeholders.