Disciplined or agile? Two approaches for handling requirement change management

Danyllo Wagner Albuquerque, Everton Tavares Guimarães, Felipe Barbosa Araújo Ramos, Antonio Alexandre Moura Costa, Alexandre Gomes, Emanuel Dantas, Mirko Perkusich, Hyggo Almeida

Research output: Chapter in Book/Report/Conference proceedingChapter


Software requirements changes become necessary due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous studies have shown that failing to manage software requirements changes well is a main contributor to project failure. Given the importance of the subject, there is a plethora of efforts in academia and industry that discuss the management of requirements change in various directions, ways, and means. This chapter provided information about the current state-of-the-art approaches (i.e., Disciplined or Agile) for RCM and the research gaps in existing work. Benefits, risks, and difficulties associated with RCM are also made available to software practitioners who will be in a position of making better decisions on activities related to RCM. Better decisions can lead to better planning, which will increase the chance of project success.

Original languageEnglish (US)
Title of host publicationBalancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products
PublisherIGI Global
Number of pages21
ISBN (Electronic)9781799841661
ISBN (Print)9781799841654
StatePublished - Jul 10 2020

All Science Journal Classification (ASJC) codes

  • General Computer Science
  • General Economics, Econometrics and Finance
  • General Business, Management and Accounting


Dive into the research topics of 'Disciplined or agile? Two approaches for handling requirement change management'. Together they form a unique fingerprint.

Cite this