Geographical Distance Challenges in Distributed Agile Software Development: Case Study of a Global Company

Kahya, Murat Dogus; Şeneler, Çağla

doi:10.1109/ubmk.2018.8566591

Cited by 19 publications

(11 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Other studies have examined the challenges of Agile software development when teams are dispersed geographically and temporally. [25]. By leveraging a global workforce, distributed software development (DSD) efforts are increasingly found in both large and small companies, including the RELX companies Elsevier and LexisNexis.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Agile Software Development during the COVID-19 Pandemic: A Technology Company Survey

Schmidt¹,

Gutfreund²

2022

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

A common baseline is that Agile-based software development is conducted by co-located teams working in well-equipped office workspaces. The COVID-19 pandemic and subsequent lockdowns have cast new light on those assumptions. Suddenly, developers were no longer co-located with their teams and their well-equipped workspaces were vacant. How did the lockdowns, and the speed in which they were implemented, affect developers and development efforts? Did the lockdowns lead to diminished product quality? How was employee productivity impacted? A survey questionnaire was created to answer these questions.

show abstract

Section: Discussionmentioning

confidence: 99%

“…DSD introduces new challenges, including navigating socio-cultural norms [25] and establishing trust [26]. Bose [27] analyzed twelve different companies to understand how their distributed Agile software efforts fared with workplace challenges including communication, culture, and trust.…”

Section: Discussionmentioning

confidence: 99%

Agile Software Development during the COVID-19 Pandemic: A Technology Company Survey

Schmidt¹,

Gutfreund²

2022

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

show abstract

“…Der Großteil der Artikel sind Fallstudienberichte (17), gefolgt von Praxisberichten (11) und Literaturanalysen (8). Der Rest (4) sind Studien anderer Art wie etwa als "deskriptive Studien" bezeichnete Untersuchungen.…”

Section: Methode Der Literaturrechercheunclassified

Problembereiche verteilter agiler Teams: Literaturanalyse und Praxisimplikationen

Haslinger

Sikora

Riedl

2020

HMD

View full text Add to dashboard Cite

Zusammenfassung Seit Bestehen des Agilen Manifests 2001 bildeten sich vermehrt agile Softwareentwicklungs-Teams, die sich in Aufbau und Funktionsweise voneinander unterscheiden. Viele dieser Teams verteilen sich auf mehrere Standorte. Der Grad der Verteilung kann dabei von „in unterschiedlichen Gebäuden auf einem Firmengelände“ bis hin zu „anderer Kontinent“ reichen. Da das Agile Manifest auf stetige informelle Kommunikation (kurze, unbürokratische Wege) und vergleichsweise wenig Dokumentation setzt, sind bei verteilten Teams Schwierigkeiten und Probleme zu erwarten, wenn die Werte des Manifests konsequent verfolgt werden. Ein verteiltes Softwareentwicklungs-Projekt birgt an sich bereits Risiken (z. B. im Wissenstransfer zwischen den Entwicklern), wobei bei einem verteilten agilen Projekt zusätzliche Probleme auftreten können. Die Fachliteratur befasst sich seit rund 15 Jahren mit dieser Problematik. Befunde empirischer Studien beschreiben verschiedene Problembereiche; zudem werden Lösungswege erläutert. Im gegenständlichen Beitrag wird der aktuelle Stand der Literatur analysiert, um die wichtigsten Problembereiche herauszuarbeiten. Die Beschreibung dieser Problembereiche hilft insbesondere Handlungs- und Entscheidungsträgern in der Praxis, potenzielle Schwierigkeiten verteilter agiler Teams zu erkennen. Dies ist eine wesentliche Grundlage für proaktives Management, um die möglichen negativen Wirkungen zu vermeiden.

show abstract

“…The findings demonstrate that the introduced decision support system provides support in the decision-making process in assessing risks and selecting a control strategy. [7] identified by conducting an empirical study at five various projects of an enterprise and the geographical distance challenges in distributed software development. As a result, it was stated that geographical distancebased challenges constitute risks for communication, coordination, and control process in distributed software development.…”

Section: Related Workmentioning

confidence: 99%

Analysis of Risk Factors in the Scope of Distributed Software Team Structure

Şahin¹,

Dinler²,

Abualigah³

2021

European Journal of Science and Technology

View full text Add to dashboard Cite

The distributed software team structure represents a development type ensuring that team members are located in different remote sites through the life cycle of the software. Hence, it forms a network of distant sub-teams. Nowadays, the development of software projects with geographically distant groups forces software development environments to be flexible. It is of great importance for these software managers to organize and manage their distributed team management well. A higher number of stakeholders are brought to the scene of software projects by the trend of the distributed teams throughout countries and zones. Whereas risk management is the most significant assurance to obtain the project's expected outcome, the said processes must be considered as the shared responsibilities and commitment of the stakeholders taking part in the project from each site. The development of software 'in-house' leads to a number of risks. At the same time, its development partially in another geography causes the exponential multiplication of the risks in question. The management of risks must start at the early project stages and proceed in the form of a monitoring and follow-up effort during the projects' life cycle. In scope of this paper, the process steps developed to be carried out in accordance with Capability Maturity Model Integration (CMMI), instead of the traditional project method approach of the main risk factors in the distributed team structure are explained in detail. Also, the current study aimed to reveal the components taking part in the process of risk management regarding distributed software development.

show abstract

Geographical Distance Challenges in Distributed Agile Software Development: Case Study of a Global Company

Cited by 19 publications

References 14 publications

Agile Software Development during the COVID-19 Pandemic: A Technology Company Survey

Agile Software Development during the COVID-19 Pandemic: A Technology Company Survey

Problembereiche verteilter agiler Teams: Literaturanalyse und Praxisimplikationen

Analysis of Risk Factors in the Scope of Distributed Software Team Structure

Contact Info

Product

Resources

About