A Practical Management and Engineering Approach to Offshore Collaboration

Cusick, James; Prasad, Alpana

doi:10.1109/ms.2006.118

Cited by 50 publications

(52 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Paasivaara and colleagues [55] identify a number of practices used and deemed successful in GSD projects, including frequent deliveries and establishing links among peers. Cusick and Prasad [20] suggest a collection of practices, some of which are adaptations of traditional practices (e.g., issue tracking, short phases, small deliverables), while some are unique to GSD (e.g. ensuring that domain expertise is retained both onshore and offshore).…”

Section: Research Summarymentioning

confidence: 99%

See 1 more Smart Citation

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

Section: Research Summarymentioning

confidence: 99%

“…Our understanding of how various practices play together takes two forms. First, sets of compatible or complementary practices are bundled together and recommended as a whole [20,60]. The other approach is to address the practices in a purely atomic manner, matching them for example to problems they address [7].…”

Section: Research Challengesmentioning

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

“…Similar scenarios are also used by e.g. Boos et al (2005, p. 25), Cusick andPrasad (2006, pp. 22 f), or King andTorkzadeh (2008, pp.…”

Section: Outsourcing Offshoring and Application Development Based Omentioning

confidence: 94%

A Method to Evaluate the Suitability of Requirements Specifications for Offshore Projects

2010

View full text Add to dashboard Cite

The success of an offshore application development project based on division of labor on the one hand heavily depends on the quality of the developed requirements specifications. On the other hand, even a poor quality of requirements specifications can possibly be compensated during the course of the offshore project. In this contribution, we present a method to evaluate the suitability of requirements specifications for an offshore project. For this purpose, we consider eight quality criteria and five potentially compensating factors. The application of the method is illustrated by a complex case study that has been conducted with an industry partner.

show abstract

“…Our defined aspect Collaboration structure is dedicated to these questions of global collaborations. This aspect is aimed at determining the approach of development task allocation between locations based on collaboration goals, at creating roles and responsibilities along with the way of distributing them; at defining an organizational structure and peer-to-peer connections between sites [16,20,[31][32][33]46]. Clear understanding of work division, roles and responsibilities might help to decrease coordination and project management e↵orts when actual global software development takes place.…”

Section: Collaboration Structurementioning

confidence: 99%

“…The first model was considered as a typical outsourcing model where most of the intellectual work stays onsite and only actual software development tasks are transferred o↵shore. In this model, requirements creation, system analysis, design are done onsite, while coding and testing phases can be performed jointly with work division, for example, by modules [16,[31][32][33]. The main challenges of this kind of task distribution consist of troublesome system requirements clarification, system integration and bug fixing along with coordination and control e↵orts.…”

Section: Collaboration Structurementioning

confidence: 99%