A systematic literature review on agile requirements engineering practices and challenges

Inayat, Irum; Salim, Siti Salwah; Marczak, Sabrina; Daneva, Maya; Shamshirband, Shahaboddin

doi:10.1016/j.chb.2014.10.046

Cited by 426 publications

(410 citation statements)

References 52 publications

Supporting

Mentioning

373

Contrasting

Unclassified

Order By: Relevance

“…Inayat, et al presented in [17] a comprehensive systematic review about resolving traditional requirements engineering issues using agile requirements engineering for studies published between January 2002 and June 2013 in which 21 papers out of 531 were studied. The main results of the study can be summarized as follow:…”

Section: Agile Requirements Engineeringmentioning

confidence: 99%

Agile Software Development Methodologies: Survey of Surveys

Al-Zewairi¹,

Biltawi²,

Etaiwi³

et al. 2017

JCC

View full text Add to dashboard Cite

Agile software design and development methodologies have been gaining rigorous attention in the software engineering research community since their early introduction in the mid-nineties in addition to being highly adopted by the software development industry. In the last 15 years, an excessive number of research studies have been conducted on agile methods, a great number of notable methods have been proposed and various surveys have been presented by many researchers. In this study, the authors intend to conduct a literature survey study of the surveys of the different agile methodologies ranging from January 2000 to December 2015 using an intuitive research methodology called "Compare and Review" (CR). Furthermore, these survey papers were classified into four major categories according to their area of study. Additionally, the newly proposed agile methodologies that have not been addressed yet in any other literature review were reviewed and compared in terms of where the changes that they proposed lay on the SDLC.

show abstract

Section: Agile Requirements Engineeringmentioning

confidence: 99%

Agile Software Development Methodologies: Survey of Surveys

Al-Zewairi¹,

Biltawi²,

Etaiwi³

et al. 2017

JCC

View full text Add to dashboard Cite

show abstract

“…Release plan is done for each release in which iteration length is decided, developers and customers unanimously decide what will be in a particular iteration; velocity points are determined per iteration. Task level planning involves the breaking down of user stories into subsequent tasks, allocation of tasks among team members and focus is put on implementation issues [39]- [42]. After the literature survey of RE in Agile the overall Agile RE process is accumulated and described in Figure 3.…”

Section: Re In Agilementioning

confidence: 99%

Quintessence of Traditional and Agile Requirement Engineering

Abbas¹

2016

JSEA

View full text Add to dashboard Cite

Requirement gathering for software development project is the most crucial stage and thus requirement engineering (RE) occupies the chief position in the software development. Countless techniques concerning the RE processes exist to make sure the requirements are coherent, compact and complete in all respects. In this way different aspects of RE are dissected and detailed upon. A comparison of RE in Agile and RE in Waterfall is expatiated and on the basis of the literature survey the overall Agile RE process is accumulated. Agile being a technique produces high quality software in relatively less time as compared to the conventional waterfall methodology. The paramount objective of this study is to take lessons from RE that Agile method may consider, if quality being the cardinal concern. The study is patterned on the survey of the previous research reported in the coexisting literature and the practices which are being pursued in the area.

show abstract

“…In the context of Scrum, the most popular agile method, requirement management is accomplished by maintaining the product backlog [7]. Therefore, to ensure a rapid delivery of business value to costumer, it is necessary to identify which requirements in this list must be developed first (ordering of requirements), i.e., to order the product backlog taking into account business and technical factors [6].…”

Section: Introductionmentioning

confidence: 99%

“…Moreover, ASD methods promotes the constant communication (e.g., face to face communication) and a development process open to changes [7]. Therefore, requirements are initially defined with customers, but are continuously refined [7].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Ordering the Product Backlog in Agile Software Development Projects: A Systematic Literature Review

Silva¹,

Araújo²,

Barbosa³

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Recently, agile software development methods have attracted the attention of academic and industrial domains. Unlike traditional approaches, agile methods focus on rapid delivery of business value to customers through fast delivery of working code. Therefore, requirement prioritization is considered a crucial process in this context, since there is the need to identify which requirements must be developed first, based on stakeholders preferences and taking into account business and technical challenges such as dependencies of tasks, developers skills, limitation of budget, etc. In Scrum, the most popular agile method, requirement management is done by maintaining the product backlog, which contains the list of functionalities that must be developed. Although some works conducted systematic reviews on the topic of agile requirement engineering, to the best of our knowledge, there is no study that reviewed the specific subject of ordering the product backlog in agile projects. Therefore, in this work, we conducted a Systematic Literature Review of studies on this topic published up to (and including) 2016 through a database search, to identify and analyze factors and techniques used to accomplish the task of ordering the product backlog in agile projects. In total, we evaluated 1556 papers, of which 13 reported on the subject of study.

show abstract

A systematic literature review on agile requirements engineering practices and challenges

Cited by 426 publications

References 52 publications

Agile Software Development Methodologies: Survey of Surveys

Agile Software Development Methodologies: Survey of Surveys

Quintessence of Traditional and Agile Requirement Engineering

Ordering the Product Backlog in Agile Software Development Projects: A Systematic Literature Review

Contact Info

Product

Resources

About