ArticlePDF Available

A Practical Management and Engineering Approach to Offshore Collaboration

September 2006
IEEE Software 23(5):20-29

DOI:10.1109/MS.2006.118

Source
DBLP

Authors:

James Cusick

Ritsumeikan University

Alpana Prasad

Wolters Kluwer

Leveraging offshore staff for software development is rapidly becoming the norm in the Corporate Legal Services division at Wolters Kluwer ,. The Global Software Development model has evolved over the years into a relatively mature approach supporting new development as well as production support . This model offers a tactical approach to the offshore process for companies pursuing or planning to expand into offshore development . This article also documents key practices that lead to success in this environment and details traps that can limit project effectiveness.This article is part of a special issue on Global Software Development.

Content uploaded by James Cusick

Content may be subject to copyright.

1 
 
                
 
A Practical Management and Engineering Approach 
to Offshore Collaboration 
 
Abstract: 
Firms  developing  or  maintaining  software  products  can't  ignore  global  software 
development's impact. Managing multiple simultaneous projects and production support with 
a global staff over the last several years has also made us aware of traps to avoid. The global 
software development model provides a tactical approach for companies pursuing or planning 
to expand into offshore development. We present  a practitioner's view of our model for 
offshore development and insights into our management and engineering techniques, which 
can be replicated in other environments. This article adds to the existing literature by providing 
a structural framework  and  the  guidelines necessary  to maintain the quality of offshore 
engagements. 
 
Published in: IEEE Software ( Volume: 23 , Issue: 5 , Sept.-Oct. 2006 )  
 
DOI: 10.1109/MS.2006.118 
 
URL: https://ieeexplore.ieee.org/document/1687857 
 
Citation: J. Cusick and A. Prasad, "A Practical Management and Engineering Approach to Offshore 
Collaboration," in IEEE Software, vol. 23, no. 5, pp. 20-29, Sept.-Oct. 2006, doi: 10.1109/MS.2006.118. 
 
IEEE Keywords: 
• Engineering management, 
• Collaborative software, 
• Lead, 
• Programming, 
• Software maintenance, 
• Standards development, 
• Software development management, 
• Maintenance engineering, 
• International collaboration, 
• Project management 
 

Towards dealing with commonly occurring requirements engineering process issues during software development outsourcing

Article

Full-text available

Jul 2022
PLOS ONE

Due to specific advantages, the volume of Software Development Outsourcing (SDO) is rapidly increasing. Because of challenges arising from the Requirements Engineering (RE) process, the anticipated benefits of SDO are not achieved in case of several projects. The objective of this research work is to recommend RE practices for addressing the commonly arising RE process issues in the case of SDO. For this reason, a thorough literature review has been undertaken, as well as two questionnaire surveys have been performed with skilled SDO industry practitioners. The surveys have been done by utilizing semi-supervised style and employing Convenience Sampling method. The 50 percent rule and a four-point Likert Scale have also been used to determine the advantages of RE practices for dealing with the issues. A comprehensive list of 147 RE practices has been extracted by conducting a Focus Group session. Furthermore, the 147 RE practices have been ranked by applying Numerical Assignment and Hundred Dollar Techniques during two Focus Group sessions. The detection and adaptation of RE practices aids in enhancing the SDO RE process, evading SDO failures, and achieving the associated SDO advantages.

Turning the Tables: The View from Offshore During 60 Days in JST

Preprint

Full-text available

May 2021

James Cusick

A report and examination of a Remote Work experience during the Covid-19 pandemic encompassing a 14-hour time difference from the primary work location. Advantages and disadvantages of a globally distributed work experience as compared to an aligned time zone are explored. Logistical aspects of the arrangement are provided as well as the management support, peer reaction, and relative productivity. Recommendations are also provided on how to improve future geographically diverse team arrangements. [Keywords: Global Software Development, Offshore Development, Software Engineering, IT Management, Remote Work, Remote Office Design, Distributed Communications, Collaboration Technology, Team Management, Research, Development, Productivity]

Software Project Management Approaches for Global Software Development: A Systematic Mapping Study

Article

Apr 2018

