Reducing Requirement Incorrectness and Coping with Its Negative Impact in Information System Development Projects

The negative impact of incorrect requirements on information system development (ISD) project performance has long been acknowledged. This study addresses the problem of incorrect requirements by proposing a model that combines the error reduction and coping concepts proposed by Field, Ritzman, Safizadeh, and Downing (2006) with the view that ISD is a knowledge-intensive process. The model hypothesizes that when developers and users possess an understanding of each other's primary domain of knowledge, the prevention of incorrect requirements and the mitigation of the negative consequences of incorrect requirements tend to improve project performance. Data collected from 250 ISD professionals on the basis of their experiences of recently completed ISD projects confirmed all of our hypotheses. The results demonstrate that the eliciting of incorrect requirements can be reduced when users and developers possess cross-domain understanding and when requirement analysis methodologies and techniques are available. Furthermore, the negative impact of incorrect requirements on project performance can be mitigated when developers have sufficient ISD knowledge and behavioral knowledge.

[1]  Roland T. Mittermeir,et al.  Alternatives to Overcome the Communications Problem of Formal Requirements Analysis. , 1982 .

[2]  C. Fornell,et al.  Evaluating structural equation models with unobservable variables and measurement error. , 1981 .

[3]  William L. Fuerst,et al.  Information technology and sustained competitive advantage: a resource-based analysis , 1995 .

[4]  Jack Shih-Chieh Hsu,et al.  The impacts of user review on software responsiveness: Moderating requirements uncertainty , 2008, Inf. Manag..

[5]  Larry E. Toothaker,et al.  Multiple Regression: Testing and Interpreting Interactions , 1991 .

[6]  Eileen M. Trauth,et al.  Critical Skills and Knowledge Requirements of IS Professionals: A Joint Academic/Industry Investigation , 1995, MIS Q..

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

[8]  Robert P. Bostrom,et al.  Successful application of communication techniques to improve the systems development process , 1989, Inf. Manag..

[9]  L. Sproull,et al.  Coordinating Expertise in Software Development Teams , 2000 .

[10]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[11]  Howard B. Lee,et al.  Foundations of Behavioral Research , 1973 .

[12]  Gary Klein,et al.  User and developer common knowledge: Effect on the success of information system development projects , 2009 .

[13]  Jacob Cohen,et al.  Applied multiple regression/correlation analysis for the behavioral sciences , 1979 .

[14]  Jay R. Galbraith.  Designing Complex Organizations , 1973 .

[15]  Dale Goodhue,et al.  Develop Long-Term Competitiveness through IT Assets , 1996 .

[16]  Albert L. Lederer,et al.  Nine management guidelines for better cost estimating , 1992, CACM.

[17]  Blaize Horner Reich,et al.  A Temporal Model of Information Technology Project Performance , 2007, J. Manag. Inf. Syst..

[18]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[19]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[20]  Tuure Tuunanen,et al.  A Contigency Model for Requirements Development , 2007, J. Assoc. Inf. Syst..

[21]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[22]  Sun-Jen Huang,et al.  An empirical analysis of risk components and performance on software projects , 2007, J. Syst. Softw..

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

[24]  Lior Fink,et al.  Exploring the perceived business value of the flexibility enabled by information technology infrastructure , 2009, Inf. Manag..

[25]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[26]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[27]  Daniel Robey,et al.  A Social Process Model of User-Analyst Relationships , 1992, MIS Q..

[28]  Izak Benbasat,et al.  Business Competence of Information Technology Professionals: Conceptual Development and Influence on IT-Business Partnerships , 2004, MIS Q..

[29]  Alistair G. Sutcliffe,et al.  Experience with SCRAM, a SCenario Requirements Analysis Method , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

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

[31]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[32]  Kate M. Kaiser,et al.  Evolution of Offshore Software Development: From Outsourcing to Cosourcing , 2004, MIS Q. Executive.

[33]  KeilMark,et al.  Software project risks and their effect on outcomes , 2004 .

