Systems Development Outsourcing: Lessons from Litigation

  • Mike Chiasson
  • Al Dexter
  • David Wotherspoon


Organisations outsource their information technology (IT) for multiple reasons: to increase service and product flexibility; reduce costs of production; restructure internal IT staff; realise cost savings through lower-priced contracts for maintenance of in-house information systems; and to gain knowledge about new trends in IT (McFarlan & Nolan, 1995). In this paper, we focus on system development outsourcing (Lacity & Hirschheim, 1993; Sabherwal, 2003), which we define as the purchase and development of IT in order to develop organisationally specific information systems.


System Requirement Major League Baseball Relational Governance Software Development Project Customer Relationship Management System 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. B. Bahli and S. Rivard, ‘A Validation of Measures Associated with the Risk Factors in Information Technology Outsourcing’, HEC Working Papers (02-05), November (2002).Google Scholar
  2. F. Brooks, The Mythical Man Month: Essays on Software Engineering (Reading MA: Addison-Wesley, 1995).Google Scholar
  3. R.S. Fortgang, D.A. Lax, and J.K. Sebenius, ‘Negotiating the Spirit of the Deal’, Harvard Business Review (February 2003) 66–75.Google Scholar
  4. M.C. Lacity and R. Hirschheim, ‘The Information Systems Outsourcing Bandwagon’, Sloan Management Review, 35:1 (1993) 73–86.Google Scholar
  5. M.C. Lacity and L.P. Willcocks, ‘An Empirical Investigation of Information Technology Sourcing Practices: Lessons from Experience’, MIS Quarterly, 22:3 (1998) 363–408.CrossRefGoogle Scholar
  6. D. Malhotra and K. Murnighan, ‘The Effects of Contracts on Interpersonal Trust’, Administrative Sciences Quarterly, 47:3 (2002) 534–559.CrossRefGoogle Scholar
  7. D.R. Marburger, ‘Arbitrator Compromise in Final Offer Arbitration: Evidence from Major League Baseball’, Economic Inquiry, 42:1 (2004), 60–68.CrossRefGoogle Scholar
  8. B.L. Marcolin, ‘The Spiraling Effect of IS Outsourcing Contract Interpretations’, in R. Hirschheim, A. Heinzl, and J. Dibbern (eds), Information Systems Outsourcing: Enduring Themes, Emergent Patterns and Future Directions (Springer-Verlag: Germany, 2002).Google Scholar
  9. F.W. McFarlan and R.L. Nolan, ‘How to Manage an IT Outsourcing Alliance’, Sloan Management Review, 36:2 (1995) 9–23.Google Scholar
  10. L. Poppo and T. Zenger, ‘Do Formal Contracts and Relational Governance Function as Substitutes or Complements?’, Strategic Management Journal, 23 (2001) 707–725.CrossRefGoogle Scholar
  11. R. Sabherwal, ‘The Evolution of Coordination in Outsourced Software Development Projects: A Comparison of Client and Vendor Perspectives’, Information & Organization, 13 (2003) 153–202.CrossRefGoogle Scholar
  12. M. Schrage, ‘Lies, Damned Lies and Requirements; The Road to Applications Development Hell is Paved with Rigid Code Requirements’, CIO, 17:2 (2003) 60–62.Google Scholar
  13. Standish Group. Extreme Chaos. (2001).Google Scholar
  14. L. Willcocks, M. Lacity and T. Kern, ‘Risk Mitigation in IT Outsourcing Strategy Revisited: Longitudinal Case Research at LISA’, Journal of Strategic Information Systems, 8 (1999) 285–314.CrossRefGoogle Scholar

Copyright information

© Mike Chiasson, Al Dexter and David Wotherspoon 2005

Authors and Affiliations

  • Mike Chiasson
  • Al Dexter
  • David Wotherspoon

There are no affiliations available

Personalised recommendations