Toward predicting software development success from the perspective of practitioners: an exploratory Bayesian model

Software development project managers may need to focus on particular issues during the development process for a variety of reasons, including limited resources. This study utilized a survey to ask software practitioners, who are at the core of development, to provide insight into some of the important early non-technical issues of software development, including those related to sponsor/senior management, customer/users and requirements management. Proposed relationships among these early items, and their relationship to software practitioners' perception of project success, were quantitatively represented through a proposed Bayesian Belief Network. The concept of ‘success’ was derived from a pilot study of practitioners and was ‘defined’ as (a) there is a project plan, (b) the project is well planned, (c) practitioners have a sense of achievement while working on a project, (d) practitioners have a sense of doing a good job (i.e. delivered quality) while working on a project, and (e) requirements are accepted by the development team as realistic/achievable. The proposed causal model provided quantitative evidence that reaching agreement with customers/users on requirements, a high level of customer/user participation, and users who make adequate time for requirements gathering have the largest direct impacts on project success among the investigated items. The proposed model identified the following as the critical chain of events for success: (1) Having a sponsor throughout the project, (2) users who make adequate time for requirements gathering, (3) a high level of customer/user participation in the development process, and (4) agreement on requirements between customer/users and the development team.

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

[2]  Tor Guimaraes,et al.  Successful Strategies for User Participation in Systems Development , 1997, J. Manag. Inf. Syst..

[3]  June M. Verner,et al.  Software practitioner's perception of project success: a pilot study , 2002 .

[4]  Roger S. Pressman,et al.  Manager: Fear of Trying - The Plight of Rookie Project Managers , 1998, IEEE Softw..

[5]  Barry Boehm,et al.  Top 10 list [software development] , 2001 .

[6]  Barry W. Boehm,et al.  Software Defect Reduction Top 10 List , 2001, Computer.

[7]  Stan Rifkin Why Software Process Innovations Are Not Adopted , 2001, IEEE Softw..

[8]  R. Kelly Rainer,et al.  The Keys to Executive Information Systems Success , 1995, J. Manag. Inf. Syst..

[9]  Earl R. Babbie,et al.  The practice of social research , 1969 .

[10]  Richard E. Neapolitan,et al.  Learning Bayesian networks , 2007, KDD '07.

[11]  Kurt R. Linberg Software developer perceptions about software project failure: a case study , 1999, J. Syst. Softw..

[12]  Naveed Saleem,et al.  An Empirical Test of the Contingency Approach to User Participation in Information Systems Development , 1996, J. Manag. Inf. Syst..

[13]  Hedley Rees,et al.  Limited-Dependent and Qualitative Variables in Econometrics. , 1985 .

[14]  Robert L. Glass,et al.  Evolving a new theory of project success , 1999, Commun. ACM.

[15]  Tom DeMarco,et al.  Management-aided software engineering , 1994, IEEE Software.

[16]  June M. Verner,et al.  Case study: factors for early prediction of software development success , 2002, Inf. Softw. Technol..

[17]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[18]  Ian Witten,et al.  Data Mining , 2000 .

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

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

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

[22]  Andrea Taylor-Cummings,et al.  Bridging the user-IS gap: a study of major information systems projects , 1998, J. Inf. Technol..

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

[24]  J. Daniel Couger,et al.  Motivators vs. demotivators in the IS environment , 1988 .

[25]  Buford D. Tackett,et al.  Process Control for Error-Free Software: A Software Success Story , 1999, IEEE Softw..

[26]  Andrea Taylor-Cummings,et al.  Bridging the User–is Gap: A Study of Major Information Systems Projects , 1998 .

[27]  David Baccarini,et al.  The Logical Framework Method for Defining Project Success , 1999 .

[28]  Gary Klein,et al.  Software development risks to project effectiveness , 2000, J. Syst. Softw..

[29]  Julia Hodgson,et al.  The chimpanzees' tea party: a new metaphor for project managers , 2003, J. Inf. Technol..

[30]  Norman E. Fenton,et al.  Software metrics: successes, failures and new directions , 1999, J. Syst. Softw..

[31]  Norman E. Fenton,et al.  Making decisions: using Bayesian nets and MCDA , 2001, Knowl. Based Syst..

[32]  G. Maddala Limited-dependent and qualitative variables in econometrics: Introduction , 1983 .

[33]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[34]  Dianne M. Finkelstein,et al.  A Beginner's Guide to Structural Equation Modeling , 2005, Technometrics.

[35]  Timo Saarinen,et al.  An expanded instrument for evaluating information system success , 1996, Inf. Manag..

[36]  David Gefen,et al.  What do software practitioners really think about project success: an exploratory study , 2005, J. Syst. Softw..

[37]  June M. Verner,et al.  In the 25 years since The Mythical Man-Month what have we learned about project management? , 1999, Inf. Softw. Technol..

[38]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[39]  Kwasi Amoako-Gyampah,et al.  When Is User Involvement Not User Involvement , 1997 .

[40]  C. Clavadetscher User involvement: key to success , 1998 .

[41]  James E. Hunton,et al.  Effects of User Participation in Systems Development: A Longitudinal Field Experiment , 1997, MIS Q..

[42]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

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

[44]  Norman E. Fenton,et al.  Software metrics: roadmap , 2000, ICSE '00.

[45]  Robert L. Glass,et al.  Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering , 2001, IEEE Softw..

[46]  Tom DeMarco,et al.  Peopleware: Productive Projects and Teams , 1987 .

[47]  Michael J. Ginzberg,et al.  Early Diagnosis of MIS Implementation Failure: Promising Results and Unanswered Questions , 1981 .

[48]  B. Hawkins,et al.  A framework: , 2020, Harmful Interaction between the Living and the Dead in Greek Tragedy.

[49]  Mary Lacity,et al.  Managing client/server implementations: today's technology, yesterday's lessons , 1997, J. Inf. Technol..