A conceptual model of client-driven agile requirements prioritization: results of a case study

Authors:
Zornitza Racheva;Maya Daneva;Andrea Herrmann
Affiliations:
University of Twente, Netherlands;University of Twente, Netherlands;University of Braunschweig, Germany
Venue:
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Year:
2010

Citing 8
Cited 2

First things first

Software Development
Managing Agile Projects

Managing Agile Projects
Agile Requirements Engineering Practices: An Empirical Study

IEEE Software
A product management challenge: Creating software product value through requirements selection

Journal of Systems Architecture: the EUROMICRO Journal
Portraying the practice of decision-making in requirements engineering: a case of large scale bespoke development

Requirements Engineering
A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case

Journal of Systems and Software
Do We Know Enough about Requirements Prioritization in Agile Projects: Insights from a Case Study

RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
Incorporating learning and expected cost of change in prioritizing features on agile projects

XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering

Agile requirements prioritization: what happens in practice and what is described in literature

REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
RCDA: Architecting as a risk- and cost management discipline

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

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.