Agile requirements engineering practices and challenges: an empirical study

Information Systems Journal

Volumn 20, Issue 5, 2010, Pages 449-480

  Ramesh, Balasubramaniam ^a   Cao, Lan ^b   Baskerville, Richard ^b  

^a GEORGIA STATE UNIVERSITY   (United States)

^b OLD DOMINION UNIVERSITY   (United States)

Author keywords

Agile practices; Agile software development; Requirements engineering; Requirements engineering risks

Indexed keywords

AGILE DEVELOPMENT; AGILE PRACTICES; AGILE SOFTWARE DEVELOPMENT; ANALYSIS OF DATA; EMPIRICAL RESEARCH; EMPIRICAL STUDIES; NON-FUNCTIONAL REQUIREMENTS; PROJECT ENVIRONMENT; RISK FACTORS; SOFTWARE DEVELOPMENT ORGANIZATIONS;

ENGINEERING; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN;

RISKS;

EID: 77955396197     PISSN: 13501917     EISSN: 13652575     Source Type: Journal    
DOI: 10.1111/j.1365-2575.2007.00259.x     Document Type: Article

References (47)

1. Abdel-Hamid T, Madnick SE. Software Project Dynamics: An Integrated Approach. 1991, Prentice Hall, Englewood Cliffs, NJ, USA
2. 2001, http://www.agilealliance.com/, Agile Alliance., ) URL (last accessed 9 May 2006).
3. Araujo J, Ribeiro JC. 2005, ) Towards an aspect-oriented agile requirements approach. Eighth International Workshop on Principles of Software Evolution.
4. Astels D. Test Driven Development: A Practical Guide. 2003, Prentice Hall PTR, Upper Saddle River, NJ, USA
5. Barki H, Rivard S, Talbot J. Toward an assessment of software development risk. Journal of Management Information Systems 1993, 10:203-225.
6. Beck K. Test Driven Development: By Example. 2003, Addison-Wesley Professional, Boston, MA, USA
7. Beck K, Hannula J, Hendrickson C, Wells D, Mee R. Embracing change with extreme programming. IEEE Computer 1999, 32:70-77.
8. Boehm B. Requirements that handle IKIWISI, COTS, and rapid change. IEEE Computer 2000, 33:99-102.
9. Boehm B. Balancing Agility and Discipline: A Guide for the Perplexed. 2003, Addison-Wesley, Boston, MA, USA.
10. Cao L, Mohan K, Xu P, Ramesh B. 2004, ) How extreme does extreme programming have to be? Adapting XP practices to large-scale projects. Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04), Hawaii HI, USA.
11. Cockburn A. Agile software development. 2002, Addison-Wesley Longman, Boston, MA, USA.
12. Curtis B, Krasner H, Iscoe N. A field study of the software design process for large systems. Communications of the ACM 1988, 31:1268-1287.
13. Cusumano M, Yoffie D. Competing on Internet Time: Lessons from Netscape and Its Battle with Microsoft. 2000, Touchstone, New York, NY, USA
14. Davis G. Strategies for information requirements determination. IBM Systems Journal 1982, 21:4-31.
15. DeMarco T, Lister T. Risk management during requirements. IEEE Software 2003, 20:99-101.
16. Eisenhardt KM. Building theories from case study research. Academy of Management Review 1989, 14:532-550.
17. Erickson J, Lyytinen K, Siau K. Agile modeling, agile software development, and extreme programming: the state of research. Journal of Database Management 2005, 16:88-99.
18. Firesmith D. Prioritizing requirements. Journal of Object Technology 2004, 3:35-47.
19. Fowler M. Refactoring: Improving the Design of Existing Programs. 1999, Addison-Wesley, Boston, MA, USA.
20. Grünbacher P, Hofer C. 2002, ) Complementing XP with requirements negotiation, XP. Third International Conference on eXtreme Programming and Agile Software Process in Software Engineering, Alghero, Sarding, Italy, 26-29 May.
21. IEEE recommended practice for software requirements specifications. IEEE Standard 830 1998, IEEE
22. Jepsen O. 2002, ) Time constrained requirement engineering - the cooperative way International Workshop on Time-Constrained Requirements Engineering, Essen, Germany, 9 September.
23. Keil M, Carmel E. Customer-developer links in software development. Communications of the ACM 1995, 38:33-44.
24. Keil M, Cule PE, Lyytinen K. A framework for identifying software project risks. Communications of the ACM 1998, 41:76-83.
25. Kotonya G, Sommerville I. Requirements Engineering: Process and Techniques. 1998, John Wiley and Sons, New York, NY, USA
26. Kraut RE, Streeter LA. Coordination in software development. Communications of the ACM 1995, 38:69-81.
27. Lawrence B, Wiegers KE, Ebert C. The top risks of requirements engineering. IEEE Software 2001, 18:62-63.
28. Lee M. 2002, ) Just-in-time requirements analysis - the engine that drives the planning game, XP. Third International Conference on eXtreme Programming and Agile Software Process in Software Engineering, Alghero, Sarding, Italy, 26-29 May.
29. Levine L, Baskerville R, Loveland Link JL, Pries-Heje J, Ramesh B, Slaughter S. Software 2002, Engineering Institute, Pittsburgh, PA, USA
30. Lindvall M, Basili V, Boehm B, Costa P, Dangle K, Shull F. 2002, ) Empirical findings in agile methods, Second XP Universe and First Agile Universe Conference, Chicago, IL, USA, 4-7 August.
31. Lubars M, Potts C, Richter C. 1993, ) A review of the state of the practice in requirements modeling. IEEE International Symposium on Requirements Engineering.
32. Mason J. Qualitative Researching. 1996, Sage, London, UK
33. Merisalo-Rantanen H, Tuunanen T, Rossi M. Is extreme programming just old wine in new bottles: a comparison of two cases. Journal of Database Management 2005, 16:41-61.
34. Miles MB, Huberman AM. Qualitative Data Analysis: An Expanded Sourcebook. 1994, Sage Publications, Thousand Oaks, CA, USA
35. Nawrocki J, Jasinski M, Walter B, Wojciechowski A. 2002, ) Extreme programming modified: embrace requirements engineering practices. IEEE Joint International Conference on Requirements Engineering (RE′02), Essen, Germany.
36. Orlikowski W, Baroudi J. Studying information technology in organizations: research approaches and assumptions. Information Systems Research 1991, 2:1-28.
37. Orr K. Agile requirements: opportunity or oxymoron? IEEE Software 2004, 21:71-73.
38. Paetsch FEA, Maurer F. 2003, ) Requirements engineering and agile software development 12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises.
39. Pinheiro FAC. 2002, ) Requirements honesty 12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, Fachhochschule Mannheim, Germany.
40. Sabherwal R. The role of trust in outsourced is development projects. Communications of the ACM 1999, 42:80-86.
41. Schneider G, Winters JP. Applying Use Cases: A Practical Guide. 1998, Addison-Wesley, Boston, MA, USA
42. Sharp H, Robinson H. 2003, ) Customer collaboration: challenges and successes in practice: an agile development 2003 technical exchange. Agile Development Conference, Salt Lake, UT, USA.
43. Sillitti A, Ceschi M, Russo B, Succi G. 2005, ) Managing uncertainty in requirements: a survey in documentation-driven and agile companies. 11th IEEE International Symposium on Software Metrics.
44. Sommerville I, Sawyer P. Requirements Engineering: A Good Practice Guide. 1997, John Wiley & Sons, New York, NY, USA
45. Strauss A, Corbin J. Basics of Qualitative Research. Grounded Theory Procedures and Techniques. 1990, Sage Publications, Thousand Oaks, CA, USA
46. Turk D, France R, Rumpe B. Assumptions underlying agile software development process. Journal of Database Management 2005, 16:62-87.
47. Walz D, Elam J, Curtis B. Inside a software design team: knowledge acquisition, sharing and integration. Communications of the ACM 1993, 36:63-76.