Global Software Development (GSD) is a well established field of software engineering with the benefits of a global environment. Software Project Management (SPM) plays a key role in the success of GSD. As a result, the need has arisen to study and evaluate the downsides of SPM for GSD, to thereby pave the way for the development of new methods, techniques, and tools with which to tackle them. This paper aims to identify and classify research on SPM approaches for GSD that are available in the literature, to identify their current weaknesses and strengths, and to analyze their applications in industry. We performed a Systematic Mapping Study (SMS) based on six classification criteria. Eighty-four papers were selected and analyzed. The results indicate that interest in SPM for GSD has been increasing since 2006. As a class of approaches, the most frequently reported methods (40%) are those used for coordination, planning, and monitoring, along with estimation techniques that can be used to better match a distributed project. SPM for GSD requires further investigation by researchers and practitioners, particularly with respect to cost and time estimations. These findings will help overcome the challenges that must to be considered in future SPM research for GSD, especially regarding collaboration and time-zone differences.

Making Agile Development and Offshoring Practice Successful on Global Software Development Project

Chapter

Jan 2014

Two significant trends have been gaining momentum in software development: the utilization of Agile development methodologies, and the continuing trend of companies to outsource development work offshore. These two trends have changed the way companies develop software and business applications. This chapter seeks to evaluate how a company can successfully manage both trends in conjunction with each other on global business. The primary question addressed is whether the benefits derived from Agile development methodologies and the savings from outsourced software development efforts cancel each other out when applied together, or whether they create a synergy greater than the sum of the parts. In order to answer this question, this chapter intends to examine several relevant business practices and industry experiences. From lessons learned, we identify factors which seem to influence a successful combination of Agile methodology and offshoring in global software development projects.

Learning to detect community smells in open source software projects

Article

Full-text available

Jul 2020
KNOWL-BASED SYST

Community smells are symptoms of organizational and social issues within the software development community that often lead to additional project costs. Recent studies identified a variety of community smells and defined them as sub-optimal patterns connected to organizational-social structures in the software development community. To early detect and discover existence of potential community smells in a software project, we introduce, in this paper, a novel machine learning-based detection approach, named csDetector, that learns from various existing bad community development practices to provide automated support in detecting such community smells. In particular, our approach learns from a set of organizational-social symptoms that characterize the existence of potential instances of community smells in a software project. We built a detection model using Decision Tree by adopting the C4.5 classifier to identify eight commonly occurring community smells in software projects. To evaluate the performance of our approach, we conduct an empirical study on a benchmark of 74 open source projects from Github. Our statistical results show a high performance of csDetector, achieving an average accuracy of 96% and AUC of 0.94. Moreover, our results indicate that the csDetector outperforms two recent state-of-the-art techniques in terms of detection accuracy. Finally, we investigate the most influential community-related metrics to identify each community smell type. We found that the number of commits and developers per time zone, the number of developers per community, and the social network betweenness and closeness centrality are the most influential community characteristics.

An empirical approach for optimizing globally distributed software product engineering

Conference Paper

Sep 2017

Bhaskarjyoti Das

A distributed software product engineering team has to deal with the additional issue of distribution apart from the usual expectations around cost, quality, time to market and innovation. Distribution of work brings in the issues of temporal, geographical and cultural separation. In spite of individually following the prescribed software engineering processes, often the distributed teams fail to act as a single product team. It is also a well accepted truth that misaligned distributed teams rarely produce satisfactory outcome. The short life cycle for Internet based products adds to these challenges. As a result, global software product engineering is still somewhat immature. In this paper we describe an empirical study to diagnose, detect and cure the health issues in a distributed software product engineering program. This consists of steps such as problem identification, research review, study design, validity consideration, data analysis and conclusion. The key hypothesis in this approach is the assumption that most distributed software product engineering teams in the same organization require alignment rather than bottom up retooling in the form of an elaborate software engineering initiative and this alignment can be achieved in a fast and effective manner by aligning the key interface leaders. By focusing first on causes of misalignment between different parts of distributed team, the root causes behind lack of satisfactory outcome can be quickly surfaced. This top down method is a departure from the usual bottom up approach of starting from process adherence. This approach allows the distributed teams to retain their cultural idiosyncrasies that are hard to remove. This paper shares the experience from such an initiative undertaken in an Internet based product company doing software product engineering across India and USA.

A process explanation of the effects of institutional distance between parties in outsourced information systems development projects

Article

Oct 2016

Outsourced information systems development (OISD) projects are challenging endeavors, and the literature suggests differences between the parties involved as critical hinderers of such projects. Using institutional theory as a foundational theory, we propose a process explanation of the effects of differences between parties in OISD projects. Our explanation relies on the interaction of four components: (1) the IS development and project management institutional profiles of the parties involved; (2) the institutional distance between practices within these profiles; (3) instances of conflicting institutional demands when institutional distance becomes salient; and (4) the repertoire of institutional strategic responses available to parties to address those instances. We suggest that the constitutive elements of institutional distance and the degree to which parties envision their collaboration beyond the project at hand contribute to explaining the enactment of strategic responses. Accounting for the fact that practices, as well as the institutional logics that drive their enactment, may differ between parties, we make a theoretical contribution to the literature on OISD by building a fine-grained explanation of the effects of differences between parties in OISD projects.

