To Overcome Communication Challenges in Distributed/Virtual Scrum Teams

The purpose of this research is to give an overview of a scrum in distributed teams and to suggest ways overcome communication challenges in such projects. In this research proposal, the latest available research on a scrum in distributed teams will be thoroughly analyzed and evaluated to know the possible solutions for communication problems in distributed teams. A review of the literature suggested scrum is widely accepted agile methodology in software projects and also it works best within collocated teams. However, the literature review also proposes that lack of proper communication is one of the main challenge faced by distributed scrum teams which needs more research. Effective communication among teams is fundamental to the agile approach in which proper and continuous feedback are absolutely necessary to improve team productivity and software quality. It is important to have right communication tool, trust among team members, organized daily scrum meetings, proper coordination, less time zone difference between locations and no language barrier to have effective communication within virtual scrum teams. Due to progression in technology scrum projects are going distributed as there are many benefits to the organizations. A brief literature review will be conducted to study the research problem which will provide valuable solutions to the communication issues in distributed teams. This research paper will be very useful to other researchers to solve the other challenges of a scrum in distributed projects

Do the scaled agile practices from s@s help with quality requirements challenges and if so, how do they do it?

Quality Requirements (QRs) pose challenges in many agile large-scale distributed enterprise systems. Often, enterprises counter such challenges by borrowing some heavyweight practices, e.g. adding more documentation. At the same time, agile methodologists proposed several scaled agile frameworks to specifically serve agile enterprises working on large and distributed systems. Little is known about the extent to which the proposed scaled frameworks address QRs and the specific ways in which this happens. Moreover, do these frameworks approach the QRs challenges in ways consistent with the Agile Manifesto? This paper treats these questions by analyzing one well-documented scaled framework, namely Scrum@Scale. We evaluated the alignment of Scrum@Scale with the Agile Manifesto, by means of the 4-Dimentional Analytical Tool proposed by other researchers. We then analyzed the practices of Scrum@Scale from the perspective of practitioners responsible for the QRs in a project, in order to understand how the Scrum@Scale practices mitigate those QRs challenges reported in previous work. Our analysis indicated that Scrum@Scale supports the agile values defined by the Agile Manifesto. Plus, we identified 12 Scrum@Scale practices that could (partially) mitigate one or more of the reported QRs challenges. Four of the reported QRs challenges got no remedy offered by Scrum@Scale.</p

Scrum Abandonment in Distributed Teams: A Revelatory Case

The last decade has witnessed substantial growth in the adoption of both Agile and distributed software development. However, combining Agile practices, which emphasize regular informal communication, with geographically and temporally distributed sites, which hinder regular informal communication, presents numerous challenges. Proponents of Agile, especially the Scrum project management framework, have published several case studies of successful Scrum implementations in distributed environments. However, few empirical studies examine failed or abandoned Scrum implementations. Consequently, this paper presents a revelatory case study of a geographically and temporally distributed software development team that abandoned its attempted transition to Scrum. Two factors associated with the team’s decision to abandon Scrum are identified – degradation of Scrum practices due to distribution and the undermining of the ScrumMaster’s credibility. Based on this analysis the paper proposes that task/team familiarity, group cohesion and transactive memory may be combined to understand the relationship between geotemporal distribution, process and performance

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

Towards a 5c theory of communication for scrum-based distributed projects

Scrum-based distributed projects face numerous challenges and failures due geographical, dispersed, times and cultural differences. To improve the success of such software development projects, there is a need to identify factors crucial to achieving the required level of communication between the distributed stakeholders. In this paper, we reviewed the issues and challenges associated with communication in scrum-based distributed projects and explored factors that could improve communication for scrum-based distributed projects. A total number of 25 interviews were conducted in various geographical regions which helped to identify five major factors, i.e. competency, correlation, comprehension, contentment and commitment, crucial to the success of scrum-based distributed projects. Our identification of these factors presents a research and practice approach to developing a theory of communication that would help project managers, scrum masters and practitioners to improve practices while undertaking scrum-based distributed projects

Effective communication in globally distributed Scrum teams

Trends in information systems development include the use of globally distributed teams and agile methodologies such as Scrum. Globally distributed (GD) software development challenges team communication. Before we can evaluate effective communication in GD teams using Scrum, we need to know what effective communication means in that context. This study captures the understanding of effective communication based on interviews with industry professionals working in GD Scrum teams and reports on Scrum practices that keep communication effective. From these interviews, we developed a model consisting of communication transparency, communication quality, and communication discipline, leading to the alignment of team understanding. This paper contributes to practitioners’ knowledge about what effective communication means in GD Scrum and describes tools that support communication. The theoretical contribution of the study is a model of effective communication that lays the ground for future research on evaluating Scrum’s effect on communication in GD contexts

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

Holistic analysis of the effectiveness of a software engineering teaching approach

To provide the best training in software engineering, several approaches and strategies are carried out. Some of them are more theoretical, learned through books and manuals, while others have a practical focus and often done in collaboration with companies. In this paper, we share an approach based on a balanced mix to foster the assimilation of knowledge, the approximation with what is done in software companies and student motivation. Two questionnaires were also carried out, one involving students, who had successfully completed the subject in past academic years (some had already graduated, and others are still students), and other questionnaire involving companies, in the field of software development, which employ students from our school. The analysis of the perspectives of the different stakeholders allows an overall and holistic) view, and a general understanding, of the effectiveness of the software engineering teaching approach. We analyse the results of the questionnaires and share some of the experiences and lessons learned.info:eu-repo/semantics/publishedVersio