Evolution of Requirements Engineering in Agile Methodology – Literature Review

Zaveri, AA; Jaafar, J; Yafi, E; Sarama, S

Evolution of Requirements Engineering in Agile Methodology – Literature Review

Zaveri, AA Jaafar, J Yafi, E

Sarama, S

Permalink

Publisher:: Multimedia University
Publication Type:: Journal Article
Citation:: Journal of Engineering Technology and Applied Physics, 6, (2), pp. 57-65

Open Access

Copyright Clearance Process

Recently Added
In Progress
Open Access

This item is open access.

Adobe PDF

Download Accepted versionAdobe PDF (381.78 kB)

View on publisher's site

View statistics

Full metadata record

Field	Value	Language
dc.contributor.author	Zaveri, AA
dc.contributor.author	Jaafar, J
dc.contributor.author	Yafi, E https://orcid.org/0000-0002-3144-0784
dc.contributor.author	Sarama, S
dc.date.accessioned	2025-04-07T05:25:37Z
dc.date.available	2025-04-07T05:25:37Z
dc.identifier.citation	Journal of Engineering Technology and Applied Physics, 6, (2), pp. 57-65
dc.identifier.issn	2682-8383
dc.identifier.issn	2682-8383
dc.identifier.uri	http://hdl.handle.net/10453/186751
dc.description.abstract	<jats:p>Requirements Agile approaches have transformed engineering. This paper shows how RE in Agile software development has evolved from documentation-heavy to collaborative, adaptable, and customer-focused. Agile was born in the mid-1990s when the industry realized it needed to respond to changing client needs and market volatility. This evolution includes iterative development, client interaction, and emphasizing communication above documentation, as discussed in the paper. By comparing conventional and Agile RE approaches, we demonstrate the benefits of adapting to change, working with customers, and delivering functional software faster. This analysis provides a persuasive description of Agile RE implementation methodologies and resources through a detailed literature review and real-world experiences. User stories and backlog refinement are notable techniques. The research finishes by exploring how these techniques affect team dynamics, project success, and customer satisfaction. RE's Agile difficulties and opportunities are also examined. The findings illuminate RE methods' successful adaptation to Agile projects' dynamic character. Software development is more responsive and effective due to this adaptation.</jats:p>
dc.language	en
dc.publisher	Multimedia University
dc.relation.ispartof	Journal of Engineering Technology and Applied Physics
dc.relation.isbasedon	10.33093/jetap.2024.6.2.9
dc.rights	info:eu-repo/semantics/restrictedAccess
dc.title	Evolution of Requirements Engineering in Agile Methodology – Literature Review
dc.type	Journal Article
utslib.citation.volume	6
pubs.organisational-group	University of Technology Sydney
pubs.organisational-group	University of Technology Sydney/Faculty of Engineering and Information Technology
utslib.copyright.status	open_access	*
dc.date.updated	2025-04-07T05:25:36Z
pubs.issue	2
pubs.publication-status	Published online
pubs.volume	6
utslib.citation.issue	2

Abstract:

Requirements Agile approaches have transformed engineering. This paper shows how RE in Agile software development has evolved from documentation-heavy to collaborative, adaptable, and customer-focused. Agile was born in the mid-1990s when the industry realized it needed to respond to changing client needs and market volatility. This evolution includes iterative development, client interaction, and emphasizing communication above documentation, as discussed in the paper. By comparing conventional and Agile RE approaches, we demonstrate the benefits of adapting to change, working with customers, and delivering functional software faster. This analysis provides a persuasive description of Agile RE implementation methodologies and resources through a detailed literature review and real-world experiences. User stories and backlog refinement are notable techniques. The research finishes by exploring how these techniques affect team dynamics, project success, and customer satisfaction. RE's Agile difficulties and opportunities are also examined. The findings illuminate RE methods' successful adaptation to Agile projects' dynamic character. Software development is more responsive and effective due to this adaptation.

Please use this identifier to cite or link to this item:

http://hdl.handle.net/10453/186751