The DOI matches its Crossref record; 30 of the 30 references it cites were found in a registry or an index.
Agile requirements engineering practices and challenges: an empirical study
Abstract
This paper describes empirical research into agile requirements engineering (RE) practices. Based on an analysis of data collected in 16 US software development organizations, we identify six agile practices. We also identify seven challenges that are created by the use of these practices. We further analyse how this collection of practices helps mitigate some, while exacerbating other risks in RE. We provide a framework for evaluating the impact and appropriateness of agile RE practices by relating them to RE risks. Two risks that are intractable by agile RE practices emerge from the analysis. First, problems with customer inability and a lack of concurrence among customers significantly impact agile development. Second, risks associated with the neglecting non‐functional requirements such as security and scalability are a serious concern. Developers should carefully evaluate the risk factors in their project environment to understand whether the benefits of agile RE practices outweigh the costs imposed by the challenges.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“Illustrating and communicating product requirements through a prototype reduces risks related to low requirements specification quality (Ramesh et al. 2010).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Ramesh et al. 2010
In the citing paper
“In particular, research shows that the use of production software in prototyping (rather than throw-away prototypes) incurs risks related to product quality such as scalability, security, and robustness (Ramesh et al. 2010).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Ramesh et al. 2010
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Qualitative Data Analysis: An Expanded Sourcebook
(1994) · Journal of Environmental Psychology · doi:10.1016/s0272-4944(05)80231-2 · Cited by 48,420
Basics of Qualitative Research: Grounded Theory Procedures and Techniques
Long, D. R., Strauss, A., & Corbin, J. (1993) · The Modern Language Journal · doi:10.2307/328955 · Cited by 17,576
Building Theories from Case Study Research
Eisenhardt, K. M. (1989) · The Academy of Management Review · doi:10.2307/258557 · Cited by 17,455
Delmont, S., & Mason, J. (1997) · The British Journal of Sociology · doi:10.2307/591613 · Cited by 4,262
Studying Information Technology in Organizations: Research Approaches and Assumptions
Orlikowski, W. J., & Baroudi, J. J. (1991) · Information Systems Research · doi:10.1287/isre.2.1.1 · Cited by 3,349
A field study of the software design process for large systems
Curtis, B., Krasner, H., & Iscoe, N. (1988) · Communications of the ACM · doi:10.1145/50087.50089 · Cited by 2,076
CYC: a large-scale investment in knowledge infrastructure
Lenat, D. B. (1995) · Communications of the ACM · doi:10.1145/219717.219745 · Cited by 1,946
Cockburn, A. (2001) · UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno · Cited by 1,858
Test Driven Development: By Example
Beck (2002) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 1,282
Requirements Engineering: A Good Practice Guide
Sommerville, I., & Sawyer, P. (1997) · Lancaster EPrints (Lancaster University) · Cited by 1,204
Balancing Agility and Discipline: A Guide for the Perplexed
Boehm, B. (2004) · Lecture Notes in Computer Science · doi:10.1007/978-3-540-24675-6_1 · Cited by 1,173
Coordination in software development
Kraut, R. E., & Streeter, L. A. (1995) · Communications of the ACM · doi:10.1145/203330.203345 · Cited by 1,080
Embracing change with extreme programming
Beck, K. (1999) · Computer · doi:10.1109/2.796139 · Cited by 979
Toward an Assessment of Software Development Risk
Barki, H., Rivard, S., & Talbot, J. (1993) · Journal of Management Information Systems · doi:10.1080/07421222.1993.11518006 · Cited by 717
A framework for identifying software project risks
Keil, M., Cule, P. E., Lyytinen, K., & Schmidt, R. C. (1998) · Communications of the ACM · doi:10.1145/287831.287843 · Cited by 698
Software project dynamics: an integrated approach
(1991) · Choice Reviews Online · doi:10.5860/choice.29-2147 · Cited by 668
Strategies for information requirements determination
Davis, G. B. (1982) · IBM Systems Journal · doi:10.1147/sj.211.0004 · Cited by 645
Inside a software design team: knowledge acquisition, sharing, and integration
Walz, D. B., Elam, J. J., & Curtis, B. (1993) · Communications of the ACM · doi:10.1145/163430.163447 · Cited by 520
The role of trust in outsourced IS development projects
Sabherwal, R. (1999) · Communications of the ACM · doi:10.1145/293411.293485 · Cited by 462
Applying Use Cases: A Practical Guide
Schneider, G., & Winters, J. P. (1998) · CERN Document Server (European Organization for Nuclear Research) · Cited by 334
IEEE Recommended Practice for Software Requirements Specifications
(1998) · doi:10.1109/ieeestd.1998.88286 · Cited by 332
Agile Modeling, Agile Software Development, and Extreme Programming
Erickson, J., Lyytinen, K., & Siau, K. L. (2005) · Journal of Database Management · doi:10.4018/jdm.2005100105 · Cited by 305
Customer-developer links in software development
Keil, M., & Carmel, E. (1995) · Communications of the ACM · doi:10.1145/203356.203363 · Cited by 291
Empirical Findings in Agile Methods
Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L., & Zelkowitz, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_19 · Cited by 276
(1998) · Cited by 267
Test Driven Development: A Practical Guide
Astels, D. (2003) · CERN Document Server (European Organization for Nuclear Research) · Cited by 221
Assumptions Underlying Agile Software-Development Processes
Turk, D., Robert, F., & Rumpe, B. (2005) · Journal of Database Management · doi:10.4018/jdm.2005100104 · Cited by 218
Requirements that handle IKIWISI, COTS, and rapid change
BOEHM, B. W. (2000) · Computer · doi:10.1109/2.869384 · Cited by 151
Is Extreme Programming Just Old Wine in New Bottles: A Comparison of Two Cases
Merisalo-Rantanen, H., Tuunanen, T., & Rossi, M. (2005) · Journal of Database Management · doi:10.4018/jdm.2005100103 · Cited by 82
Agile requirements: opportunity or oxymoron?
Orr, K. (2004) · IEEE Software · doi:10.1109/ms.2004.1293075 · Cited by 39
Research works printed but not linked: 17
- Araujo J.&Ribeiro J.C.(2005) Towards an aspect‐oriented agile requirements approach. Eighth International Workshop on Principles of Software Evolution.
- 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.
- 10.1109/MS.2003.1231163 · doi:10.1109/ms.2003.1231163
- 10.5381/jot.2004.3.8.c4 · doi:10.5381/jot.2004.3.8.c4
- Fowler M., 1999, Refactoring: Improving the Design of Existing Programs.
- 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.
- Jepsen O.(2002) Time constrained requirement engineering – the cooperative way International Workshop on Time‐Constrained Requirements Engineering Essen Germany 9 September.
- Kotonya G., 1998, Requirements Engineering: Process and Techniques.
- 10.1109/52.965804 · doi:10.1109/52.965804
- 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.
- Levine L., 2002, Software
- Lubars M. Potts C.&Richter C.(1993) A review of the state of the practice in requirements modeling. IEEE International Symposium on Requirements Engineering.
- 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.
- Paetsch F.E.A.&Maurer F.(2003) Requirements engineering and agile software development.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises.
- Pinheiro F.A.C.(2002) Requirements honesty.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises Fachhochschule Mannheim Germany.
- 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.
- 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.
Cited by
A systematic literature review on agile requirements engineering practices and challenges
Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. (2015) · Computers in Human Behavior · doi:10.1016/j.chb.2014.10.046 · Cited by 521
Agile Requirements Engineering: A systematic literature review
Schön, E.-M., Thomaschewski, J., & Escalona, M. J. (2017) · Computer Standards & Interfaces · doi:10.1016/j.csi.2016.08.011 · Cited by 359
When the Machine Meets the Expert: An Ethnography of Developing AI for Hiring
van den Broek, E., Sergeeva, A., & Huysman, M. (2021) · MIS Quarterly · doi:10.25300/misq/2021/16559 · Cited by 330
Challenges of shared decision-making: A multiple case study of agile software development
Moe, N. B., Aurum, A., & Dybå, T. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2011.11.006 · Cited by 205
A Mapping Study on Requirements Engineering in Agile Software Development
Heikkila, V. T., Damian, D., Lassenius, C., & Paasivaara, M. (2015) · 2015 41st Euromicro Conference on Software Engineering and Advanced Applications · doi:10.1109/seaa.2015.70 · Cited by 131
Metadata
- Authors
- Ramesh, B., Cao, L., & Baskerville, R.
- Venue
- Information Systems Journal
- Publisher
- Wiley
- Published
- 2010-08-05
- Volume
- 20
- Issue
- 5
- Pages
- 449-480
- ISSN
- 1350-1917 (ISSN-L)
- 1365-2575
- OpenAlex
- W1592034869
- Cited by
- 384
- References
- 30
- FWCI
- 5.32
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.