Describing agile requirements development and communication using complex adaptive systems theory

Aaron Read, Gert Jan De Vreede, Robert O. Briggs

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Scopus citations

Abstract

Agile software development methods help software development teams respond to changing requirements. Fundamental to this ability to respond to change is the manner in which requirements are communicated and developed. The question of agile requirements development is considered through the lens of Complex Adaptive Systems theory, a theory used to explain agility in software development teams. A case study of the communication and development of requirements in a software development team is reported, where the three dimensions of CAS Theory described by Vidgen and Colleagues (Vidgen and Wang 2009) are adapted to describe requirements communication and development practices in greater detail. We find that this focus on requirements practices can further explain increases in a software team's agility.

Original languageEnglish (US)
Title of host publication18th Americas Conference on Information Systems 2012, AMCIS 2012
Pages2086-2093
Number of pages8
StatePublished - 2012
Event18th Americas Conference on Information Systems 2012, AMCIS 2012 - Seattle, WA, United States
Duration: Aug 9 2012Aug 12 2012

Publication series

Name18th Americas Conference on Information Systems 2012, AMCIS 2012
Volume3

Conference

Conference18th Americas Conference on Information Systems 2012, AMCIS 2012
Country/TerritoryUnited States
CitySeattle, WA
Period8/9/128/12/12

Keywords

  • Agile software development
  • Complex adaptive systems
  • User stories

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Computer Science Applications
  • Information Systems
  • Library and Information Sciences

Fingerprint

Dive into the research topics of 'Describing agile requirements development and communication using complex adaptive systems theory'. Together they form a unique fingerprint.

Cite this