The Fixed-Price Contract: A Challenge for the Software Development Project

Describing the software development project between customer and supplier at the contracting level as interaction of the involved organizations in terms of game theory, we can show that the parties are in a dilemma situation regarding the effort for closing the gaps of incomplete requirement specifications. Incomplete, ambiguous, and changing requirements are the number one reason for failure of software development projects. Customer and supplier have to interchange information for closing requirement gaps. However, gathering and interchanging information generates undesirable costs. The most commonly used contract model is a fixed-price contract. Under this condition, the supplier is forced to cooperate, whereas the customer prefers to defect regarding closing requirement gaps. In support of our theoretical argument, we carried out an empirical investigation. We derive suggestions for improving the fixed-price contract design of software development projects as well as for the cooperation behavior during the project.

[1]  Frank Maurer,et al.  Comparing Decision Making in Agile and Non-agile Software Organizations , 2007, XP.

[2]  Robert Axelrod Die Evolution der Kooperation: Aus dem Amerikanischen übersetzt und mit einem Nachwort von Werner Raub und Thomas Voss , 2009 .

[3]  Alistair Cockburn,et al.  The end of software engineering and the start of economic-cooperative gaming , 2004, Comput. Sci. Inf. Syst..

[4]  Rory V. O'Connor,et al.  Improving Software Development Process through Economic Mechanism Design , 2010, EuroSPI.

[5]  Lior Fink,et al.  Ex post adaptations and hybrid contracts in software development services , 2013 .

[6]  Deborah Tollefsen,et al.  Organizations as true believers , 2002 .

[7]  Cecil Eng Huang Chua,et al.  Client strategies in vendor transition: A threat balancing perspective , 2012, J. Strateg. Inf. Syst..

[8]  Joseph Natovich,et al.  Vendor Related Risks in IT Development: A Chronology of an Outsourced Project Failure , 2003, Technol. Anal. Strateg. Manag..

[9]  William R. King,et al.  Predictors of Formal Control Usage in IT Outsourcing Partnerships , 2008, Inf. Syst. Res..

[10]  Yogesh Kumar Dwivedi,et al.  IS/IT Project Failures: A Review of the Extant Literature for Deriving a Taxonomy of Failure Factors , 2013, TDIT.

[11]  Ah-Hwee Tan,et al.  Agent-Based Virtual Humans in Co-Space: An Evaluative Study , 2012, 2012 IEEE/WIC/ACM International Conferences on Web Intelligence and Intelligent Agent Technology.

[12]  Charlie C. Chen,et al.  Relationships among interpersonal conflict, requirements uncertainty, and software project performance , 2011 .

[13]  Orit Hazzan,et al.  Social Perspective of Software Development Methods: The Case of the Prisoner Dilemma and Extreme Programming , 2005, XP.

[14]  Mark Keil,et al.  'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects , 2004, DATB.

[15]  Des Greer,et al.  Towards an understanding of the causes and effects of software requirements change: two case studies , 2012, Requirements Engineering.

[16]  Hans Ulrich Buhl,et al.  Die Verantwortung der Wirtschaftsinformatik bei IT-Großprojekten , 2011, Wirtsch..

[17]  N. Kano,et al.  Attractive Quality and Must-Be Quality , 1984 .

[18]  Khaled El Emam,et al.  A Replicated Survey of IT Software Project Failures , 2008, IEEE Software.

[19]  Kyle J. Mayer,et al.  Relationships and Hybrid Contracts: An Analysis of Contract Choice in Information Technology , 2004 .

[20]  Saleem Abuleil,et al.  A Taxonomy of an IT Project Failure: Root Causes , 2009 .

[21]  Jochen Gläser,et al.  Experteninterviews und qualitative Inhaltsanalyse , 2010 .

[22]  Michael D. Myers,et al.  The qualitative interview in IS research: Examining the craft , 2007, Inf. Organ..