Global software development at siemens: experience from nine projects

Herbsleb, J.D.; Paulish, Daniel J.; Bass, M.

doi:10.1109/icse.2005.1553598

Cited by 94 publications

(123 citation statements)

References 16 publications

Supporting

Mentioning

116

Contrasting

Unclassified

Order By: Relevance

“…Herbsleb et al [3,40] highlighted the relevance of tracking information in projects where code is developed in more than one site, increasing the visibility of the work in progress [4]. In agüe software development, Brede et al [41 ] used agüe artifacts, such as product backlogs, sprint backlogs, and burn-down charts to measure the level of work performed by a team.…”

Section: Measures On Project Statusmentioning

confidence: 99%

An exploratory study in communication in Agile Global Software Development

Yagüe

Garbajosa

Díaz

et al. 2016

Computer Standards & Interfaces

View full text Add to dashboard Cite

Keywords:Global Distributed Software Development Agüe Exploratory research Tools and technologies Infrastructure Global software development (GSD) is gaining ever more relevance. Although communication is key in the exchange of information between team members, multi-site software development has introduced additional obstacles (different time-zones and cultures, IT infrastructure, etc.) and delays into the act of communication, which is already problematic. Communication is even more critical in the case of Agile Global Software Development (AGSD) in which communication plays a primary role. This paper reports an exploratory study of the effects of tools supporting communication in AGSD. More precisely, this paper analyses the perception of team members about communication infrastructures in AGSD. The research question to which this study responds concerns how development teams perceive the communication infrastructure while developing products using agile methodologies. Most previous studies have dealt with communication support from a highly technological media tool perspective. In this research work, instead, observations were obtained from three perspectives: communication among team members, communication of the status of the development process, and communication of the status of the progress of the product under development. It has been possible to show that team members perceive advantages to using media tools that make them feel in practice that teams are co-located, such as smartboards supported by effident video-tools, and combining media tools with centralized repository tools, with information from the process development and product characteristics, that allow distributed teams to effectively share information about the status of the project/process/product during the development process in order to overeóme some of the still existing problems in communication in AGSD.

show abstract

Section: Measures On Project Statusmentioning

confidence: 99%

An exploratory study in communication in Agile Global Software Development

Yagüe

Garbajosa

Díaz

et al. 2016

Computer Standards & Interfaces

View full text Add to dashboard Cite

show abstract

“…As geographic and temporal distance increases, a wide variety of impediments to coordination are introduced (see generally [10,12,22,40,41,53]. GSD projects are diverse, of course, and experience various disruptions to different degrees.…”

Section: What Is Different About Global Development?mentioning

confidence: 99%

Global Software Engineering: The Future of Socio-technical Coordination

Herbsleb

2007

Future of Software Engineering (FOSE '07)

479

406

View full text Add to dashboard Cite

“…In the mentioned research [5], the authors point out that the learning curve of the new site takes time due to substantial training required for those who are unfamiliar with the product. Lack of domain and product expertise, in fact, is frequently referred to as one of the key challenges when starting global software development [6], [7], [8].…”

Section: Related Workmentioning

confidence: 99%

Software Product Transfers: Lessons Learned from a Case Study

mite

Wohlin

2010

2010 5th IEEE International Conference on Global Software Engineering

View full text Add to dashboard Cite

Abstract-Although global software work nowadays is not a phenomenon, research and practice is still addressing the complexities associated with the new forms of work enabled through globalization. 'Go global' strategies usually prescribe two alternative approaches: distribution of software development activities across several locations, or re-location of work to another site. This research paper focuses on the latter approach that is called software product transfers and discusses findings from an empirical case study conducted in Ericsson. The observations indicate that transferring software work from one site to another site of the same company is a challenging endeavor. Furthermore, practices used in colocated projects do not necessarily lead to a desired outcome. The paper provides an overview of the challenges and highlights practical advice for handling software product transfers.

show abstract

Global software development at siemens: experience from nine projects

Cited by 94 publications

References 16 publications

An exploratory study in communication in Agile Global Software Development

An exploratory study in communication in Agile Global Software Development

Global Software Engineering: The Future of Socio-technical Coordination

Software Product Transfers: Lessons Learned from a Case Study

Contact Info

Product

Resources

About