Agile software product lines: a systematic mapping study
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
Background: Software product lines and Agile methods have been an effective solution for dealing with the growing complexity of software and handling competitive needs of software organizations. They also share common goals, such as improving productivity, reducing time‐to‐market, decreasing development costs and increasing customer satisfaction. There has been growing interest in whether the integration of Agile and SPL could provide further benefits and solve many of the outstanding issues surrounding software development. Objective: This study investigates the state‐of‐the‐art in Agile SPL approaches, while identifying gaps in current research and synthesizing available evidence. It also provides a basis for a deeper understanding of the issues involved in the integration of Agile and SPL. Method: A mapping study was undertaken to analyze the relation between Agile and SPL methods. A set of four research questions were defined in which the 32 primary studies were evaluated. Results: This study provides insights into the integration of Agile and SPL approaches, it identifies the current gaps in the research, synthesize the available evidence and propose specific Agile methods and practices for integration in SPL. Conclusions: In general, few studies describe the underlying Agile principles being adopted by proposed Agile SPL solutions. The most common Agile practices proposed by the studies came from the XP and Scrum methods, particularly in the pro‐active SPL strategy. We identify certain Agile methods that are being overlooked by the Agile SPL community, and propose specific SPL practices areas suitable for adoption of Agile practices. Copyright © 2011 John Wiley & Sons, Ltd.
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
Systematic Mapping Studies in Software Engineering
Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008) · Electronic Workshops in Computing · doi:10.14236/ewic/ease2008.8 · Cited by 3,239 · cited 2×
“The idea of categorizing the studies was based on [ 9 ] .”
MethodEmpirical studies of agile software development: A systematic review
Dybå, T., & Dingsøyr, T. (2008) · Information and Software Technology · doi:10.1016/j.infsof.2008.01.006 · Cited by 2,668 · cited 2×
“The most popular Agile methods are XP, SCRUM, and TDD [ 49 ] .”
MethodBrereton, P., Kitchenham, B. A., Budgen, D., Turner, M., & Khalil, M. (2007) · Journal of Systems and Software · doi:10.1016/j.jss.2006.07.009 · Cited by 2,394 · cited 1×
“While Systematic Reviews (SR) are commonly [ 8, 10 ] applied to identify, evaluate, and compare all available research related to a particular research question, an MS intends to map out the research undertaken rather than to answer detailed research question [ 11 ] .”
BackgroundSynthesising qualitative and quantitative evidence: A review of possible methods
Dixon-Woods, M., Agarwal, S., Jones, D., Young, B., & Sutton, A. (2005) · Journal of Health Services Research & Policy · doi:10.1177/135581960501000110 · Cited by 2,132
Requirements engineering paper classification and evaluation criteria: a proposal and a discussion
Wieringa, R., Maiden, N., Mead, N., & Rolland, C. (2006) · Requirements Engineering · doi:10.1007/s00766-005-0021-6 · Cited by 940
Cited by
Guidelines for conducting systematic mapping studies in software engineering: An update
Petersen, K., Vakkalanka, S., & Kuzniarz, L. (2015) · Information and Software Technology · doi:10.1016/j.infsof.2015.03.007 · Cited by 2,669
Ampatzoglou, A., Bibi, S., Avgeriou, P., Verbeek, M., & Chatzigeorgiou, A. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.10.006 · Cited by 305
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
“Although the traditional approaches allow for iteration between the steps of the process [6], agile methods are based on the rapid iteration of the whole software development process from the elicitation of the requirements to the release of a new version of the software [2], [20], [21].”
Method
Metadata
- Authors
- da Silva, I. F., da Mota Silveira Neto, P. A., O'Leary, P., de Almeida, E. S., & de Lemos Meira, S. R.
- Venue
- Software: Practice and Experience
- Publisher
- Wiley
- Published
- 2011-05-03
- Volume
- 41
- Issue
- 8
- Pages
- 899-920
- ISSN
- 0038-0644 (ISSN-L)
- 1097-024X
- OpenAlex
- W2082734372
- Cited by
- 45
- References
- 5
- FWCI
- 12.95
- 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 software product lines: a systematic mapping study. https://app.cochat.ai/papers/10.1002/spe.1078
- The paper
- da Silva, I. F., da Mota Silveira Neto, P. A., O'Leary, P., de Almeida, E. S., & de Lemos Meira, S. R. (2011). Agile software product lines: a systematic mapping study. Software: Practice and Experience. https://doi.org/10.1002/spe.1078
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.