Philips experiences in global distributed software development

Rob Kommeren, Päivi Parviainen (Corresponding Author)

Research output: Contribution to journalArticleScientificpeer-review

71 Citations (Scopus)

Abstract

Global software development is increasingly common. Main expected benefits are improvements in time-to-market efficiency and access to greater—and less costly—resources.
A number of problems are still to be solved before the full potential of global development can be obtained. This paper describes the experience of over 10 years of global distributed development at Philips, derived from about 200 projects.
We discuss the experience and lessons learnt from multi-site development. Main lessons learned are that explicit agreements and ways of working should be defined for the following areas needing the most attention; team coordination and communication, requirements and architectures, integration, and configuration management.
In addition, we discuss the experience gained from subcontracting software development to suppliers.
Main lesson learned from subcontracting software development is the need for explicit attention and ways of working with respect to selection of suppliers, specification of the work to be subcontracted and establishment and content of the contract.
Original languageEnglish
Pages (from-to)647-660
JournalEmpirical Software Engineering
Volume12
Issue number6
DOIs
Publication statusPublished - 2007
MoE publication typeA1 Journal article-refereed

Fingerprint

Software engineering
Specifications
Communication

Keywords

  • Philips
  • Software development
  • Globally distributed software

Cite this

Kommeren, Rob ; Parviainen, Päivi. / Philips experiences in global distributed software development. In: Empirical Software Engineering. 2007 ; Vol. 12, No. 6. pp. 647-660.
@article{3640fa78955c42b78d7c64f46f5ad9cc,
title = "Philips experiences in global distributed software development",
abstract = "Global software development is increasingly common. Main expected benefits are improvements in time-to-market efficiency and access to greater—and less costly—resources. A number of problems are still to be solved before the full potential of global development can be obtained. This paper describes the experience of over 10 years of global distributed development at Philips, derived from about 200 projects. We discuss the experience and lessons learnt from multi-site development. Main lessons learned are that explicit agreements and ways of working should be defined for the following areas needing the most attention; team coordination and communication, requirements and architectures, integration, and configuration management. In addition, we discuss the experience gained from subcontracting software development to suppliers. Main lesson learned from subcontracting software development is the need for explicit attention and ways of working with respect to selection of suppliers, specification of the work to be subcontracted and establishment and content of the contract.",
keywords = "Philips, Software development, Globally distributed software",
author = "Rob Kommeren and P{\"a}ivi Parviainen",
year = "2007",
doi = "10.1007/s10664-007-9047-3",
language = "English",
volume = "12",
pages = "647--660",
journal = "Empirical Software Engineering",
issn = "1382-3256",
publisher = "Springer",
number = "6",

}

Philips experiences in global distributed software development. / Kommeren, Rob; Parviainen, Päivi (Corresponding Author).

In: Empirical Software Engineering, Vol. 12, No. 6, 2007, p. 647-660.

Research output: Contribution to journalArticleScientificpeer-review

TY - JOUR

T1 - Philips experiences in global distributed software development

AU - Kommeren, Rob

AU - Parviainen, Päivi

PY - 2007

Y1 - 2007

N2 - Global software development is increasingly common. Main expected benefits are improvements in time-to-market efficiency and access to greater—and less costly—resources. A number of problems are still to be solved before the full potential of global development can be obtained. This paper describes the experience of over 10 years of global distributed development at Philips, derived from about 200 projects. We discuss the experience and lessons learnt from multi-site development. Main lessons learned are that explicit agreements and ways of working should be defined for the following areas needing the most attention; team coordination and communication, requirements and architectures, integration, and configuration management. In addition, we discuss the experience gained from subcontracting software development to suppliers. Main lesson learned from subcontracting software development is the need for explicit attention and ways of working with respect to selection of suppliers, specification of the work to be subcontracted and establishment and content of the contract.

AB - Global software development is increasingly common. Main expected benefits are improvements in time-to-market efficiency and access to greater—and less costly—resources. A number of problems are still to be solved before the full potential of global development can be obtained. This paper describes the experience of over 10 years of global distributed development at Philips, derived from about 200 projects. We discuss the experience and lessons learnt from multi-site development. Main lessons learned are that explicit agreements and ways of working should be defined for the following areas needing the most attention; team coordination and communication, requirements and architectures, integration, and configuration management. In addition, we discuss the experience gained from subcontracting software development to suppliers. Main lesson learned from subcontracting software development is the need for explicit attention and ways of working with respect to selection of suppliers, specification of the work to be subcontracted and establishment and content of the contract.

KW - Philips

KW - Software development

KW - Globally distributed software

U2 - 10.1007/s10664-007-9047-3

DO - 10.1007/s10664-007-9047-3

M3 - Article

VL - 12

SP - 647

EP - 660

JO - Empirical Software Engineering

JF - Empirical Software Engineering

SN - 1382-3256

IS - 6

ER -