Paper Number
ECIS2026-2608
Paper Type
SP
Abstract
Non-functional requirements are critical for software quality but are often neglected in agile projects, where tool-supported requirements management is dominated by functional user stories. Building on a grey literature pre-study, we adopt a design science research approach and ask how a requirements management tool should be designed to systematically capture and manage non-functional requirements in agile projects. Drawing on the Theory of Effective Use, we designed a user experience prototype that extends a typical agile project management tool including features like a dynamic glossary for shared understanding, a visually differentiated backlog that makes non-functional requirements visible as first-class items, and a dashboard with a checklist based on an international quality model standard. We demonstrate and qualitatively evaluate the prototype in six expert interviews and analyze the data using qualitative content analysis. The results indicate that the features address pain points and yield concrete requirements for future tool design and evaluation.
Recommended Citation
Mombrey, Carolin; Stuber, Kim; Mavromatis, Dimitrios; Dzubba, Janina; and Herzwurm, Georg, "Designing A Requirements Management Tool To Prevent The Neglect Of Non-Functional Requirements In Agile Projects" (2026). ECIS 2026 Proceedings. 12.
https://aisel.aisnet.org/ecis2026/isd_pm/isd_pm/12
Designing A Requirements Management Tool To Prevent The Neglect Of Non-Functional Requirements In Agile Projects
Non-functional requirements are critical for software quality but are often neglected in agile projects, where tool-supported requirements management is dominated by functional user stories. Building on a grey literature pre-study, we adopt a design science research approach and ask how a requirements management tool should be designed to systematically capture and manage non-functional requirements in agile projects. Drawing on the Theory of Effective Use, we designed a user experience prototype that extends a typical agile project management tool including features like a dynamic glossary for shared understanding, a visually differentiated backlog that makes non-functional requirements visible as first-class items, and a dashboard with a checklist based on an international quality model standard. We demonstrate and qualitatively evaluate the prototype in six expert interviews and analyze the data using qualitative content analysis. The results indicate that the features address pain points and yield concrete requirements for future tool design and evaluation.
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.