research-article

A Faceted Taxonomy of Requirements Changes in Agile Contexts

Authors:

Kashumi Madampe,

John GrundyAuthors Info & Claims

IEEE Transactions on Software Engineering, Volume 48, Issue 10

Pages 3737 - 3752

https://doi.org/10.1109/TSE.2021.3104732

Published: 01 October 2022 Publication History

Abstract

<italic>Background:</italic> Originally, developers aimed to identify most software requirements upfront in software development projects. However, agile methods explicitly encourage software requirements to be changed throughout development, i.e., many Requirements Changes (RCs) occur. <italic>Objective:</italic> The objective of this study is to better understand RCs and produce a taxonomy of RCs in agile contexts. <italic>Method:</italic> We ran a mixed-methods approach comprising a series of studies: an interview-based study (10 participants from New Zealand and Australia), a focused literature review, and an in-depth survey (40 participants world-wide). <italic>Results:</italic> Key characteristics of RCs in agile we found relate to different <italic>types</italic> and <italic>forms</italic>, agile RCs have multiple <italic>reasons</italic> and <italic>sources</italic>, they are brought by different <italic>carriers</italic>, and their emergence in agile is via a variety of <italic>events.</italic> <italic>Summary:</italic> The presented taxonomy provides a guide for software practitioners to use to help manage RC-related issues in agile contexts.

References

[1]

IEEE Standard Glossary of Software Engineering Terminology, IEEE Standard 610.12–1990, 1990.

[2]

K. Becket al., “Manifesto for agile software development,” 2001.

[3]

R. Hoda, N. Salleh, and J. Grundy, “The rise and evolution of agile software development,” IEEE Softw., vol. 35, no. 5, pp. 58–63, Sep./Oct. 2018.

[4]

S. McGee and D. Greer, “A software requirements change source taxonomy,” in Proc. 4th Int. Conf. Softw. Eng. Advances, 2009, pp. 51–58.

[5]

S. McGee and D. Greer, “Software requirements change taxonomy: Evaluation by case study,” in Proc. IEEE 19th Int. Requirements Eng. Conf., 2011, pp. 25–34.

[6]

N. Nurmuliani, D. Zowghi, and S. Fowell, “Analysis of requirements volatility during software development life cycle,” in Proc. Australian Softw. Eng. Conf., 2004, pp. 28–37.

[7]

A. Inpirom and N. Prompoon, “Diagram change types taxonomy based on analysis and design models in UML,” in Proc. IEEE Int. Conf. Softw. Eng. Service Sci., 2013, pp. 283–287.

[8]

N. Saher, F. Baharom, and O. Ghazali, “Requirement change taxonomy and categorization in agile software development,” in Proc. 6th Int. Conf. Elect. Eng. Inform.: Sustain. Soc. Through Digital Innov., 2018, pp. 1–6.

[9]

P. Ralphet al., “Empirical standards for software engineering research,” 2020, arXiv:2010.03525.

[10]

A. Strauss and J. Corbin, Basics of Qualitative Research Techniques.Citeseer, 1998.

[11]

S. D. Harker, K. D. Eason, and J. E. Dobson, “The change and evolution of requirements as a challenge to the practice of software engineering,” in Proc. IEEE Int. Symp. Requirements Eng., 1993, pp. 266–272.

[12]

M. R. Basirati, H. Femmer, S. Eder, M. Fritzsche, and A. Widera, “Understanding changes in use cases: A case study,” in Proc. IEEE 23rd Int. Requirements Eng. Conf., 2015, pp. 352–361.

[13]

M. V. Mäntylä and C. Lassenius, “Drivers for software refactoring decisions,” in Proc. 5th ACM-IEEE Int. Symp. Empir. Softw. Eng., 2006, pp. 297–306.

[14]

B. A. Kitchenhamet al., “Preliminary guidelines for empirical research in software engineering,” IEEE Trans. Softw. Eng., vol. 28, no. 8, pp. 721–734, Aug. 2002.

Digital Library

[15]

B. A. Kitchenham and S. L. Pfleeger, “Personal opinion surveys,” in Guide to Advanced Empirical Software Engineering, London, U.K: Springer, 2008, pp. 63–92.