Globalization

Chapter

Aug 2008

In this chapter we address the concept of agility in a wider context. One topic on which we focus is globalization in terms of distributed teamsdistributed teams ; the second idea is the application of the agile approach for the managementmanagement of non-software projectsnon-software projects project . Agile software development has evolved significantly during the last decade. In parallel to this evolution, globalization in software development has also emerged, and software is developed in many cases by teams which are spread across geographical areas, cultures, and nationalities. This reality, called global software development, has advantages as well as disadvantages. The most obvious advantage is the business aspect of cost reduction; the most problematic issues are communication and team synchronization. In this chapter we briefly describe the notion of global software development and explain how some agile practices help cope with the challenges involved. Specifically, we will see that the agile approach encourages a transparent global software development process. thus increasing information flow and project visibility and assistings in solving communication and synchronization problems. Further, the tightness of agile processes simplifies software project management. We also examine in this chapter the notion of agility beyond the software world and discover its usefulness in such projects

GlobalizationGlobalization

Chapter

Oct 2014

Globalization is usually related to time, distance, and culture. Referring to time, we cite Friedman’s book The World is Flat : “… That’s globalization, said Nilekani. Above the screen, there were eight clocks that pretty well summed up the Infosys workday: 24/7/365. The clocks were labeled US West, US East, GMT, India, Singapore, Hong Kong, Japan, Australia” (Friedman 2005, p. 6). Referring to distance, a physical distance between teams, which work together on one product, increases the process complexity. It is further claimed that even a 50 m distance can be considered as a distributed environment (Allen 1984 in Sangwan et al. 2007). Referring to culture , this concept has been explored extensively with respect to different kinds and sizes of groups like nations, tribes, and teams. We define the concept of culture as a set of explicit and implicit norms, values, and beliefs, shared by the practitioners in a group to which they belong that, on one hand, influences directly the practitioners’ daily activities, behaviors, and interactions and, on the other hand, is fed back by these activities, behaviors, and interactions and is shaped by them. The culture of a specific team is influenced by the culture of the nation as well as the organizational culture. Both are relevant for global environments. In this chapter, we address globalization as it is expressed by agile teams.

Offshore Suitability: Criteria for Selecting IS Applications or Projects for Offshoring

Chapter

Jan 2009

Markus Westner

The identification of suitable applications or projects is a main initial step in any software development or maintenance related IS offshoring arrangement. This paper identifies evaluation criteria for selecting candidates for offshoring, analyzes the importance of the criteria, and relates them to an organization's offshoring expertise. Based on a literature analysis and interviews with 47 experts from 36 different German companies, we identified several evaluation criteria. The main findings are that in contrast to the literature, size, codification, and language are perceived as important selection criteria by experts. These differences might be due to cultural differences. Additionally, codification, business criticality, business specificity, and complexity seem to be less important in the case of organizations with offshoring expertise.

Designing the Inter-Organizational Software Engineering Cooperation: An Experience Report

Article

Full-text available

Hans W. Nissen

This paper reports about experiences in managing the transformation from internal development and maintenance of software engineering tools towards an external one. We describe three different inter- organizational cooperation forms which differ in the distribution of development responsibilities between client and vendor - and which support the distributed design of three different classes of software products. An important finding was that even for software engineering tools which were extremely important for project success a carefully designed relationship model enables a successful distributed development.

Using Iterative and Incremental Processes in Global Software Development

Article

Full-text available

Iterative and incremental development seems to be a viable approach providing several benefits in inter- organizational distributed software development. This pa- per presents initial results from an interview study on the usage of iterative and incremental development in inter- organizational distributed software development projects. We describe identified practices, such as delivery synchro- nization, design and code reviews, communication empha- sis, feature-based development, behavioral patterns, and frequent deliveries. We also present the benefits that the use of these practices brought, such as transparency of progress, increased developer motivation due to rapid feed- back, flexibility regarding changes, the possibility to involve subcontractors early, ensuring joint understanding of re- quirements, and the avoidance of "big bang" integration. It seems that the advantages of using the practices overweigh the extra communication and coordination cost they incur.

Offshoring Opportunities: Strategies and Tactics for Global Competitiveness

Book

Aug 2015

