A systematic review of distributed Agile software engineering

Abstract

The combination of Agile methods and distributed software development via remote teams represents an emerging approach to address the challenges such as late feedback, slow project timelines, and high cost, typically associated with software development projects. However, when projects are implemented using an Agile model with distributed human resources, there are a number of challenges that need to be considered and mitigated. The objectives of our work are multifold. First, we would like to understand the reasons and conditions that lead to the adoption of distributed Agile software engineering (DASE) practices. Second, we would like to investigate and find out the most important risks that threaten a DASE approach and what mitigation strategies exist to address them. Finally, we would like to highlight which of the available approaches among the existing Agile methodologies has been successfully adopted by the community. We intend to solidify our findings by exploring the strength of the evidence that has been reported in the literature. We carried out a systematic literature review of DASE techniques and approaches. This systematic literature review found time zone difference, knowledge of resources, lack of infrastructure, missing roles, and responsibilities as being the primary challenges that needed to be addressed. Copyright © 2015 John Wiley & Sons, Ltd.

Comparing Methods for Large-Scale Agile Software Development: A Systematic Literature Review

“…After removing duplicates, the titles and abstracts of the remaining articles were read. We identified 19 relevant systematic literature reviews in this area ( [4], [6], [7], [9], [17], [20], [21], [22], [23], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42]). By reading the titles of articles that cite these reviews, we identified three more relevant articles ( [18], [43], [44]).…”

The Changing Role of the Software Engineer

“…Agile based development is by design capable of reducing communication related delays and increasing discussion between software engineers, but it can also reduce the amount of documentation produced [19]. When working in geographically distributed teams, this may introduce challenges in communication since some remote communication, we suggest, may in fact benefit from documented artefacts.…”

Strengths and Weakness of Traditional and Agile Processes - A Systematic Review

“…Scrum software development is suitable for small projects and it becomes comparatively difficult to follow Scrum in large organizations. One of the main weaknesses of Scrum is reported in [23] that many employees in the software industry lack the knowledge of Scrum. They complete one simple course on Scrum and call themselves as Scrum masters.…”