[16]

T. Punter, M. Ciolkowski, B. Freimut, and I. John, “Conducting on-line surveys in software engineering,” in Proc. Int. Symp. Empir. Softw. Eng., 2003, pp. 80–88.

[17]

E. Smith, R. Loftin, E. Murphy-Hill, C. Bird, and T. Zimmermann, “Improving developer participation rates in surveys,” in Proc. 6th Int. Workshop Cooperative Human Aspects Softw. Eng., 2013, pp. 89–92.

[18]

K. Madampe, R. Hoda, J. Grundy, and P. Singh, “Towards understanding technical responses to requirements changes in agile teams,” in Proc. IEEE/ACM 42nd Int. Conf. Softw. Eng. Workshops, 2020, Art. no.

[19]

F. Paetsch, A. Eberlein, and F. Maurer, “Requirements engineering and agile software development,” in Proc. Workshop Enabling Technologies: Infrastructure Collaborative Enterprises, 2003, pp. 308–313.

[20]

I. Gizzatullina, “Empirical study of customer communication problem in agile requirements engineering,” in Proc. 3rd EUROMICRO Conf. Softw. Eng. Advanced Appl., 2019, pp. 1262–1264.

[21]

N. N. B. Abdullah, S. Honiden, H. Sharp, B. Nuseibeh, and D. Notkin, “Communication patterns of agile requirements engineering,” in Proc. 1st Agile Requirements Eng. Workshop, 2011, pp. 1–4.

[22]

V. Stray, D. I. Sjøberg, and T. Dybå, “The daily stand-up meeting: A grounded theory study,” J. Syst. Softw., vol. 114, pp. 101–124, 2016.

Digital Library

[23]

R. Krishna, A. Agrawal, A. Rahman, A. Sobran, and T. Menzies, “What is the connection between issues, bugs, and enhancements?: Lessons learned from 800+ software projects,” in Proc. Int. Conf. Softw. Eng., 2018, pp. 306–315.

[24]

X. Wang, L. Zhao, Y. Wang, and J. Sun, “The role of requirements engineering practices in agile development: An empirical study,” Commun. Comput. Inf. Sci., Berlin, Germany: Springer, 2014, pp. 195–205.

[25]

G. Hoff, A. Fruhling, and K. Ward, “Requirement prioritization decision factors for agile development environments,” 2008.

[26]

R. Hoda, J. Noble, and S. Marshall, “Agile undercover: When customers don't collaborate,” in Lecture Notes in Business Information Processing, Berlin, Germany: Springer, 2010, pp. 73–87.

[27]

“14th Annual State of Agile Report | State of Agile”.

[28]

M. Pikkarainen, J. Haikara, O. Salo, P. Abrahamsson, and J. Still, “The impact of agile practices on communication in software development,” Empir. Softw. Eng., vol. 13, pp. 303–337, 2008.

Digital Library

[29]

L. Cao and B. Ramesh, “Agile requirements engineering practices: An empirical study,” IEEE Softw., vol. 25, pp. 60–67, Jan./Feb. 2008.

Digital Library

[30]

M. Gall, B. Bruegge, and B. Berenbach, “Towards a framework for real time requirements elicitation,” in Proc. 1st Int. Workshop Multimedia Requirements Enineering, 2006, p. 4.

[31]

I. R. McChesney and S. Gallagher, “Communication and co-ordination practices in software engineering projects,” Inf. Softw. Technol., vol. 46, pp. 473–489, 2004.

Cited By

Madampe KHoda RGrundy J(2024)Supporting Emotional Intelligence, Productivity and Team Goals while Handling Software Requirements ChangesACM Transactions on Software Engineering and Methodology10.1145/366460033:6(1-38)Online publication date: 27-Jun-2024
https://dl.acm.org/doi/10.1145/3664600
Madampe KHoda RGrundy J(2024)Addressing Bad Feelings in Agile Software Project Contexts: Considering Team Welfare and Developer Mental HealthIEEE Software10.1109/MS.2024.337770341:4(44-50)Online publication date: 21-Mar-2024
https://dl.acm.org/doi/10.1109/MS.2024.3377703
Pant AHoda RTantithamthavorn CTurhan B(2024)Ethics in AI through the practitioner’s view: a grounded theory literature reviewEmpirical Software Engineering10.1007/s10664-024-10465-529:3Online publication date: 6-May-2024
https://dl.acm.org/doi/10.1007/s10664-024-10465-5
Show More Cited By

