Beyond the border: A comparative literature review on communication practices for agile global outsourced software development projects

Software development is increasingly heading in the direction of combining agile software development practices and outsourcingsoftware development to external vendors worldwide. The resultingagile global outsourced software development (AGOSD) projects are characterized by applying agile methods to distributed environments, whichresults in several problems for collaboration and coordination. Specifically, communication between the project participantshas been found to be a major challenge in distributed environment. Therefore, our study investigates the problem of improving communication in distributed settings by identifying suitable communication practicesfor usage within AGOSD projects.Based on an extensive literature review,our study (1) provides an overview of adequate practices for usage in AGOSD and (2) points out differences to traditional communication practices ofagile software development(ASD)projects used in collocated, non-distributed environments

Applying Agile Lean to Global Software Development

Although challenges of Global Software Development (GSD) are well known in the industry, practitioners and the organizations look for ways to improve results and overcome challenges. Companies have tried to implement many workable solutions possible to solve issues like poor communication, lack of trust, low morale and many other such issues prevalent in the distributed setting. With the success of agile, the methodology gained interest in leveraging its benefits to alleviate some of these challenges. Similarly, lean was also implemented in distributed software development to resolve issues. While each methodology provided some improvement in the results achieved in global software development, many issues persisted and the desired growth/results were not received. Recent years have seen an increased interest of applying a combination of agile and lean software development paradigms to resolve current industry issues in the area and meet the needs of rapid changing environment. This study aims to study the current practices of the combination of agile lean existing in the industry and how it can be utilized in the global software development. The study focuses on challenges faced to implement agile lean and successful sustainable implementation of agile lean in an environment of global software development

Considerations for Effective Requirements Analysis in Offshore Software Development Projects: Lessons from Multi-method Research

Offshore software development using geographically distributed teams is an accepted practice in software development today. However, software development companies have largely only offshored the software development lifecycle’s coding and testing phases. However, lately, offshoring the requirements analysis (RA) phase has become increasingly viable for several reasons including the software industry’s maturation and improved communication technologies. However, successfully evaluating this highly interactive phase between geographically dispersed client and provider teams requires special considerations. In this paper, we present practical insights garnered from conducting experiments and surveys of IS professionals from the Indian software industry and from extensively examining the literature. Our findings confirm that, subject to certain best practices, one can effectively conduct RA in software projects offshore. We present these practices as lessons learned and provide related recommendations for industry and academia

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

Requirements volatility in multicultural situational contexts

Requirements volatility refers to additions, deletions, and modifications of requirements during the system development life cycle. Different approaches in software development, including Agile and DevOps, have addressed requirements volatility by increasing user participation throughout the whole development process. In this paper, we analyse requirements volatility from a situational context angle with the aim to increase understanding of the role of culture and cultural diversity in a multicultural requirements elicitation process. Research on the situational context in Requirements Engineering (RE) is rather limited, despite the recognized importance of RE and requirements elicitation for improving the quality of the final system and software product. This paper builds on an extensive literature review demonstrating the importance of raising awareness and understanding of the role of culture and cultural diversity for requirements volatility, as one of the most significant situational factors in the requirements elicitation process, with the aim to improve the whole systems development process as well as the resulting products and services. The paper concludes with the presentation of the Requirements Cultural Volatility Framework which aims to reveal potential conflicts that may occur in requirements elicitation on a multiplicity of cultural dimensions, The framework proposes actions to be taken in order to address the conflicts and point out expected benefits on each dimension

Project Management in the Fourth Industrial Revolution. Beer production project

El objetivo de este documento es encontrar soluciones a los problemas de gestión de proyectos que surgen como consecuencia de la cuarta revolución industrial, que está cambiando la industria tal y como la conocemos y nos sitúa en un punto crítico de adaptación a una nueva realidad que traerá consigo grandes oportunidades y también grandes riesgos. Además, la gestión de los nuevos proyectos 4.0 supondrá un reto de comunicación entre expertos en tecnologías y lenguajes informáticos muy diferentes, por lo que este documento destaca los elementos a tener en cuenta en la revolución tecnológica y estudia cómo gestionar un proyecto en una Smart factory.The aim of this document is to find solutions to the project management problems that arise as a result of the fourth industrial revolution, which is changing industry as we know it and places us at a critical point of adaptation to a new reality that will bring great opportunities as well as great risks. In addition, the management of new 4.0 projects will pose a challenge for communication between experts in very different technologies and computer languages, which is why this document highlights the elements to be taken into account in the technological revolution and studies how to manage a project in a Smart factory.Hochschule Albstadt-SigmaringenGrado en Ingeniería en Organización Industria

Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams

Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives

Advances in Production Management Systems: Issues, Trends, and Vision Towards 2030

Since its inception in 1978, the IFIP Working Group (WG) 5.7 on Advances in Production Management Systems (APMS) has played an active role in the fields of production and production management. The Working Group has focused on the conception, development, strategies, frameworks, architectures, processes, methods, and tools needed for the advancement of both fields. The associated standards created by the IFIP WG5.7 have always been impacted by the latest developments of scientific rigour, academic research, and industrial practices. The most recent of those developments involves the Fourth Industrial Revolution, which is having remarkable (r)evolutionary and disruptive changes in both the fields and the standards. These changes are triggered by the fusion of advanced operational and informational technologies, innovative operating and business models, as well as social and environmental pressures for more sustainable production systems. This chapter reviews past, current, and future issues and trends to establish a coherent vision and research agenda for the IFIP WG5.7 and its international community. The chapter covers a wide range of production aspects and resources required to design, engineer, and manage the next generation of sustainable and smart production systems.acceptedVersio

Distributed development of large-scale distributed systems: the case of the particle physics grid

Developing a Grid within High Energy Physics for the Large Hadron Collider particle accelerator is characterised as a highly collaborative, distributed and dynamic systems development effort. This research examines the way this distributed Grid is developed, deployed and provided as a service to the thousands of physicists analysing data from the Large Hadron Collider. The particle physics community has always been at the forefront of computing with a tradition of working in large distributed collaborations, therefore providing a "distinctive" case of distributed systems development practice. The focus of concern is the collaborative systems development practices employed by particle physicists in their attempt to develop a usable Grid. The research aims to offer lessons and practical recommendations to those involved in globally distributed systems development and to inform the information systems development literature. Global software development presents unaddressed challenges to organisations and it is argued that there is an urgent need for new systems development practices and strategies to be created that can facilitate and embrace the rapid changes of the environment and the complexities involved in such projects. The contribution of the study, therefore, is a framework of guidance towards engendering what the author defines as "Hybrid Experimental Agile Distributed Systems Development Communities" revealing a set of dynamic collaborative practices for those organisational contexts engaged in distributed systems development. The framework will allow them to reflect on their own practice and perhaps foster a similarly dynamic flexible community in order to manage their global software development effort. The research is in the form of an interpretative qualitative exploratory case study, which draws upon Activity Theory, and frames the Grid's distributed development activity as a complex overarching networked activity system influenced by the context, the community's tools, rules, norms, culture, history, past experiences, shared visions and collaborative way of working. Tensions and contradictions throughout the development of this Grid are explored and surfaced, with the research focusing on how these are resolved in order for the activity system to achieve stability. Such stability leads to the construction of new knowledge and learning and the formation of new systems development practices. In studying this, practices are considered as an emergent property linked to improvisation, bricolage and dynamic competences that unfold as large-scale projects evolve