[34]  Charles E. Downing,et al.  Uncertainty Reduction Approaches, Uncertainty Coping Approaches, and Process Performance in Financial Services , 2006, Decis. Sci..

[35]  Qing Hu,et al.  Assimilation of Enterprise Systems: The Effect of Institutional Pressures and the Mediating Role of Top Management , 2007, MIS Q..

[36]  M. Hoegl,et al.  Teamwork Quality and the Success of Innovative Projects , 2001 .

[37]  Capers Jones,et al.  Assessment and control of software risks , 1994, Yourdon Press Computing Series.

[38]  Richard L. Daft,et al.  Organizational information requirements, media richness and structural design , 1986 .

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

[40]  L. J. Williams,et al.  Recent Advances in Causal Modeling Methods for Organizational and Management Research , 2003 .

[41]  Ephraim R. McLean,et al.  Expertise Integration and Creativity in Information Systems Development , 2005, J. Manag. Inf. Syst..

[42]  Patricia J. Guinan,et al.  Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach , 1998, Inf. Syst. Res..

[43]  Richard P. Bagozzi,et al.  Assessing Construct Validity in Organizational Research , 1991 .

[44]  Amrit Tiwana,et al.  Information Systems Project Continuation in Escalation Situations: A Real Options Model , 2006, Decis. Sci..

[45]  Sarma R. Nidumolu.  A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software Development Projects , 1996, J. Manag. Inf. Syst..

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

[47]  Gordon W. Cheung,et al.  Evaluating Goodness-of-Fit Indexes for Testing Measurement Invariance , 2002 .

[48]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..

[49]  Judy E. Scott,et al.  Relational Alignment in Offshore IS Outsourcing , 2009, MIS Q. Executive.

[50]  Denise Silver,et al.  Joint Application Development , 1995 .

[51]  D. Campbell,et al.  Convergent and discriminant validation by the multitrait-multimethod matrix. , 1959, Psychological bulletin.

[52]  Elena Karahanna,et al.  Antecedents of IS Strategic Alignment: A Nomological Network , 2009, Inf. Syst. Res..

[53]  Mary C. Jones,et al.  IS project team performance: An empirical assessment , 1996, Inf. Manag..

[54]  Mark Keil,et al.  How Software Project Risk Affects Project Performance: An Investigation of the Dimensions of Risk and an Exploratory Model , 2004, Decis. Sci..

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

[56]  Scott B. MacKenzie,et al.  Common method biases in behavioral research: a critical review of the literature and recommended remedies. , 2003, The Journal of applied psychology.

[57]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[58]  Richard E. Fairley,et al.  Risk management for software projects , 1994, IEEE Software.

[59]  Thiagarajan Ravichandran,et al.  Quality Management in Systems Development: An Organizational System Perspective , 2000, MIS Q..

[60]  E. Burton Swanson,et al.  Management information requirements assessment: the state of the art , 1979, DATB.

[61]  Nirup M. Menon,et al.  Managing Technology and Administration Innovations: Four Case Studies on Software Reuse , 2004, J. Assoc. Inf. Syst..

[62]  Milton Harris,et al.  Organization Design , 2000, Manag. Sci..

[63]  Paul A. Pavlou,et al.  Psychological Contract Violation in Online Marketplaces: Antecedents, Consequences, and Moderating Role , 2005, Inf. Syst. Res..

[64]  Andrew P. Sage,et al.  Handbook of Systems Engineering and Management , 2011 .

[65]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[66]  K. Weick.  The social psychology of organizing , 1969 .

[67]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

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

[69]  Amrit Tiwana,et al.  Governance-Knowledge Fit in Systems Development Projects , 2009, Inf. Syst. Res..

[70]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[71]  Kathy Schwalbe,et al.  Information Technology Project Management , 1999 .

[72]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[73]  Mark Keil,et al.  Software project risks and their effect on outcomes , 2004, CACM.