Bibliometric Analysis of Agile Software Development

Agile methodologies are currently considered one of the main paradigms of software development. Its study, from a scientific point of view, has deserved prominence in recent years by the scientific community related to the area of software engineering. This study intends to perform a bibliometric analysis of the quantity, characteristics and scope of the most relevant studies published in this area of knowledge. The findings indicate that the number of studies published from 2010 to 2016 significantly increased, having reached a peak in 2015. The study identifies the main journals and conferences in the field and we also concluded that the majority of published studies are literature reviews of agile software development, and qualitative and quantitative research methods have identical number of publications.

💡 Research Summary

**
The paper presents a comprehensive bibliometric study of Agile software development research covering the period from 2010 to 2016. Unlike many previous analyses that relied on Web of Science or Scopus and focused solely on journal articles and conference papers, the authors chose the INSPEC database, which indexes a broader spectrum of engineering and physics literature. This decision allowed them to capture a more diverse set of publications, including books and book chapters, thereby providing a richer view of the field’s evolution.

The methodology follows the guidelines of Royle et al. (2013) for bibliometric investigations and builds on the earlier work of Dingsøyr et al. (2012), which examined the growth of Agile publications from 2001 to 2010. The authors extended the previous two‑dimensional approach (journal articles vs. conference papers) by adding a third dimension—books. They searched INSPEC using five key terms that represent the most widely adopted Agile practices: “agile software development,” “scrum,” “extreme programming,” “test‑driven development,” and “Kanban software.” Duplicate records were removed to avoid double counting.

The quantitative results show a substantial increase of approximately 79.4 % in the total number of Agile‑related publications between 2010 and 2016, with a clear peak in 2015. The following year, 2016, experienced an 11.2 % decline, suggesting a short‑term saturation after the peak. Notably, the output of books and book chapters surged by about 223 % over the six‑year span, indicating a shift of scholarly attention toward more pedagogical and practitioner‑oriented formats.

Journal analysis reveals that IEEE Software is the leading outlet, publishing the highest number of Agile papers, followed by the International Journal of Production Research and Information and Software Technology. This distribution highlights the interdisciplinary nature of Agile, extending beyond classic software engineering into production and systems engineering domains. Conference contributions, while growing, remain secondary to journal publications in terms of volume.

Keyword analysis identifies “Agile,” “Software Engineering,” “Lean,” and “Requirements Engineering” as the most frequent terms, underscoring current research interests in the integration of Lean principles, the handling of requirements, and the broader software engineering context. Methodologically, the study finds an almost equal split between quantitative empirical studies and qualitative case‑based investigations. However, more than half of the examined works are literature reviews, suggesting that the field is still consolidating knowledge rather than generating extensive new empirical evidence.

Geographically, the United States, Canada, and Germany emerge as the most prolific contributors, consistent with earlier bibliometric surveys of software engineering. Nevertheless, the authors note a growing presence of researchers from non‑traditional regions such as Portugal and Brazil, reflecting the global diffusion of Agile practices.

In the discussion, the authors point out two main limitations of the current research landscape: (1) a lack of methodological diversity, with relatively few large‑scale longitudinal or controlled experiments, and (2) an over‑reliance on secondary analyses (reviews) rather than primary empirical data. To address these gaps, they propose several avenues for future work:

1. Conduct long‑term, data‑driven empirical studies that track Agile adoption outcomes across multiple organizations and domains.
2. Perform domain‑specific effectiveness analyses (e.g., healthcare, public sector, embedded systems) to understand contextual factors influencing Agile success.
3. Explore the integration of Agile with emerging development paradigms such as DevOps, MLOps, and continuous delivery pipelines.
4. Leverage the rapid growth of Agile‑related books to develop standardized curricula and practitioner guides that bridge the gap between academic research and industry practice.

Overall, the paper demonstrates that Agile software development has experienced robust scholarly growth, with a peak in 2015 and a notable expansion into book publications. While the field is vibrant, it remains in a consolidation phase, with a pressing need for more rigorous empirical investigations and interdisciplinary integration. The authors’ bibliometric framework provides a solid baseline for tracking future trends and for guiding researchers toward under‑explored methodological and topical areas.