Challenges When Using Scrum in Globally Distributed Teams

The interest of companies towards using agile approaches in GSD projects is growing at a rapid pace. On that note, it is extremely vital to consider the challenging factors involved in agile practices such as scrum in GSD projects. However, the remarkable and effective attempts towards precisely identify, synthesize and report the literature on agile practices for GSD projects have always been inadequate (Hossain, AliBabar & Young Paik, 2009). With the purpose of encouraging research committee to explore and analyze the projects that implements scrum process in globally distributed environment, the thesis paper places great emphasis on challenges involved with the implementation of agile methodologies with scrum framework in Global Software Development. In order to thoroughly understand these challenges, the thesis paper also addresses the core characteristics of a scrum team, benefits of scrum framework and the nature of Global Software Development projects. Moreover, through the qualitative data collection approach the mythology section of this thesis will in designing the further sections of this thesis. In accordance with the selected data collection approach, the result section focuses on the communication challenges as well as gathers the bunch of information through the interviews of two professionals working in the scrum projects with GSD settings. Going forward, the discussion section talks about the lessons learned and solutions to alleviate the challenges associated with distributed scrum projects

Customising software products in distributed software development a model for allocating customisation requirements across organisational boundaries

Requirements engineering plays a vital role in the software development process. While it is difficult to manage those requirements locally, it is even more difficult to communicate those requirements over organisational boundaries and to convey them to multiple distribution customers. This paper discusses the requirements of multiple distribution customers empirically in the context of customised software products. The main purpose is to understand the challenges of communicating and allocating customisation requirements across distributed organisational boundaries. We conducted an empirical survey with 19 practitioners, which confirmed that communicating customisation requirements in a DSD context is a significant challenge. We therefore propose a model for allocating customisation requirements between a local, customer-based agile team and a distributed development team that uses a traditional development approach. Our conjecture is that the model would reduce the challenge of communicating requirements across organisational boundaries, address customers’ requirements and provide a focus for future empirical studies

Learning From the Case Studies, How Global Software Development Process is Executed in an Agile Method Environment

. The biggest challenge in Global Software Development (GSD) is the efficiency of time to develop. GSD provides a guidance to use the process along with up-front analysis method like unified process or waterfall method. Although, it gives a benefit through comprehensive documentation and its clearness, it gives inhibits the organization which wants use GSD but in a rush. Agile methods claim an efficient and the effective approach to software development. This paper reports on how organizations combine the GSD process with agile methods like eXtreme Programming (XP), Scrum, Agile Unified Process (Agile UP), Feature Driven Development (FDD), and Microsoft Solution Framework Agile (MSF Agile). The paper uses case study to get organization experiences and describe useful practices for the organization that want to implement GSD with an agile method.

Risk Mitigation Techniques in Agile Development Processes

The main purpose of agile development methods is to reduce risks leading to a more successful and effective information system. In fact, analysing priorities, finding and identifying risks are important activities in all development approaches, including Agile development. However, some studies seek to assess risk management based on agile global software development (GSD) and provide mitigation measures to address specific risks. The risk mitigation technique for good development for sustainable development is expected to be designed to achieve time efficiency improvements to obtain greater resources at lower cost and thereby gain and maintain a competitive advantage

Risk Mitigation Techniques in Agile Development Processes

The main purpose of agile development methods is to reduce risks leading to a more successful and effective information system. In fact, analysing priorities, finding and identifying risks are important activities in all development approaches, including Agile development. However, some studies seek to assess risk management based on agile global software development (GSD) and provide mitigation measures to address specific risks. The risk mitigation technique for good development for sustainable development is expected to be designed to achieve time efficiency improvements to obtain greater resources at lower cost and thereby gain and maintain a competitive advantage

Communication Issues in Agile Software Development

Scrum framework is a growing trend in software industry to companies that are looking for development agile ways. In their early days, this methodology required that the working team members were established in a unique room, because it is necessary to have great communication and working together. However, it is a common increasingly practice that the teams are in geographically dispersed places, which means that it is necessary to adapt and/or look for the way that this methodology is suitable in these contexts. There are many experiences in the industry where we can see communication issues due to this kind work. In this paper we will briefly explain the Scrum framework definition, the Global Software Development (GSD) context, and the practices used in different case studies to solve the issues when applying Scrum in GSD.XIII Workshop Ingeniería de Software (WIS).Red de Universidades con Carreras en Informática (RedUNCI

Role of Agile Methods in Global Software Development

Currently software companies are developing the software applications that are developed by global software development teams. In order to develop the quality and cost effective software applications, companies are trying to adopt new methodologies for the global software development. Using of agile in global software development industry yielded benefits and challenges too. The researchers show that agile has many benefits in the software development and fewer complications. But suggesting the agile software development to the global projects is more challenging. This paper focuses on presenting the benefits and challenges in adopting the agile in global software development projects

The Use of Kanban to Alleviate Collaboration and Communication Challenges of Global Software Development

Aim/Purpose: This paper aims to describe how various Kanban elements can help alleviate two prominent types of challenges, communication and collaboration in Global Software Development (GSD). Background: Iterative and Lean development methodologies like Kanban have gained significance in the software development industry, both in the co-located and globally distributed contexts. However, little is known on how such methodologies can help mitigate various challenges in that occur in a globally distributed software development context. Methodology: The study was conducted using a single-case study based on a general inductive approach to analysis and theory development. Through the literature review, collaboration and communication challenges that GSD teams face were identified. Data collected through semi-structured interviews was then inductively analyzed to describe how the case-study teams employed various Kanban elements to mitigate communication and collaboration challenges they face during GSD. Findings: The study found that some Kanban elements, when properly employed, can help alleviate collaboration and communication challenges that occur within GSD teams. These relate to Inclusion Criteria, Reverse Items, Kanban Board, Policies, Avatars, and Backlog. Contribution: The paper contributes to knowledge by proposing two simple concept maps that detail the specific types of communication and collaboration challenges which can be alleviated by the aforementioned Kanban elements in GSD. Recommendations for Practitioners: This paper is relevant to GSD teams who are seeking ways to enhance their team collaboration and communication as these are the most important elements that contribute to GSD project success. It is recommended that relevant Kanban elements be used to that effect, depending on the challenges that they aim to alleviate. Future Research: Future research can investigate the same research questions (or similar ones) using a quantitative approach