Scaling agile methods to regulated environments: an industry case study
Open accessThe DOI matches its OpenAlex record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
Abstract—Agile development methods are growing in popu-larity with a recent survey reporting that more than 80 % of organizations now following an agile approach. Agile methods were seen initially as best suited to small, co-located teams developing non-critical systems. The first two constraining char-acteristics (small and co-located teams) have been addressed as research has emerged describing successful agile adoption involving large teams and distributed contexts. However, the applicability of agile methods for developing safety-critical sys-tems in regulated environments has not yet been demonstrated unequivocally, and very little rigorous research exists in this area. Some of the essential characteristics of agile approaches appear to be incompatible with the constraints imposed by regulated environments. In this study we identify these tension points and illustrate through a detailed case study how an agile approach was implemented successfully in a regulated environment. Among the interesting concepts to emerge from the research are the notions of continuous compliance and living traceability. Index Terms—Agile methods, regulated environments, Scrum, case study. I.
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
Determining Validity in Qualitative Inquiry
Creswell, J. W., & Miller, D. L. (2000) · Theory Into Practice · doi:10.1207/s15430421tip3903_2 · Cited by 9,184
Boland, D. (2004) · "Third International Workshop on Global Software Development (GSD 2004)" W12S Workshop - 26th International Conference on Software Engineering · doi:10.1049/ic:20040303 · Cited by 50
Cited by
Continuous software engineering: A roadmap and agenda
Fitzgerald, B., & Stol, K.-J. (2017) · Journal of Systems and Software · doi:10.1016/j.jss.2015.06.063 · Cited by 723
Self-citationUsage, costs, and benefits of continuous integration in open-source projects
Hilton, M., Tunnell, T., Huang, K., Marinov, D., & Dig, D. (2016) · Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2970276.2970358 · Cited by 342
Requirements engineering challenges and practices in large-scale agile system development
Kasauli, R., Knauss, E., Horkoff, J., Liebel, G., & de Oliveira Neto, F. G. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2020.110851 · Cited by 224
Continuous software engineering and beyond: trends and challenges
Fitzgerald, B., & Stol, K.-J. (2014) · Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering · doi:10.1145/2593812.2593813 · Cited by 212
Self-citationTwo's company, three's a crowd: a case study of crowdsourcing software development
Stol, K.-J., & Fitzgerald, B. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568249 · Cited by 203
Self-citation
Metadata
- Authors
- Fitzgerald, B. F., Stol, K.-J., O'Sullivan, R., & O’Brien, D.
- Venue
- University of Limerick Institutional Repository (University of Limerick)
- Publisher
- University of Limerick
- Published
- 2013-05-18
- Pages
- 863-872
- DOI
- 10.5555/2486788.2486906
- OpenAlex
- W2121016257
- Cited by
- 124
- References
- 2
- FWCI
- 13.72
- Type
- conference paper
- Language
- en
- Open access
- green
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.