Index Terms

A Faceted Taxonomy of Requirements Changes in Agile Contexts

Index terms have been assigned to the content through auto-classification.

Recommendations

A dependency taxonomy for agile software development projects

Agile software development is designed to achieve collaborative software development. A supporting pillar of collaboration is effective coordination, which is necessary to manage dependencies in projects. Understanding the dependencies arising in agile ...
The agile requirements refinery: Applying SCRUM principles to software product management

Context: Although agile software development methods such as SCRUM and DSDM are gaining popularity, the consequences of applying agile principles to software product management have received little attention until now. Objective: In this paper, this gap ...
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image IEEE Transactions on Software Engineering

IEEE Transactions on Software Engineering Volume 48, Issue 10

Oct. 2022

513 pages

ISSN:0098-5589

Issue’s Table of Contents

0098-5589 © 2021 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See https://www.ieee.org/publications/rights/index.html for more information.

Publisher

IEEE Press

Publication History

Published: 01 October 2022

Qualifiers

Research-article

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

6
Total Citations
View Citations
0
Total Downloads

Downloads (Last 12 months)0
Downloads (Last 6 weeks)0

Reflects downloads up to 24 Oct 2024

Other Metrics

View Author Metrics

Citations

Cited By

Madampe KHoda RGrundy J(2024)Supporting Emotional Intelligence, Productivity and Team Goals while Handling Software Requirements ChangesACM Transactions on Software Engineering and Methodology10.1145/366460033:6(1-38)Online publication date: 27-Jun-2024
https://dl.acm.org/doi/10.1145/3664600
Madampe KHoda RGrundy J(2024)Addressing Bad Feelings in Agile Software Project Contexts: Considering Team Welfare and Developer Mental HealthIEEE Software10.1109/MS.2024.337770341:4(44-50)Online publication date: 21-Mar-2024
https://dl.acm.org/doi/10.1109/MS.2024.3377703
Pant AHoda RTantithamthavorn CTurhan B(2024)Ethics in AI through the practitioner’s view: a grounded theory literature reviewEmpirical Software Engineering10.1007/s10664-024-10465-529:3Online publication date: 6-May-2024
https://dl.acm.org/doi/10.1007/s10664-024-10465-5
Madampe KHoda RGrundy J(2023)A Framework for Emotion-Oriented Requirements Change Handling in Agile Software EngineeringIEEE Transactions on Software Engineering10.1109/TSE.2023.325314549:5(3325-3343)Online publication date: 1-May-2023
https://dl.acm.org/doi/10.1109/TSE.2023.3253145
Madampe KHoda RGrundy J(2023)The Emotional Roller Coaster of Responding to Requirements Changes in Software EngineeringIEEE Transactions on Software Engineering10.1109/TSE.2022.317292549:3(1171-1187)Online publication date: 1-Mar-2023
https://dl.acm.org/doi/10.1109/TSE.2022.3172925
Hidellaarachchi DGrundy JHoda RMueller I(2023)The Impact of Personality on Requirements Engineering Activities: A Mixed-Methods StudyEmpirical Software Engineering10.1007/s10664-023-10426-429:1Online publication date: 28-Dec-2023
https://dl.acm.org/doi/10.1007/s10664-023-10426-4
Hidellaarachchi DGrundy JHoda RMueller I(2022)The Influence of Human Aspects on Requirements Engineering-related Activities: Software Practitioners’ PerspectiveACM Transactions on Software Engineering and Methodology10.1145/354694332:5(1-37)Online publication date: 6-Jul-2022
https://dl.acm.org/doi/10.1145/3546943

View Options

View options

Get Access

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

Media

Figures

Other

Tables

View Issue’s Table of Contents