Structure and perceived effectiveness of software development subunits: a task contingency analysis
Journal of Management Information Systems - Special issue: Collaboration technology, modeling, and end-user computing for the 1990s
An approach to partitioning programs on the functional basis and applications
Microprocessing and Microprogramming
Incomplete information, task assignment, and managerial control systems
Management Science
Information Technology and Management
Bridging Space Over Time: Global Virtual Team Dynamics and Effectiveness
Organization Science
The Mutual Knowledge Problem and Its Consequences for Dispersed Collaboration
Organization Science
Just Right Outsourcing: Understanding and Managing Risk
Journal of Management Information Systems
A Contingency Approach to Software Project Coordination
Journal of Management Information Systems
Vendors' perspectives on trust and control in offshore information systems outsourcing
Information and Management
Boundary spanning in offshored ISD projects: a project social capital perspective
Proceedings of the special interest group on management information system's 47th annual conference on Computer personnel research
Antecedents and consequences of team memory in software development projects
Information and Management
Information and Software Technology
Test strategies in distributed software development environments
Computers in Industry
Hi-index | 0.00 |
This paper presents two case studies of offshored software tasks. The success of such tasks is critically dependent on managing an inherent interdependence between onshore and offshore teams. In one case study, both teams belong to the vendor organization, while in the other they are affiliated respectively with client and vendor. It is shown that that interdependence is best addressed through procedural coordination, which entails two complementary strategies. The first consists of carefully specifying and partitioning tasks, and the second of implementing integration mechanisms to bridge communication gaps. Despite contextual differences, the two case studies offer common lessons.