Agile Distributed Software Development in Nine Central European Teams:challenges, Benefits and Recommendations

Abstract

Although initially designed for co-located teams, agile methodologies promise mitigation to the challenges present in distributed software development with their demand for frequent communication. We examine the application of agile practices in software engineering teams with low geographical distribution in Austria and Germany. To gather insights on challenges and benefits faced by distributed teams we conduct interviews with eleven representatives and analyse the interview transcripts using the inductive category formation method. As a result, we identify four major challenges, such as technical obstructions or the impediments different language abilities have on communication, and four benefits, regarding collaboration and information radiation, that agile methods yield in distributed teams. Based on our analysis of challenges and benefits, we deduct seven recommendations to improve collaboration, overcome distance and avoid pitfalls. Key recommendations for teams with low geographical distance include that teams should get together at certain points to build relationships and trust and share information face-toface.

An Empirical Investigation of Geographically Distributed Agile Development: The Agile Enterprise Architecture is a Communication Enabler

“…The combination of geographically distributed development and industry-strength agile practices [1], [2], known as GDAD, seems to offer many benefits, such as low production cost, the opportunity to involve the most talented developers around the world, and faster time to market [3], [4]. GDAD refers to the agile development that includes teams and/or team members distributed over different locations [3], [5]. Accordingly, GDAD teams or team members can be locally distributed in different physical locations within the same country or can be globally distributed around the globe in different time zones or different countries [3], [6], [7].…”

A Critique on Task Allocation Processes in Distributed Agile Software Development

“…e inductive category method is applied to draw a conclusion from collected data. Challenges and recommendations are presented [69].…”

“…Seven recommendations related to challenges of communication, language, awareness, technology, and connectivity are described. Using practices and tools to radiate information, colocating the team regularly, providing channels and encouraging communication, planning for communication, preparing alternative communication strategies, adapting the process model, and sticking to the defined processes and practices are recommended to support DASD [69]. Different types of challenges such as different cultures having dissimilar methods to solve the same problems, lack of face to face communication, late instead of initial top-level design and incomplete high-level requirements becoming a cause of waste of resources and time, and poor tools and a poor environment leading to a poor project are presented.…”

Agile Software Development Techniques: A Survey

“…Several principles of the agile method exist, of which some are based on behavioural and some are based on managerial improvement for software development [24,25]. Agile software development methodologies are mainly concerned with code development rather than documents driven [26,27].…”