Empirical Findings in Agile Methods
The DOI matches its Crossref record; 18 of the 18 references it cites were found in a registry or an index.
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.
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
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
Agile Software Development with SCRUM
Schwaber, K., & Beedle, M. (2001) · Cited by 2,656
Refactoring improving the design of existing code
Saca, M. A. (2017) · 2017 IEEE 37th Central America and Panama Convention (CONCAPAN XXXVII) · doi:10.1109/concapan.2017.8278488 · Cited by 2,054
Cockburn, A. (2001) · UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno · Cited by 1,858
Agile software development: the business of innovation
Highsmith, J., & Cockburn, A. (2001) · Computer · doi:10.1109/2.947100 · Cited by 1,211
Agile Software Development Ecosystems
Highsmith, J. (2002) · International Linear Collider · Cited by 1,194
Agile software development, the people factor
Cockburn, A., & Highsmith, J. (2001) · Computer · doi:10.1109/2.963450 · Cited by 1,097
A discipline for software engineering
(1995) · Control Engineering Practice · doi:10.1016/0967-0661(95)90062-4 · Cited by 1,018
Get ready for agile methods, with care
Boehm, B. (2002) · Computer · doi:10.1109/2.976920 · Cited by 902
Self-citation
Cited by
Does Agile work? — A quantitative analysis of agile project success
Serrador, P., & Pinto, J. K. (2015) · International Journal of Project Management · doi:10.1016/j.ijproman.2015.01.006 · Cited by 844
Agile requirements engineering practices and challenges: an empirical study
Ramesh, B., Cao, L., & Baskerville, R. (2010) · Information Systems Journal · doi:10.1111/j.1365-2575.2007.00259.x · Cited by 384
Identifying some important success factors in adopting agile software development practices
Misra, S. C., Kumar, V., & Kumar, U. (2009) · Journal of Systems and Software · doi:10.1016/j.jss.2009.05.052 · Cited by 382
Self-Organizing Roles on Agile Software Development Teams
Hoda, R., Noble, J., & Marshall, S. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.30 · Cited by 330
A study of the documentation essential to software maintenance
de Souza, S. C. B., Anquetil, N., & de Oliveira, K. M. (2005) · Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information · doi:10.1145/1085313.1085331 · Cited by 305
Sabharwal, N., Rathore, R., & Agrawal, U. (2022) · Hands-On Guide to AgileOps · doi:10.1007/978-1-4842-7505-4_5 · Cited by 254
Do Agile Managed Information Systems Projects Fail Due to a Lack of Emotional Intelligence?
Luong, T. T., Sivarajah, U., & Weerakkody, V. (2021) · Information Systems Frontiers · doi:10.1007/s10796-019-09962-6 · Cited by 45
“…in the scholarly literature (Cockburn and Highsmith 2001; Boehm and Turner 2005; Moe et al. 2012; Fortmann 2018; Cram 2019) and it has been repeatedly identified as critical success factor for ADM managed projects (Lindvall et al. 2002; Chow and Cao 2008; Pedersen 2013; Kalenda et al. 2018).”
BackgroundAltuwaijri, F. S., & Ferrario, M. A. (2022) · Journal of Systems and Software · doi:10.1016/j.jss.2022.111347 · Cited by 37
Metadata
- Authors
- Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L., & Zelkowitz, M.
- Venue
- Lecture Notes in Computer Science
- Publisher
- Springer Berlin Heidelberg
- Published
- 2002
- Pages
- 197-207
- ISSN
- 0302-9743 (ISSN-L)
- OpenAlex
- W2028810660
- Cited by
- 276
- References
- 18
- FWCI
- 6.63
- Type
- conference paper
- 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.