Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 384

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

Ramesh, Balasubramaniam, Cao, Lan, Baskerville, Richard·2010·Information Systems Journal

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.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1111/j.1365-2575.2007.00259.x

Cites

30 of 30 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

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

Show all 30 references

Research works printed but not linked: 17

  1. Araujo J.&Ribeiro J.C.(2005) Towards an aspect‐oriented agile requirements approach. Eighth International Workshop on Principles of Software Evolution.
  2. 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.
  3. 10.1109/MS.2003.1231163 · doi:10.1109/ms.2003.1231163
  4. 10.5381/jot.2004.3.8.c4 · doi:10.5381/jot.2004.3.8.c4
  5. Fowler M., 1999, Refactoring: Improving the Design of Existing Programs.
  6. 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.
  7. Jepsen O.(2002) Time constrained requirement engineering – the cooperative way International Workshop on Time‐Constrained Requirements Engineering Essen Germany 9 September.
  8. Kotonya G., 1998, Requirements Engineering: Process and Techniques.
  9. 10.1109/52.965804 · doi:10.1109/52.965804
  10. 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.
  11. Levine L., 2002, Software
  12. Lubars M. Potts C.&Richter C.(1993) A review of the state of the practice in requirements modeling. IEEE International Symposium on Requirements Engineering.
  13. 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.
  14. Paetsch F.E.A.&Maurer F.(2003) Requirements engineering and agile software development.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises.
  15. Pinheiro F.A.C.(2002) Requirements honesty.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises Fachhochschule Mannheim Germany.
  16. 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.
  17. 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

See all 384

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

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Agile requirements engineering practices and challenges: an empirical study. https://app.cochat.ai/papers/10.1111/j.1365-2575.2007.00259.x
The paper
Ramesh, B., Cao, L., & Baskerville, R. (2010). Agile requirements engineering practices and challenges: an empirical study. Information Systems Journal. https://doi.org/10.1111/j.1365-2575.2007.00259.x

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.