A systematic literature review on agile requirements engineering practices and challenges

Published on Oct 1, 2015in Computers in Human Behavior
· DOI :10.1016/j.chb.2014.10.046
Irum Inayat7
Estimated H-index: 7
(Information Technology University),
Siti Salwah Salim12
Estimated H-index: 12
(Information Technology University)
+ 2 AuthorsShahaboddin Shamshirband38
Estimated H-index: 38
(IAU: Islamic Azad University)
We mapped out 17 requirements engineering practices adopted by agile practitioners so far.Identified 5 challenges of traditional requirements engineering overcome by adopting agile requirements engineering.Found 8 challenges posed by following agile requirements engineering.Findings suggest that research context needs attention in terms of more empirical.The empirical results can help to analyse impact of adopting agile requirements engineering. Unlike traditional software development methods, agile methods are marked by extensive collaboration, i.e. face-to-face communication. Although claimed to be beneficial, the software development community as a whole is still unfamiliar with the role of the requirements engineering practices in agile methods. The term "agile requirements engineering" is used to define the "agile way" of planning, executing and reasoning about requirements engineering activities. Moreover, not much is known about the challenges posed by collaboration-oriented agile way of dealing with requirements engineering activities. Our goal is to map the evidence available about requirements engineering practices adopted and challenges faced by agile teams in order to understand how traditional requirements engineering issues are resolved using agile requirements engineering. We conducted a systematic review of literature published between 2002 and June 2013 and identified 21 papers, that discuss agile requirements engineering. We formulated and applied specific inclusion and exclusion criteria in two distinct rounds to determine the most relevant studies for our research goal. The review identified 17 practices of agile requirements engineering, five challenges traceable to traditional requirements engineering that were overcome by agile requirements engineering, and eight challenges posed by the practice of agile requirements engineering. However, our findings suggest that agile requirements engineering as a research context needs additional attention and more empirical results are required to better understand the impact of agile requirements engineering practices e.g. dealing with non-functional requirements and self-organising teams.
  • References (65)
  • Citations (135)
