The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.03 - May/June (2010 vol.27)
pp: 87-88
Neil Maiden , City University London
ABSTRACT
This column looks at agile techniques in requirements processes, summarizes their successes and failures so far, and proposes that we re-consider our use of electronic documentation in requirements projects
INDEX TERMS
Requirements, agile techniques, requirements documentation
CITATION
Neil Maiden, "Agile Requirements", IEEE Software, vol.27, no. 3, pp. 87-88, May/June 2010, doi:10.1109/MS.2010.67
REFERENCES
1. L. Cao and B. Ramesh, "Agile Requirements Engineering Practices: An Empirical Study," IEEE Software, vol. 25, no. 1, 2008, pp. 60–67.
2. N. Maiden, S. Robertson, and A. Gizikis, "Provoking Creativity: Imagine What Your Requirements Could Be Like," IEEE Software, vol. 21, no. 5, 2004, pp. 68–75.
3. M.R. Cook, "Creative Requirements Conversations," IEEE Software, vol. 27, no. 2, 2010, pp. 90–91.
4. "Information Spaces for Collaborative Creativity," Joint Information Systems Committee, 2010; www.jisc.ac.uk/whatwedo/programmes/elearning/ curriculumdeliveryinformationcreativity.aspx.
6 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool