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

doi:10.4018/978-1-7998-4165-4.ch007

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

Engineering Division (Great Valley)

Research output: Chapter in Book/Report/Conference proceeding › Chapter

Abstract

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 language	English (US)
Title of host publication	Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products
Publisher	IGI Global
Pages	130-150
Number of pages	21
ISBN (Electronic)	9781799841661
ISBN (Print)	9781799841654
DOIs	https://doi.org/10.4018/978-1-7998-4165-4.ch007
State	Published - Jul 10 2020

All Science Journal Classification (ASJC) codes

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

Access to Document

10.4018/978-1-7998-4165-4.ch007

Cite this

Albuquerque, D. W., Guimarães, E. T., Ramos, F. B. A., Costa, A. A. M., Gomes, A., Dantas, E., Perkusich, M., & Almeida, H. (2020). Disciplined or agile? Two approaches for handling requirement change management. In Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products (pp. 130-150). IGI Global. https://doi.org/10.4018/978-1-7998-4165-4.ch007

@inbook{7011f047bcaa4e058f9b229d1310f7c0,

title = "Disciplined or agile? Two approaches for handling requirement change management",

abstract = "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.",

author = "Albuquerque, {Danyllo Wagner} and Guimar{\~a}es, {Everton Tavares} and Ramos, {Felipe Barbosa Ara{\'u}jo} and Costa, {Antonio Alexandre Moura} and Alexandre Gomes and Emanuel Dantas and Mirko Perkusich and Hyggo Almeida",

year = "2020",

month = jul,

day = "10",

doi = "10.4018/978-1-7998-4165-4.ch007",

language = "English (US)",

isbn = "9781799841654",

pages = "130--150",

booktitle = "Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products",

publisher = "IGI Global",

}

Albuquerque, DW, Guimarães, ET, Ramos, FBA, Costa, AAM, Gomes, A, Dantas, E, Perkusich, M & Almeida, H 2020, Disciplined or agile? Two approaches for handling requirement change management. in Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products. IGI Global, pp. 130-150. https://doi.org/10.4018/978-1-7998-4165-4.ch007

Disciplined or agile? Two approaches for handling requirement change management. / Albuquerque, Danyllo Wagner; Guimarães, Everton Tavares; Ramos, Felipe Barbosa Araújo et al.
Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products. IGI Global, 2020. p. 130-150.

Research output: Chapter in Book/Report/Conference proceeding › Chapter

TY - CHAP

T1 - Disciplined or agile? Two approaches for handling requirement change management

AU - Albuquerque, Danyllo Wagner

AU - Guimarães, Everton Tavares

AU - Ramos, Felipe Barbosa Araújo

AU - Costa, Antonio Alexandre Moura

AU - Gomes, Alexandre

AU - Dantas, Emanuel

AU - Perkusich, Mirko

AU - Almeida, Hyggo

PY - 2020/7/10

Y1 - 2020/7/10

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=85128009053&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85128009053&partnerID=8YFLogxK

U2 - 10.4018/978-1-7998-4165-4.ch007

DO - 10.4018/978-1-7998-4165-4.ch007

M3 - Chapter

AN - SCOPUS:85128009053

SN - 9781799841654

SP - 130

EP - 150

BT - Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products

PB - IGI Global

ER -

Disciplined or agile? Two approaches for handling requirement change management

Abstract

All Science Journal Classification (ASJC) codes

Access to Document

Other files and links

Fingerprint

Cite this