Requirement change management challenges in GSD: An analytical hierarchy process approach

Muhammad Azeem Akbar, Arif Ali Khan*, Abdul Wahid Khan, Sajjad Mahmood

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

34 Scopus citations

Abstract

Majority of software development firms are adopting the concepts of global software development (GSD) in order to develop high-quality and low-cost products. However, the requirements change management (RCM) becomes a significant challenge in the GSD environment because of the unavailability of proper RCM framework and taxonomy. The objective of this study is to develop a taxonomy of the challenging factors of the RCM process in GSD. The taxonomy is developed based on the results of the data collected during the survey study and the implementation of the analytical hierarchy process (AHP). Total 25 challenging factors are identified and mapped into four core categories, ie, “organizational management,” “team,” “technology,” and “process.” Moreover, the AHP analysis is performed to prioritize the challenging factors and their categories. The prioritization process highlight that “process” is the most significant category of the RCM challenging factors. The taxonomy developed in this study provides a robust framework to tackle problems associated with RCM activities in GSD environment, which is significant to the success and progression of GSD firms.

Original languageEnglish
Article numbere2246
JournalJournal of software: Evolution and Process
Volume32
Issue number7
DOIs
StatePublished - 1 Jul 2020

Bibliographical note

Publisher Copyright:
© 2020 John Wiley & Sons, Ltd.

Keywords

  • analytic hierarchy process (AHP)
  • challenging factors
  • global software development (GSD)
  • requirements change management (RCM)

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Requirement change management challenges in GSD: An analytical hierarchy process approach'. Together they form a unique fingerprint.

Cite this