Empirical Experiences, Metrics and Tools
for Project Management in Globally Distributed
Software Development Projects


The workshop is co-located with ICGSE 2009 in Limerick, Ireland on July 13, 2009. For more information, see the call for papers below.


ICGSE 2009 Call for Papers

Call for Papers

Empirical Experiences, Metrics and Tools
for Project Management in Globally Distributed Software Development Projects

July 13, 2009
Limerick, Ireland
Co-located with ICGSE 2009 Limerick, Ireland, July 13-16, 2009

Important dates

April 15, 2009 Deadline for paper submission to the workshop organizers
May 1, 2009 Decision of acceptance to paper authors
May 5, 2009 Final version of accepted papers due, according to IEEE standards
May 5, 2009 Deadline for early registration
July 13, 2009 Workshop

Workshop Schedule

9:00-9:15 - Introductions and short discussion on attendees interests
9:15-10:05 - Keynote -  Darja Smite -   The Challenges of Addressing GSE Challenges
Regular Paper Sessions (20 minutes + 5 Q/A)
10:05-10:30 -  Alberto Avritzer and Adailton Lima. An Empirical Approach for the Assessment of Scheduling Risk in A Large Globally Distributed Industrial Software Project
10:30-11:00 - Break
11:00-11:25 - Shareeful Islam and Md. Mahbubul Alam Joarder. Goal and Risk Factors for Offshore Outsourced Software Development
11:25-11:50 - Patricia Shiroma Brockmann and Thomas Thaumueller. Cultural Aspects of Global Requirements Engineering: An Empirical Chinese-German Case
11:50-12:15 - Tony Clear. Researching Collaborative Technologies in Global Virtual Teams: Empirical Studies from an Interpretive Perspective

Organizing Committee

Alberto Avritzer, Siemens Corporate Research
Juho Mäkiö, Research Centre for Information Technologies
Stefanie Betz, University of Karlsruhe
Rafael Prikladnicki, PUCRS, Brazil

Technical description

The strategic reasons for a company to opt for distributed software development are among others to speed up the time-to-market, to access the global resource pools, to profit from the around-the-clock development, and to reduce the costs. The distribution may be organized in multiple ways: The Company may cooperate with an onshore or offshore provider or the distribution is organized within the company by captive outsourcing. The distribution of software development projects has become a key software development technique. But, the distribution is a challenge. For example, various studies report about failures in outsourced software development projects. Hence, there seems to be a gap between the expectations and the reality regarding the results. Specifically, there is a severe gap in tools and methods to support the project lifecycle. The most popular project management, requirement engineering, architecture and testing tools were developed to support single-site projects. However, it is well known that globally distributed projects carry additional risks to quality, schedule and cost.

In this workshop we propose to present empirical experience, metrics, and tools for Project Management in globally distributed software development projects.

Various aspects of distributed software development are discussed in the current literature. However, there are still several gaps in project management of distributed software development projects. Reasons for negative incidents are, for example, missing skill management and difficult task coordination or task synchronisation. Thus, suitable tools and methods taking into account the specific needs of offshore software development are required. These new tools need to account for additional risks incurred by globally distributed software development projects like, language, geographical distribution, culture, time difference, etc…

Issues of risk management are highly relevant, when an organization distributes the software development project. Fitting risk management tools and methodologies are required as the ignorance of the risks may lead to various undesirable and costly events. But, how should one manage the risks? What tools and methodologies are required? What is “risky” in the distributed software development and what makes it risky? How the risks may be avoided? What do we need to do (mechanisms, approaches) to avoid the risks?

Successful organization of geographically distributed teams requires additional efforts. Different approaches should be taken for dividing and allocating tasks. Additional infrastructure and tools need to be implemented. Time and communication delays are often inevitable in an offshore environment. It is therefore more difficult for the whole team to react to emerging events or changes. How can tool support the communication during the project? Which information needs to be communicated to whom and when?

Furthermore, globally distributed software development projects also raise new challenges for the education of future software professionals. In addition to technical skills, there is obviously a need to focus on the education of high-level system skills, project management issues, and analytical as well as synthetic reasoning techniques in the software engineering field.

Technical issues

The challenges that are coupled with the management of distributed software development projects call for new process models, techniques, methodologies and tools. This workshop focuses on multiple aspects of management of distributed software development.

Topics of interest to the conference include the following aspects of global software engineering projects (but are not restricted to):

  • requirement engineering for globally distributed software development projects
  • requirement description in globally distributed software development projects
  • multi-sourcing in global software development
  • quality  metrics form globally distributed projects
  • risk management / risk modelling / risk analysis of offshore projects
  • process for planning and execution
  • organizational models and strategies
  • project portfolio management
  • communication models for distributed software development teams
  • causalities between critical success factors
  • metrics for critical success factors
  • problem handling during project work
  • outsourcing / offshoring contracts
  • decision support systems
  • strategic planning
  • project planning and preparations
  • simulation


The challenging issues arising in the field of offshore software engineering projects require novel approaches in risk analysis, project planning, and methods in order to handle the bounded financial and technical risks.

The goal of this workshop is to provide a forum for researchers and professionals interested in global software development to discuss and exchange ideas. In particular, this workshop takes the perspective of the practitioner and focuses on the techniques that will help software professionals to meet the unique challenges in a global development environment. Thus, the major goal of this workshop is to discuss novel methodologies for risk management for global software development. Additionally, we want to provide a platform bringing together researches and practitioners in order to share their knowledge and requirements in the field of offshore software development.

Target Audience

  • requirement engineers
  • software engineers
  • computer scientists
  • business process engineers
  • project managers

Program committee

  • Dr. Andre Bondi, Siemens Corporate Research
  • Prof. Dr. M. Esser, St. Petersburg State Polytechnic University
  • PhD. Robert Feld, Blekinge Inst. of Technology
  • Prof. Dr. Eila Järvenpää, Helsinki University of Technology
  • Dr. Andreas Kotulla, Telisys GmbH
  • Dr. Steve Masticola, Siemens Corporate Research
  • Prof. Dr. Andreas Oberweis, University of Karlsruhe
  • Dr. Maria Paasivaara, Helsinki University of Technology
  • Dr. Darja Smite, Riga Information Technology Institute
  • Prof. Dr. Riitta Smeds, Helsinki University of Technology

Paper submission

  • Paper should be submitted to
  • Your paper must conform to the IEEE proceedings publication format (8.5" x 11", Two-Column Format) described at IEEE/CPS.
  • You paper should not be longer than 6 pages including all text, references, appendices, and figures.
  • Your submissions should be in PDF format. Submissions that exceed the page limit (6) or do not comply withthe proceedings format will be desk rejected without review.
  • The results described must not be under consideration for publication elsewhere.
  • Conference details are available on

Related Workshops

This workshop is the third in a series of Risk Management ICGSE workshops. This year we are expanding the focus to project management and requirement engineering as well. Links to previous ICGSE workshops are:

ICGSE 2008
ICGSE 2007