A systematic literature review on agile requirements engineering practices and challenges

Irum Inayat, Siti Salwah Salim, Sabrina Marczak, Maia Daneva, Shahaboddin Shamshirband

Research output: Contribution to journalArticleAcademicpeer-review

117 Citations (Scopus)
1117 Downloads (Pure)

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.
Original languageUndefined
Pages (from-to)915-929
Number of pages15
JournalComputers in human behavior
Volume51
Issue numberPart B
DOIs
Publication statusPublished - Oct 2015

Keywords

  • EWI-25402
  • SCS-Services
  • Traditional Requirements Engineering
  • Systematic Review
  • METIS-309714
  • Agile Requirements Engineering
  • Agile software development methods
  • Collaboration
  • IR-93998

Cite this

Inayat, Irum ; Salim, Siti Salwah ; Marczak, Sabrina ; Daneva, Maia ; Shamshirband, Shahaboddin. / A systematic literature review on agile requirements engineering practices and challenges. In: Computers in human behavior. 2015 ; Vol. 51, No. Part B. pp. 915-929.
@article{bab052c31e7240baa9c75d570d9ba3d5,
title = "A systematic literature review on agile requirements engineering practices and challenges",
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.",
keywords = "EWI-25402, SCS-Services, Traditional Requirements Engineering, Systematic Review, METIS-309714, Agile Requirements Engineering, Agile software development methods, Collaboration, IR-93998",
author = "Irum Inayat and Salim, {Siti Salwah} and Sabrina Marczak and Maia Daneva and Shahaboddin Shamshirband",
note = "eemcs-eprint-25402",
year = "2015",
month = "10",
doi = "10.1016/j.chb.2014.10.046",
language = "Undefined",
volume = "51",
pages = "915--929",
journal = "Computers in human behavior",
issn = "0747-5632",
publisher = "Elsevier",
number = "Part B",

}

A systematic literature review on agile requirements engineering practices and challenges. / Inayat, Irum; Salim, Siti Salwah; Marczak, Sabrina; Daneva, Maia; Shamshirband, Shahaboddin.

In: Computers in human behavior, Vol. 51, No. Part B, 10.2015, p. 915-929.

Research output: Contribution to journalArticleAcademicpeer-review

TY - JOUR

T1 - A systematic literature review on agile requirements engineering practices and challenges

AU - Inayat, Irum

AU - Salim, Siti Salwah

AU - Marczak, Sabrina

AU - Daneva, Maia

AU - Shamshirband, Shahaboddin

N1 - eemcs-eprint-25402

PY - 2015/10

Y1 - 2015/10

N2 - 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.

AB - 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.

KW - EWI-25402

KW - SCS-Services

KW - Traditional Requirements Engineering

KW - Systematic Review

KW - METIS-309714

KW - Agile Requirements Engineering

KW - Agile software development methods

KW - Collaboration

KW - IR-93998

U2 - 10.1016/j.chb.2014.10.046

DO - 10.1016/j.chb.2014.10.046

M3 - Article

VL - 51

SP - 915

EP - 929

JO - Computers in human behavior

JF - Computers in human behavior

SN - 0747-5632

IS - Part B

ER -