📖 Papers frequently viewed together
162 Citations
267 Citations
1,385 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
#1Buturab Rizvi (Athabasca University)H-Index: 1
#2Ebrahim Bagheri (RyeU: Ryerson University)H-Index: 18
Last. Dragan Gasevic (Edin.: University of Edinburgh)H-Index: 38
view all 3 authors...
The combination of Agile methods and distributed software development via remote teams represents an emerging approach to address the challenges such as late feedback, slow project timelines, and high cost, typically associated with software development projects. However, when projects are implemented using an Agile model with distributed human resources, there are a number of challenges that need to be considered and mitigated. The objectives of our work are multifold. First, we would like to u...
11 CitationsSource
Before technology is transferred to the market, it must be validated empirically by simulating future practical use of the technology. Technology prototypes are first investigated in simplified contexts, and these simulations are scaled up to conditions of practice step by step as more becomes known about the technology. This paper discusses empirical research methods for scaling up new requirements engineering (RE) technology. When scaling up to practice, researchers want to generalize from val...
31 CitationsSource
#1Neil A. Ernst (UBC: University of British Columbia)H-Index: 20
#2Alexander Borgida (RU: Rutgers University)H-Index: 41
Last. J. Mylopolous (University of Trento)H-Index: 78
view all 4 authors...
Innovative companies need an agile approach towards product and service requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and non-functional requirements. This paper examines how to support lightweight, agile requirements processes which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a propositional ...
15 CitationsSource
#1Orit Hazzan (Technion – Israel Institute of Technology)H-Index: 26
#2Yael Dubinsky (IBM)H-Index: 17
This chapter introduces the main ideas that form the basis for the agile approach. Originally, the agile approach offers a professional approach for software development that encompasseshuman, organizational, and technological aspects of software development processes. The main ideas of agile software development processes were first introduced by the Agile Manifesto and second by presenting specific agile practices that enable agile teams to accomplish their development task on high quality. In...
507 CitationsSource
May 29, 2013 in RCIS (Research Challenges in Information Science)
#1Aias Martakis (UT: University of Twente)H-Index: 1
#2Maya Daneva (UT: University of Twente)H-Index: 22
Agile practices on requirements dependencies are a relatively unexplored topic in literature. Empirical studies on it are scarce. This research sets out to uncover concepts that practitioners in companies of various sizes across the globe and in various industries, use for dealing with requirements dependencies in their agile software projects. Concepts were revealed through online focus group research, using an adapted forum for discussion, and grounded theory to analyze the responses. Our stud...
19 CitationsSource
#1Maya Daneva (UT: University of Twente)H-Index: 22
#2Egbert van der Veen (UT: University of Twente)H-Index: 4
Last. Roel Wieringa (UT: University of Twente)H-Index: 38
view all 9 authors...
The application of agile practices for requirements prioritization in distributed and outsourced projects is a relatively recent trend. Hence, not all of its facets are well-understood. This exploratory study sets out to uncover the concepts that practitioners in a large software organization use in the prioritization process and the practices that they deem good. We seek to provide a rich analysis and a deep understanding of three cases in an exploratory study that was carried out in a large an...
73 CitationsSource
Feb 23, 2013 in CSCW (Conference on Computer Supported Cooperative Work)
#1Ban Al-Ani (UCI: University of California, Irvine)H-Index: 15
#2Matthew J. Bietz (UCI: University of California, Irvine)H-Index: 11
Last. Rafael Prikladnicki (PUCRS: Pontifícia Universidade Católica do Rio Grande do Sul)H-Index: 21
view all 8 authors...
Trust remains a challenge in globally distributed development teams. In order to investigate how trust plays out in this context, we conducted a qualitative study of 5 multi-national IT organizations. We interviewed 58 individuals across 10 countries and made two principal findings. First, study participants described trust in terms of their expectations of their colleagues. These expectations fell into one of three dimensions: that socially correct behavior will persist, that team members posse...
33 CitationsSource
Agile software development methods (ASD) and open source software development methods (OSSD) are two different approaches which were introduced in last decade and both of them have their fanatical advocators. Yet, it seems that relation and interface between ASD and OSSD is a fertile area and few rigorous studies have been done in this matter. Major goal of this study was assessment of the relation and integration of ASD and OSSD. Analyzing of collected data shows that ASD and OSSD are able to s...
8 Citations
#1Kent BeckH-Index: 24
#2Mike BeedleH-Index: 2
Last. Dave ThomasH-Index: 15
view all 17 authors...
1,397 Citations
#1Lina LagerbergH-Index: 2
#2Tor SkudeH-Index: 2
Agile software development methods are often advertised as a contrast to the traditional, plan-driven approach to software development. The reported and argued benefits on software quality, coordin ...
4 Citations
Cited By135
#1Woubshet Behutiye (University of Oulu)H-Index: 3
#2Pertti Karhapää (University of Oulu)H-Index: 2
Last. Markku Oivo (University of Oulu)H-Index: 15
view all 9 authors...
Abstract Context Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD a...
2 CitationsSource
#1Mirosław Ochodek (PUT: Poznań University of Technology)H-Index: 7
#2Sylwia Kopczynska (PUT: Poznań University of Technology)H-Index: 5
Last. Miroslaw Staron (University of Gothenburg)H-Index: 20
view all 3 authors...
Abstract Context: COSMIC is a widely used functional size measurement (FSM) method that supports software development effort estimation. The FSM methods measure functional product size based on functional requirements. Unfortunately, when the description of the product’s functionality is often abstract or incomplete, the size of the product can only be approximated since the object to be measured is not yet fully described. Also, the measurement performed by human-experts can be time-consuming, ...
1 CitationsSource
#1Oliver Krancher (ITU: IT University of Copenhagen)H-Index: 3
Although agile practices are gaining in popularity, there is little evidence showing how particular agile practices, in particular those involving the client, affect the success of outsourced software projects. Data from a matched survey of sponsors and developers in 60 outsourced information systems projects indicate negative effects of continuous analysis and positive effects of joint decision making and continuous integration on project success. Moreover, interaction analyses show that some p...
#1Lucas Gren (Chalmers University of Technology)H-Index: 6
#2Alfredo Goldman (USP: University of São Paulo)H-Index: 15
Last. Christian Jacobsson (University of Gothenburg)H-Index: 6
view all 3 authors...
With the agile approach to managing software development projects comes an increased dependability on well functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspective is related to some work practices of agile teams. Data were collected from 34 agile teams (200 individuals) from six software development organizations and one university in both Brazil and Sweden using the ...
3 CitationsSource
#1Mohammad Shameem (Madanapalle Institute of Technology and Science)
#1Mohammad Shameem (Madanapalle Institute of Technology and Science)H-Index: 3
Last. Arif Ali Khan (NU: Nanjing University)H-Index: 10
view all 4 authors...
Abstract Increasingly, software development organizations are scaling agile practices in the global software development (GSD) environment in order to meet the requirements of the quickly changing and regularly developing business environment. The main objectives of this study are to investigate the key barriers and develop a prioritization-based taxonomy of the barriers for scaling agile development in the GSD environment. Total twenty-two barriers were extracted from the available literature a...
#1Mehdi Rajabi Asadabadi (ANU: Australian National University)H-Index: 5
#1Mehdi Rajabi Asadabadi (ANU: Australian National University)
Last. Keiran Sharpe (UNSW: University of New South Wales)H-Index: 1
view all 3 authors...
Abstract In large-scale projects, it often occurs that the product the purchaser ends up receiving – possibly from projects extending over many years – differs from what they expected. The provider usually defends its delivered product and may blame the imprecision and ambiguity of the requirements, defined by the purchaser, as the primary reason for misinterpretation of requirements and resulting deficiencies. This letter relies on game theory to explain this problem including both intentional ...
#2Mike Kagioglou (USYD: University of Sydney)
Last. Patricia TzortzopoulosH-Index: 14
view all 3 authors...
The recent notable emergence of a body of research in requirements management on one hand and benefits realisation has contributed to addressing a growing need for improved performance in Architecture, Engineering and Construction (AEC) projects. However, front end design (FED) as one of the vital processes in the project life cycle and delivery has attracted limited research to date within this understanding. This paper aims to map current evidence on requirements management in facilitating ben...
#1Nitish Patkar (University of Bern)
#2Mohammad Ghafari (University of Bern)H-Index: 8
Last. Sofija Hotomski (UZH: University of Zurich)H-Index: 3
view all 4 authors...
#1Rita Marques (IST: Instituto Superior Técnico)H-Index: 1
#1Rita MarquesH-Index: 3
Last. Pedro GonçalvesH-Index: 1
view all 5 authors...
Despite the wide adoption of agile methodologies, software development teams still struggle to meet requirements, partially due to practitioners’ lack of motivation to apply agile techniques in practice. We propose a gamification software tool to make Scrum techniques more fun and engaging for practitioners. This paper presents the results of the first iteration of a larger research effort that follows the Design Science Research methodology, in which a prototype was developed as a Jira Software...