A faceted taxonomy of Requirements Changes in agile contexts

Research output: Contribution to journalArticleResearchpeer-review

11 Citations (Scopus)


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. <b>Objective:</b> The objective of this study is to better understand RCs and produce a taxonomy of RCs in agile contexts. <b>Method:</b> 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). <b>Results:</b> Key characteristics of RCs in agile we found relate to different <i>types</i> and <i>forms</i>, agile RCs have multiple <i>reasons</i> and <i>sources</i>, they are brought by different <i>carriers</i>, and their emergence in agile is via a variety of <i>events.</i> <b>Summary:</b> The presented taxonomy provides a guide for software practitioners to use to help manage RC-related issues in agile contexts.

Original languageEnglish
Pages (from-to)3737-3752
Number of pages16
JournalIEEE Transactions on Software Engineering
Issue number10
Publication statusPublished - 1 Oct 2022


  • agile software development
  • Australia
  • Bibliographies
  • Computer bugs
  • Interviews
  • requirements changes
  • requirements engineering
  • Software
  • Software engineering
  • software engineering
  • Taxonomy
  • taxonomy

Cite this