Abstract
[Context and Motivation] Focusing single-mindedly on delivering functional requirements while neglecting quality requirements has been a point of criticism of Agile software development methods since their introduction. [Question/problem] Empirical evidence on the challenges that organizations currently face when dealing with quality requirements in Agile, is however scant. [Principle ideas/results] We performed a qualitative exploratory multiple case study in the context of real-life large-scale distributed Agile projects, in order to understand the challenges Agile teams face regarding quality requirements. Based on 17 semi-structured, open-ended, in-depth interviews with Agile practitioners from six organizations in the Netherlands, we collected and analysed data, revealing 13 quality requirements challenges classified in five categories: (1) team coordination and communication, (2) quality assurance, (3) quality requirements elicitation, (4) conceptual definitions, and (5) software architecture. We found an incongruity in the way QRs are conceptualized by Agile practitioners and in RE textbooks. [Contribution] The main contributions of the paper are the explication of the challenges from practitioners’ perspective and the comparison of our findings with previously published results.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
