A systematic literature review on agile requirements engineering practices and challenges. (October 2015)
- Record Type:
- Journal Article
- Title:
- A systematic literature review on agile requirements engineering practices and challenges. (October 2015)
- Main Title:
- A systematic literature review on agile requirements engineering practices and challenges
- Authors:
- Inayat, Irum
Salim, Siti Salwah
Marczak, Sabrina
Daneva, Maya
Shamshirband, Shahaboddin - Abstract:
- Highlights: 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. Abstract: 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. WeHighlights: 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. Abstract: 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. … (more)
- Is Part Of:
- Computers in human behavior. Volume 51:Part B(2015)
- Journal:
- Computers in human behavior
- Issue:
- Volume 51:Part B(2015)
- Issue Display:
- Volume 51, Issue 2 (2015)
- Year:
- 2015
- Volume:
- 51
- Issue:
- 2
- Issue Sort Value:
- 2015-0051-0002-0000
- Page Start:
- 915
- Page End:
- 929
- Publication Date:
- 2015-10
- Subjects:
- Agile software development methods -- Agile requirements engineering -- Collaboration -- Traditional requirements engineering -- Systematic review
Interactive computer systems -- Periodicals
Man-machine systems -- Periodicals
004.019 - Journal URLs:
- http://www.sciencedirect.com/science/journal/07475632 ↗
http://www.elsevier.com/journals ↗ - DOI:
- 10.1016/j.chb.2014.10.046 ↗
- Languages:
- English
- ISSNs:
- 0747-5632
- Deposit Type:
- Legaldeposit
- View Content:
- Available online (eLD content is only available in our Reading Rooms) ↗
- Physical Locations:
- British Library DSC - 3394.921600
British Library DSC - BLDSS-3PM
British Library HMNTS - ELD Digital store - Ingest File:
- 7361.xml