2017 6th International Conference on Electrical Engineering and Informatics (ICEEI) 2017
DOI: 10.1109/iceei.2017.8312441
|View full text |Cite
|
Sign up to set email alerts
|

Requirement change taxonomy and categorization in agile software development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 17 publications
0
6
0
Order By: Relevance
“…Saher et al present a taxonomy for requirement changes in the context of agile software development [20]. The authors present a categorization of elements of requirement changes in order to be able to propose a model for the management of requirements changes in agile software development projects.…”
Section: Related Workmentioning
confidence: 99%
“…Saher et al present a taxonomy for requirement changes in the context of agile software development [20]. The authors present a categorization of elements of requirement changes in order to be able to propose a model for the management of requirements changes in agile software development projects.…”
Section: Related Workmentioning
confidence: 99%
“…Unsurprisingly, as noted in literature relevant to ARCM, the identification and validation of the need for change is important prior to initiating the development process. Akbar et al [8] and Saher et al [18] have also highlighted the significance of the identification and validation process in ARCM. We mapped the investigated factors for both organisation types by considering the mapping model proposed by Khan et al [47] and Akbar et al [8].…”
Section: Organisation-type-based Analysismentioning
confidence: 99%
“…Apart from the abovementioned advantages, GSD firms also face several limitations, particularly with regard to implementing ARCM activities [18]. Since these activities are based on communication and coordination, the geographical distance between offshore sites results in the lack of effective and efficient communication and coordination [19].…”
Section: Introductionmentioning
confidence: 99%
“…Bano et al [21] reported the causes of requirement change and classified them into two categories as accidental and essential. For better understanding, McGee and Greer [22] used a taxonomy, and Saher et al [23] categorized the causes of requirement change factors into reason and change of origin. Agile requirement in large scale is presented in [24] and analysis and management of conflicts between team are described in [25].…”
Section: Introductionmentioning
confidence: 99%