Systems Development Outsourcing: Lessons from Litigation
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.
KeywordsSystem Requirement Major League Baseball Relational Governance Software Development Project Customer Relationship Management System
Unable to display preview. Download preview PDF.
- 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
- F. Brooks, The Mythical Man Month: Essays on Software Engineering (Reading MA: Addison-Wesley, 1995).Google Scholar
- 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
- M.C. Lacity and R. Hirschheim, ‘The Information Systems Outsourcing Bandwagon’, Sloan Management Review, 35:1 (1993) 73–86.Google Scholar
- 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
- F.W. McFarlan and R.L. Nolan, ‘How to Manage an IT Outsourcing Alliance’, Sloan Management Review, 36:2 (1995) 9–23.Google Scholar
- 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