Beyond user acceptance: The determinants of the intention to produce user created contents on the internet

This paper summarizes an empirical investigation that explored biased project reporting by Information Systems (IS) professionals. The study is based on a survey of 91 professionals who were involved with system implementations in various governmental agencies. Our investigation assessed the impact of project importance, control, structure, and size on biasing behaviors. To formulate the research hypotheses for our study, we adopted a Message Exchange Perspective. The results reveal that IS professionals are more likely to bias their project status communications when working in projects that are (1) large, (2) important, and (3) lack controls. The practical and research implications of our findings are discussed.

[1]  Woody M. Liao,et al.  Motivating Truthful Upward Communication of Private Information: An Experimental Study of Mechanisms From Theory and Practice , 2000 .

[2]  Sarma R. Nidumolu.  The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable , 1995, Inf. Syst. Res..

[3]  G. Mellinger.  Interpersonal trust as a factor in communication. , 1956, Journal of abnormal psychology.

[4]  Mark Keil,et al.  A Framework for Assessing the Reliability of Software Project Status Reports , 2002 .

[5]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[6]  David Baccarini,et al.  The concept of project complexity—a review , 1996 .

[7]  S. Grover,et al.  The truth, the whole truth, and nothing but the truth: The causes and management of workplace lying , 2005 .

[8]  Mark Keil,et al.  The effects of optimistic and pessimistic biasing on software project status reporting , 2007, Inf. Manag..

[9]  Mark Keil,et al.  Blowing the whistle on troubled software projects , 2001, CACM.

[10]  Fredric M. Jablin.  Superior–subordinate communication: The state of the art. , 1979 .

[11]  Donald T. Campbell,et al.  Systematic Error on the Part of Human Links in Communication Systems , 1958, Inf. Control..

[12]  C. O'Reilly.  The Intentional Distortion of Information in Organizational Communication: A Laboratory and Field Investigation , 1978 .

[13]  Charalambos L. Iacovou,et al.  The linkage between reporting quality and performance in IS projects , 2007, Inf. Manag..

[14]  Katja Hölttä-Otto,et al.  Estimating factors affecting project task size in product development-an empirical study , 2006, IEEE Transactions on Engineering Management.

[15]  Mark Keil,et al.  Reporting bad news on software projects: the effects of culturally constituted views of face‐saving , 2007, Inf. Syst. J..

[16]  William H. Read,et al.  Upward Communication in Industrial Hierarchies , 1962 .

[17]  Suzanne Rivard,et al.  An Integrative Contingency Model of Software Project Risk Management , 2001, J. Manag. Inf. Syst..

[18]  Mark Keil,et al.  Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..

[19]  Jeffrey K. Pinto,et al.  The causes of project failure , 1990 .

[20]  Hedda Hopper,et al.  The whole truth and nothing but , 1963 .

[21]  Janet Fulk,et al.  Distortion of Communication in Hierarchical Relationships , 1986 .

[22]  David F. Bean.  Equivocal Reporting: Ethical Communication Issues , 2001 .

[23]  Chiara Francalanci,et al.  Predicting the implementation effort of ERP projects: empirical evidence on SAP/R3 , 2001, J. Inf. Technol..

[24]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[25]  Ralf Müller,et al.  Determinants for external communications of IT project managers , 2003 .

[26]  Charalambos L. Iacovou.  Managing MIS project failures : a crisis management perspective , 1999 .

[27]  Mark Keil,et al.  The challenge of accurate software project status reporting: a two-stage model incorporating status errors and reporting bias , 2002, IEEE Trans. Engineering Management.

[28]  Sarma R. Nidumolu.  Standardization, requirements uncertainty and software project performance , 1996, Inf. Manag..

[29]  Sidney Rosen,et al.  The Reluctance to Transmit Bad News , 1975 .

[30]  Mark Keil,et al.  The reluctance to report bad news on troubled software projects: a theoretical model , 2003, Inf. Syst. J..

[31]  Izak Benbasat,et al.  Development of an Instrument to Measure the Perceptions of Adopting an Information Technology Innovation , 1991, Inf. Syst. Res..

[32]  Robert E. Spekman,et al.  Characteristics of partnership success: Partnership attributes, communication behavior, and conflict resolution techniques , 1994 .

[33]  J. C. Henderson,et al.  Managing I/S Design Teams: A Control Theories Perspective , 1992 .

[34]  Russell L. Purvis,et al.  Controlling Information Systems Development Projects: The View from the Client , 2002, Manag. Sci..

[35]  Weidong Xia,et al.  Development of a Measure to Assess the Complexity of Information Systems Development Projects , 2002, ICIS.

[36]  Stanley Baiman,et al.  AGENCY RESEARCH IN MANAGERIAL ACCOUNTING: A SECOND LOOK. , 1990 .

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