Orchestration of Global Software Engineering Projects - Position Paper

Christian Bartelt, Manfred Broy, Christoph Herrmann, Eric Knauss, Marco Kuhrmann, Andreas Rausch, Bernhard Rumpe, Kurt Schneider

TL;DR

This position paper argues that orchestrating global software engineering (GloSE) projects is crucial for success, moving beyond simple integration to actively manage diverse teams, processes, and artifacts. The authors propose a framework for this orchestration across project setup, processes, and artifacts, highlighting the need for "views" that provide tailored, role-specific snapshots of the project.

What Problem Does This Paper Address?

The paper tackles the growing reality of global software engineering (GloSE), where development teams are distributed across different locations, cultures, and time zones. While this distribution is driven by economic, organizational, and strategic factors, it introduces significant challenges. These include difficulties in quality management, schedule and budget overruns, and the inherent complexities of integrating diverse cultures, languages, and working styles. The core problem is how to effectively manage and coordinate these distributed efforts to achieve project goals, moving beyond just technical integration to a more holistic "orchestration" of the entire project environment.

Methods

The authors present a conceptual framework for orchestrating GloSE projects. Their approach focuses on re-orchestrating existing communication and coordination cultures across three key levels:

  1. Project set-up and management: Establishing how the project is initiated, structured, and managed globally.
  2. Processes and information flows: Harmonizing or coupling diverse development processes and ensuring effective communication channels.
  3. Artifacts and product models: Managing the creation, consistency, and accessibility of project artifacts across distributed teams.

A key element of their approach is the concept of "views." These are defined as site-independent, task-driven, and role-specific snapshots of the project, designed to provide relevant information to individuals without overwhelming them with unnecessary details.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • GloSE is a necessity, not a choice: The paper emphasizes that global software engineering is no longer an option but a practical reality driven by market forces and company structures.
  • Orchestration is more than integration: Simply connecting distributed teams and tools isn't enough. Effective GloSE requires actively managing and harmonizing diverse elements.
  • The "Virtual Project Environment": The paper frames a globally distributed project as a "virtual project environment" that needs deliberate orchestration.
  • The critical role of "Views": The concept of tailored, role-specific "views" is central to managing information and communication in GloSE, allowing individuals to focus on what's relevant to their tasks.
  • Three-level orchestration: The proposed framework of orchestrating across project setup, processes, and artifacts provides a structured way to address GloSE challenges.
  • Cultural and temporal distances are major hurdles: The paper highlights that differences in culture and time zones significantly impact communication and coordination, often leading to issues similar to or worse than those in co-located projects.

Key Results

As this is a position paper, it doesn't present empirical results in the traditional sense. Instead, it outlines a conceptual approach and identifies key challenges and research questions. The "results" are the identification of:

  • The primary drivers for GloSE (economic, organizational, strategic).
  • The main challenges: cultural and temporal distances, communication and coordination issues, and the management of distributed artifacts and processes.
  • A proposed framework for orchestration across three levels.
  • The concept of "views" as a solution for information management.
  • A set of open questions to guide future research in GloSE.

Limitations and Future Work

The authors acknowledge that their paper is a position paper and serves as a baseline for discussion. They identify several areas for future research:

  • Identifying critical problems beyond integration: Are there other significant issues in GloSE not covered by their framework?
  • Scope of orchestration: Does their proposed orchestration cover all relevant aspects, and what new problems might it introduce?
  • Completeness of the three levels: Do the three identified levels (project setup, processes, artifacts) encompass the entirety of GloSE integration capabilities?
  • Practical realization of GloSE infrastructure: What are the most efficient ways to implement the proposed infrastructure in practice?
  • Parallel vs. sequential integration: Should integration issues at each level be addressed separately or in parallel?
  • Experiences with integrating technical and non-technical issues: What are the lessons learned from integrating communication habits and other non-technical aspects?
  • Techniques for identifying individual practices: How can individual practices be identified without disrupting development work?
  • Accommodating project dynamics: How can the approach handle the inherent dynamics and changes in multi-site projects?
  • Defining "views": How can common and standardizable patterns of views be identified?
  • Identifying global spanning elements: Are there processes or artifacts that span all sub-projects, and how can they be managed?
  • Tooling for GloSE: How can a GloSE infrastructure accommodate diverse individual tools?
  • Organizational readiness for GloSE: What is the optimal strategy for making organizations "GloSE-ready," considering investments in different dimensions?

Summary updated

Abstract

Global software engineering has become a fact in many companies due to real necessity in practice. In contrast to co-located projects global projects face a number of additional software engineering challenges. Among them quality management has become much more difficult and schedule and budget overruns can be observed more often. Compared to co-located projects global software engineering is even more challenging due to the need for integration of different cultures, different languages, and different time zones-across companies, and across countries. The diversity of development locations on several levels seriously endangers an effective and goal-oriented progress of projects. In this position paper we discuss reasons for global development, sketch settings for distribution and views of orchestration of dislocated companies in a global project that can be seen as a ldquovirtual project environmentrdquo. We also present a collection of questions, which we consider relevant for global software engineering. The questions motivate further discussion to derive a research agenda in global software engineering.
BibTeX
@inproceedings{bartelt2009orchestration,
  author = {Christian Bartelt and Manfred Broy and Christoph Herrmann and Eric Knauss and Marco Kuhrmann and Andreas Rausch and Bernhard Rumpe and Kurt Schneider},
  title = {{Orchestration of Global Software Engineering Projects - Position Paper}},
  booktitle = {ICGSE},
  year = {2009},
  url = {https://openreview.net/forum?id=YR4g0YDYZKz},
}
Figure