Abstract
Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects.
Original language | English |
---|---|
Title of host publication | ESEM '10 |
Subtitle of host publication | Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement |
Editors | G. Succi, M. Morisio, N. Nagappan |
Place of Publication | New York |
Publisher | Association for Computing Machinery |
Number of pages | 4 |
ISBN (Print) | 978-1-4503-0039-1 |
DOIs | |
Publication status | Published - Sept 2010 |
Event | 4th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM 2010 - Bolzano-Bozen, Italy Duration: 15 Sept 2010 → 17 Sept 2010 Conference number: 4 |
Conference
Conference | 4th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM 2010 |
---|---|
Abbreviated title | ESEM 2010 |
Country/Territory | Italy |
City | Bolzano-Bozen |
Period | 15/09/10 → 17/09/10 |
Keywords
- Agile development
- SCS-Services
- Requirements prioritization
- Inter-iteration decision-making process
- Case study