TL;DR
Agile Software Development (ASD) relies heavily on effective communication, yet a comprehensive understanding of its research landscape is lacking. This paper presents a mapping study of 14 relevant research papers to identify current research trends and pinpoint critical gaps in the area of communication within ASD.
What Problem Does This Paper Address?
The software industry is rapidly evolving, and Agile Software Development (ASD) has emerged as a dominant paradigm for delivering fast and efficient solutions. While ASD has been around for over two decades, there are still many unanswered questions, particularly concerning the crucial aspect of communication. Existing research has explored various facets of ASD communication, but there's a need for a structured overview to understand what has been studied, what the community is interested in, and where future research efforts should be directed. This paper aims to fill this gap by systematically mapping the existing literature on communication in ASD.
Methods
The authors conducted a systematic mapping study to identify and categorize research on communication in Agile Software Development. Their methodology involved:
- Literature Search: They searched major digital libraries (IEEE, ACM, Google Scholar) using relevant keywords.
- Initial Screening: Titles and abstracts of the retrieved articles were scanned.
- Relevance Filtering: Based on initial scans and sorting by relevance, they selected a subset of papers.
- Quality Assessment: The selected papers were evaluated against quality attributes, including publication year (excluding studies before 2013), clarity of evidence, and venue.
- Full-Text Review: A final manual review of the remaining papers was performed to determine the final set of 14 studies included in the analysis.
Datasets
Not discussed in the paper. The study is a systematic review of existing literature, not an empirical study that relies on specific datasets for training or evaluation.
Key Insights and Ideas
- Communication is Central to ASD: The paper reinforces that communication and coordination are fundamental to the success of any software project, especially within the agile framework.
- ASD's Shift from Traditional Methods: Agile methods aim to move away from traditional, rigid approaches like extensive documentation and predefined processes, favoring more collaborative and feedback-driven interactions.
- Challenges Remain: Despite the benefits of agile, challenges persist, particularly in large-scale settings involving multiple teams and in bridging geographical distances.
- Need for a Structured Overview: The authors highlight the lack of existing mapping studies that provide a consolidated view of research on ASD communication, motivating their work.
Key Results
The study identified 14 relevant papers and analyzed their research goals. The findings indicate that:
- Dominant Research Areas: The majority of studies focused on:
- Challenges in ASD Communication: 42% of the studies addressed communication challenges.
- Impact of Communication in ASD: 28% of the studies explored the impact of communication.
- Role of Communication in ASD: Less than 20% of studies investigated the role of communication.
- Specific Focus Areas: A smaller percentage of studies delved into specific aspects like interpersonal communication in distributed teams, customer communication for requirements engineering, and communication factors for speed and reuse in large-scale ASD.
- Research Gaps Identified: The authors suggest that while challenges, impact, and role of communication have been explored, there are significant research gaps in areas such as:
- Communication between and among ASD teams.
- Communication between all stakeholders of a project.
- Communication between development, testing, and operations teams (DevOps).
- Communication in scaled agile environments has not been explored in detail.
Limitations and Future Work
Limitations:
- Publication Year Bias: The study focused on papers from 2013 onwards, acknowledging that this choice was based on experience with scaled agile literature but could be considered arbitrary.
- Search String Limitations: The vast number of initial search results meant that the authors relied on sorting by relevance and reviewing a limited number of pages, potentially missing some relevant studies.
- Reviewer Scope: The study was performed by a PhD student with a single secondary reviewer, suggesting that a larger review team might have yielded different results.
Future Work:
The authors emphasize that the identified research gaps represent potential future work. They call for the community to actively pursue these avenues to gain a better understanding of ASD. Specifically, they recommend:
- Investigating communication between different ASD teams and across all project stakeholders.
- Exploring communication dynamics in DevOps environments.
- Conducting rigorous primary studies on ASD at scale, as factors like communication and coordination are likely to change significantly in larger, distributed agile contexts.
Summary updated