Vendor Related Risks in IT Development: A Chronology of an Outsourced Project Failure

Many organizations consider outsourcing their information technology (IT) development projects as an attractive risk-mitigating approach. In such an engagement, the vendor may agree to complete a project for a fixed cost and according to a defined time schedule. Nevertheless, while the vendor is liable for the traditional project risks, other forms of risk may arise, which are the vendor risks. This paper presents a recent case study of a project failure that demonstrates some of the major vendor risks and their contribution to system development failure. The risks discussed in the paper are: (a) Adversarial relationships and loss of trust between the vendor and the client; (b) Vendor management de-escalation of commitment; and (c) Di.fficulry in breaking the contractual engagement. The case shows that IT outsourcing, an organization might not eliminate the traditional IT project risks but rather exchange them for equally fatal vendor risks. Furthermore, the case raises doubts regarding the effectiveness of the contract-driven control approach to mitigate vendor risks. This paper suggest that perhaps, since placing all risks on the vendor is impractical, a partnership approach of sharing risks and rewards may be more effective in bringing the client and the vendor to successful project outcomes.

[1]  D. Gefen,et al.  Nurturing clients’ trust to encourage engagement success during the customization of ERP systems , 2002 .

[2]  M. Keil,et al.  The effects of sunk cost and project completion on information technology project escalation , 1995 .

[3]  T. Das,et al.  Between Trust and Control: Developing Confidence in Partner Cooperation in Alliances , 1998 .

[4]  Timo Saarinen,et al.  Understanding Runaway Information Technology Projects: Results from an International Research Program Based on Escalation Theory , 1994, J. Manag. Inf. Syst..

[5]  Leslie P. Willcocks,et al.  Global Information Technology Outsourcing: In Search of Business Advantage , 2001 .

[6]  Paul J. Hart,et al.  Power and Trust: Critical Factors in the Adoption and Use of Electronic Data Interchange , 1997 .

[7]  Effy Oz,et al.  When professional standards are lax: the CONFIRM failure and its lessons , 1994, CACM.

[8]  Steven Tadelis,et al.  Incentives Versus Transaction Costs: A Theory of Procurement Contracts , 2001 .

[9]  Rajiv Sabherwal,et al.  The role of trust in outsourced IS development projects , 1999, CACM.

[10]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[11]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[12]  Young-Gul Kim,et al.  Effect of Partnership Quality on IS Outsourcing Success: Conceptual Framework and Empirical Validation , 1999, J. Manag. Inf. Syst..

[13]  A. C. Day,et al.  The State of Software. , 1975 .

[14]  S. Ghoshal,et al.  Bad for Practice: A Critique of the Transaction Cost Theory , 1996 .

[15]  Suresh L. Konda,et al.  Taxonomy-Based Risk Identification , 1993 .

[16]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[17]  R. Acevedo,et al.  Research report , 1967, Revista odontologica de Puerto Rico.

[18]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.