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

Published on Sep 16, 2010 in ESEM (Empirical Software Engineering and Measurement)
· DOI :10.1145/1852786.1852837
Zornitza Racheva7
Estimated H-index: 7
(UT: University of Twente),
Maya Daneva22
Estimated H-index: 22
(UT: University of Twente),
Andrea Herrmann10
Estimated H-index: 10
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.
  • References (14)
  • Citations (20)
📖 Papers frequently viewed together
2010RCIS: Research Challenges in Information Science
28 Citations
34 Citations
73 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
Sep 1, 2010 in RE (IEEE International Conference on Requirements Engineering)
#1Zornitza Racheva (UT: University of Twente)H-Index: 7
#2Maya Daneva (UT: University of Twente)H-Index: 22
Last. Roel WieringaH-Index: 38
view all 5 authors...
Requirements prioritization is an essential mechanism of agile software development approaches. It maximizes the value delivered to the clients and accommodates changing requirements. This paper presents results of an exploratory cross-case study on agile prioritization and business value delivery processes in eight software organizations. We found that some explicit and fundamental assumptions of agile requirement prioritization approaches, as described in the agile literature on best practices...
42 CitationsSource
May 1, 2010 in RCIS (Research Challenges in Information Science)
#1Zornitza Racheva (UT: University of Twente)H-Index: 7
#2Maya Daneva (UT: University of Twente)H-Index: 22
Last. Roel Wieringa (UT: University of Twente)H-Index: 38
view all 4 authors...
28 CitationsSource
#1Kai Petersen (BTH: Blekinge Institute of Technology)H-Index: 24
#2Claes Wohlin (BTH: Blekinge Institute of Technology)H-Index: 47
Recent empirical studies have been conducted identifying a number of issues and advantages of incremental and agile methods. However, the majority of studies focused on one model (Extreme Programming) and small projects. To draw more general conclusions we conduct a case study in large-scale development identifying issues and advantages, and compare the results with previous empirical studies on the topic. The principle results are that (1) the case study and literature agree on the benefits whi...
150 CitationsSource
#1Beatrice Alenljung (University of Skövde)H-Index: 6
#2Ann I. Persson (University of Skövde)H-Index: 18
Complex decision-making is a prominent aspect of requirements engineering (RE) and the need for improved decision support for RE decision-makers has been identified by a number of authors in the research literature. A first step toward better decision support in requirements engineering is to understand multifaceted decision situations of decision-makers. In this paper, the focus is on RE decision-making in large scale bespoke development. The decision situation of RE decision-makers on a subsys...
36 CitationsSource
#1Sebastian Barney (UNSW: University of New South Wales)H-Index: 10
#2Aybüke Aurum (UNSW: University of New South Wales)H-Index: 27
Last. Claes Wohlin (BTH: Blekinge Institute of Technology)H-Index: 47
view all 3 authors...
It is important for a software company to maximize value creation for a given investment. The purpose of requirements engineering activities is to add business value that is accounted for in terms of return on investment of a software product. This paper provides insight into the release planning processes used in the software industry to create software product value, by presenting three case studies. It examines how IT professionals perceive value creation through requirements engineering and ...
99 CitationsSource
#1Lan Cao (ODU: Old Dominion University)H-Index: 16
#2Balasubramaniam Ramesh (GSU: Georgia State University)H-Index: 30
An analysis of data from 16 software development organizations reveals seven agile RE practices, along with their benefits and challenges. The rapidly changing business environment in which most organizations operate is challenging traditional requirements-engineering (RE) approaches. Software development organizations often must deal with requirements that tend to evolve quickly and become obsolete even before project completion. Rapid changes in competitive threats, stakeholder preferences, de...
267 CitationsSource
#1R. Scott Harris (Montana State University Billings)H-Index: 1
#2Mike CohnH-Index: 1
Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionabl...
14 CitationsSource
#1Kathy CharmazH-Index: 33
An Invitation to Grounded Theory Gathering Rich Data Coding in Grounded Theory Practice Memo-Writing Theoretical Sampling, Saturation and Sorting Reconstructing Theory in Grounded Theory Studies Writing the Draft Reflecting on the Research Process
12.1k Citations
#1Adele E. Clarke (UCSF: University of California, San Francisco)H-Index: 20
List of Illustrations Acknowledgments Prologue: Regrounding Grounded Theory 1. Pushing and Being Pulled Around the Postmodern Turn Grounded Theory/Symbolic Interactionism as a Theory/Methods Package Grounded Theory/Symbolic Interactionism as Always Already Around the Postmodern Turn Grounded Theory as Recalcitrant Against the Postmodern Turn Pushing Grounded Theory Around the Postmodern Turn Reflections and Anticipations 2. From Chicago Ecologies to Situational Analysis Root Metaphors: From Chic...
1,079 Citations
#1Sanjiv AugustineH-Index: 1
PRAISE FOR MANAGING AGILE PROJECTS"In the hands of another, this class of material could become incoherent, but Sanjiv has enough intellectual power to ground his subject...Fans of APM and those who prefer new ideas as a catalyst for their management approach should find Managing Agile Projects rewarding."Wes Balakian, Chairman and Executive Advisor, PMI eBusiness SIG"I only wish I had read this book when I started my career in software product management, or even better yet, when I was given my...
105 Citations
Cited By20
#1Faiza Allah Bukhsh (UT: University of Twente)H-Index: 2
#2Zaharah Allah Bukhsh (UT: University of Twente)H-Index: 2
Last. Maya Daneva (UT: University of Twente)H-Index: 22
view all 3 authors...
Abstract [Context and Motivation] Many requirements prioritization approaches have been proposed, however not all of them have been investigated empirically in real-life settings. As a result, our knowledge of their applicability and actual use is incomplete. [Question/problem] A 2007 systematic review on requirements prioritization mapped out the landscape of proposed prioritization approaches and their prioritization criteria. To understand how this sub-field of requirements engineering has de...
#1Abderrahmane Leshob (UQAM: Université du Québec à Montréal)H-Index: 4
#2Pierre Hadaya (UQAM: Université du Québec à Montréal)H-Index: 13
Last. Laurent Renard (UQAM: Université du Québec à Montréal)H-Index: 3
view all 3 authors...
Requirements prioritization is an important activity of the software development process. It is performed to rank information systems (IS) requirements in the order in which they will be implemented to maximize the value delivered to customers. A number of methods and techniques have been proposed to help organizations prioritize IS requirements. However, they all suffer from a number of limitations and their implementation are mostly informal. This work aims to design a novel method that automa...
#1Woogon Shim (Ajou University)
Agile and lean are now the mainstream tenets of software development. This development methodology is attracting attention because it can develop software that operates quickly despite uncertain situations and limited information (requirements), and it can adaptively develop while checking feedback both frequently and regularly. The key is to welcome change without resistance, which is not limited to development but also requires changes in requirement management. However, there is a lack of pra...
#1Woogon Shim (LG Electronics)H-Index: 1
#2Seok-Won Lee (Ajou University)H-Index: 13
Abstract Nowadays agile development has become a mainstream development methodology. Yet agile is still lacking in how in-depth it deals with Requirement Engineering (RE) compared to the other development stages. There have been attempts to apply agile RE techniques to traditional development and conversely to apply traditional RE techniques to agile development. But the biggest problem is that it is difficult to maintain the essence of agile which is to “collaborate”, “(iterative and frequent) ...
3 CitationsSource
#1Geraldo Torres G. Neto (UPE: Universidade de Pernambuco)
#2Wylliams Barbosa Santos (UPE: Universidade de Pernambuco)H-Index: 2
Last. Tiziana Margaria (UL: University of Limerick)H-Index: 32
view all 4 authors...
Recently, studies involving the creation of business value in Agile Software Development (ASD) have been growing substantially. However, the concept of value creation in ASD has not yet been clearly defined. Besides, the literature does not define practices that can create business value for ASD. Identifying these practices can change the mindset of agile teams, since surveys indicate that, from the point of view of the agile team, the creation of value is poorly understood. Thus, this study car...
#1Emily Winter (Lancaster University)H-Index: 1
#2Steve Forshaw (Lancaster University)H-Index: 1
Last. Maria Angela Ferrario (Lancaster University)H-Index: 11
view all 3 authors...
Background: Human values, such as prestige, social justice, and financial success, influence software production decision-making processes. While their subjectivity makes some values difficult to measure, their impact on software motivates our research. Aim: To contribute to the scientific understanding and the empirical investigation of human values in Software Engineering (SE). Approach: Drawing from social psychology, we consider values as mental representations to be investigated on three le...
6 CitationsSource
#1Shalinka Jayatilleke (La Trobe University)H-Index: 2
#2Richard Lai (La Trobe University)H-Index: 13
ContextSoftware requirements are often not set in concrete at the start of a software development project; and requirements changes become necessary and sometimes inevitable due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous work has shown that failing to manage software requirements changes well is a main contributor to project failure. G...
8 CitationsSource
#1Vaibhav Sachdeva (UTD: University of Texas at Dallas)H-Index: 1
Agile Methodologies are gaining popularity at lightning pace and have provided software industry a way to deliver products incrementally at a rapid pace. With an attempt to welcome changing requirements and incremental delivery, requirements prioritization becomes vital for the success of the product and thereby the organization. However, prioritizing requirements can become a nightmare for product owners and there is no easy way to create a product backlog, 1 to n list of prioritized requiremen...
1 CitationsSource
#1Kaiss ElgharianiH-Index: 1
#2Nazri KamaH-Index: 7
The popularity of agile methodology has been increased since agile offers further collaboration. Requirements engineering (RE) is one of the software development process in agile approaches. The features of face to face communication is one of agile way which unlike to other traditional software methods. Software developers are using the definition agile way to improve the agile way of activities. Besides, the challenge of dealing with RE practices is not much is known in agile way or model. How...
6 CitationsSource
#1Varun Gupta (Amity University)H-Index: 5
#2Durg Singh Chauhan (GLA University)H-Index: 15
Last. Kamlesh DuttaH-Index: 11
view all 3 authors...
Mass market software development involves uncertainties and involves effortful activities of requirement prioritisation and reprioritisations that may lead to delivery cost and time overrun. To facilitate the minimisation of efforts in resource constrained incremental developments, the historical preferences of stakeholders of previous similar projects could be reused during the development of the new similar project by employing the modified version of the HR tree, indexing structure as used fo...