J. Berry

Offshoring opportunities is on target for today's marketplace. "This book provides a much needed framework for offshoring that supports making sound business decisions in this area, and it can help guide the management of the resulting offshore relationship in an efficient and effective manner. John brings clarity and structure to this broad and complex subject." -Jim Maloney Chief Security Executive Corillian Corporation. "An extremely well-written and researched book. Starts with a good background on the political and cultural implications of offshoring and proceeds to provide an invaluable guide to take the reader through the sourcing decision and how to make it." -Charly Paelinck Vice President of Application Development Harrah's Casino. "We evaluate many different offshoring and site selection decisions each year for our clients, and I encourage every executive faced with these quandaries to consider the strategies discussed in this book. Offshoring Opportunities can be used as a practical review before investing millions, and it may just help you avoid several unintended consequences." -Jay Doherty Principal Mercer Human Resource Consulting.

Using iterative and incremental processes in global software development

Conference Paper

Jan 2004

Maria Paasivaara

Iterative and incremental development seems to be a viable approach providing several benefits in inter-organizational distributed software development. This paper presents initial results from an interview study on the usage of iterative and incremental development in inter-organizational distributed software development projects. We describe identified practices, such as delivery synchronization, design and code reviews, communication emphasis, feature-based development, behavioral patterns, and frequent deliveries. We also present the benefits that the use of these practices brought, such as transparency of progress, increased developer motivation due to rapid feedback, flexibility regarding changes, the possibility to involve subcontractors early, ensuring joint understanding of requirements, and the avoidance of "big bang" integration. It seems that the advantages of using the practices overweigh the extra communication and coordination cost they incur.

Designing the inter-organizational software engineering cooperation: an experience report

Conference Paper

Jan 2004

Hans W. Nissen

This paper reports about experiences in managing the transformation from internal development and maintenance of software engineering tools towards an external one. We describe three different inter-organizational cooperation forms which differ in the distribution of development responsibilities between client and vendor - and which support the distributed design of three different classes of software products. An important finding was that even for software engineering tools which were extremely important for project success a carefully designed relationship model enables a successful distributed development.

Cultures and Organizations. Software of the Mind

Book

Jan 2004

The revolutionary study of how the place where we grew up constrains the way we think, feel, and act, updated for today's new realities The world is a more dangerously divided place today than it was at the end of the Cold War. This despite the spread of free trade and the advent of digital technologies that afford a degree of global connectivity undreamed of by science fiction writers fifty years ago. What is it that continues to drive people apart when cooperation is so clearly in everyone's interest? Are we as a species doomed to perpetual misunderstanding and conflict? Find out in Cultures and Organizations: Software of the Mind. A veritable atlas of cultural values, it is based on cross-cultural research conducted in seventy countries for more than thirty years. At the same time, it describes a revolutionary theory of cultural relativism and its applications in a range of professions. Fully updated and rewritten for the twenty-first century, this edition: Reveals the unexamined rules by which people in different cultures think, feel, and act in business, family, schools, and political organizations Explores how national cultures differ in the key areas of inequality, collectivism versus individualism, assertiveness versus modesty, tolerance for ambiguity, and deferment of gratification Explains how organizational cultures differ from national cultures, and how they can--sometimes--be managed Explains culture shock, ethnocentrism, stereotyping, differences in language and humor, and other aspects of intercultural dynamics Provides powerful insights for businesspeople, civil servants, physicians, mental health professionals, law enforcement professionals, and others Geert Hofstede, Ph.D., is professor emeritus of Organizational Anthropology and International Management at Maastricht University, The Netherlands. Gert Jan Hofstede, Ph.D., is a professor of Information Systems at Wageningen University and the son of Geert Hofstede.

Efficient Maintenance Support in Offshore Software Development: a Case Study on a Global E-Commerce Project

Article

Jan 2004

Zheng Yan

Software maintenance is a very important phase in software development. It generally occupies the most of development life cycle in order to ensure software quality. This paper takes an e-commerce project as an example to study how to efficiently provide software maintenance support in offshore software development for a global deployed software product. Through interviews and a survey to the project developers, authors summarize the good methods and approaches used in its maintenance that greatly helped its success. Meanwhile, the authors also study lessons that influenced its efficient maintenance (e.g. extra workload caused by performance tuning, troubles due to sharp time-difference, problem- reproducing difficulty caused by testing environment difference and slow code transfer). Suggestions for further improvement are also proposed based on real experiences in order to benefit similar software development in the future.

Global Software Development: Managing Virtual Teams and Environments

Article