The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January/February (2008 vol.25)
pp: 60-67
Lan Cao , Old Dominion University
Balasubramaniam Ramesh , Georgia State University
ABSTRACT
An analysis of data from 16 software development organizations reveals seven agile requirements-engineering practices, along with their benefits and challenges. These practices include face-to-face communication, iterative RE, extreme prioritization, constant planning, prototyping, test-driven development, and reviews and tests.
INDEX TERMS
requirements engineering, agile software development
CITATION
Lan Cao, Balasubramaniam Ramesh, "Agile Requirements Engineering Practices: An Empirical Study", IEEE Software, vol.25, no. 1, pp. 60-67, January/February 2008, doi:10.1109/MS.2008.1
REFERENCES
1. B. Boehm, "Requirements That Handle IKIWISI, COTS, and Rapid Change," Computer, July 2000, pp. 99–102.
2. J. Erickson, K. Lyytinen, and K. Siau, "Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research," J. Database Management, vol. 16, no. 4, 2005, pp. 88–99.
3. C.B. Seaman, "Qualitative Methods in Empirical Studies of Software Engineering," IEEE Trans. Software Eng., vol. 25, no. 4, 1999, pp. 557–572.
4. A. Strauss and J. Corbin, Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory, Sage Publications, 1990.
25 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool