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

Journal of Information Technology

Volumn 20, Issue 3, 2005, Pages 187-200

  Procaccino, J Drew ^a   Verner, June M ^b,c   Darter, Marvin E ^a   Amadio, William J ^a  

^a RIDER UNIVERSITY   (United States)

^b CSIRO   (Australia)

^c UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

Motivation; Practitioners; Software; Success; Team

Indexed keywords

EID: 30744453280     PISSN: 02683962     EISSN: 14664437     Source Type: Journal    
DOI: 10.1057/palgrave.jit.2000044     Document Type: Article

References (50)

1. Amoako-Gyampah, K. and White, K.B. (1997). When is user involvement not user involvement, Information Strategy: The Executive's Journal 13(4): 40-45.
2. Babbie, E. (2001). The Practice of Social Research, 9th edn, Belmont, California: Wadsworth/Thomson Learning.
3. Baccarini, D. (1999). The logical framework method for defining project success, Project Management Journal 30(4): 25-32.
4. Boehm, B.W. (1981). Software Engineering Economics, Englewood Cliffs, NJ: Prentice-Hall.
5. Boehm, B.W. (1991). Software Risk Management: Principles and practices, IEEE Software 8(1): 32-41.
6. Boehm, B.W. and Basili, V.R. (2001). Software defect reduction top 10 list, IEEE Computer 34(1): 135-137.
7. Brady, S. and DeMarco, T. (1994). Management-aided software engineering, IEEE Software 11(6): 25-32.
8. Brooks Jr, P.P. (1995). The Mythical Man-Month, Reading, MA: Addison-Wesley.
9. Clavadetscher, C. (1998). User Involvement: Key to success, IEEE Software 15(2): 30, 32.
10. Couger, D. (1988). Motivators vs. demotivators in the IS environment, Journal of Systems Management 39(6): 36-41.
11. DeMarco, T. and Lister, T. (1999). Peopleware: Productive projects and teams, 2nd edn., New York, NY: Dorset House Publishing Co.
12. Drummond, H. and Hodgson, J. (2003). The Chimpanzees' Tea Party: A new metaphor for project managers, Journal of Information Technology 18(3): 151-158.
13. Ewusi-Mensah, K. (1997). Critical numbers in abandoned information systems development projects, Communications of The ACM 40(9): 74-80.
14. Fenton, N.E. and Neil, M. (1999). Software Metrics: Successes, failures and new directions, Journal of Systems and Software 47(2-3): 149-157.
15. Fenton, N.E. and Neil, M. (2000). Software Metrics: A roadmap, International Conference On Software Engineering, Limerick, Ireland.
16. Fenton, N.E. and Neil, M. (2001). Making Decisions: Using Bayesian nets and MCDA, Knowledge-Based Systems 14(7); 307-325.
17. Ginzberg, M.J. (1981). Early diagnosis of MIS implementation failure promising results and unanswered questions, Management Science 27(4): 459-478.
18. Glass, R.L. (1998). Software Runaways, Upper Saddle River, NJ: Prentice-Hall.
19. Glass, R.L. (1999). Evolving a new theory of project success, Communications of The ACM 42(11): 17-19.
20. Glass, R.L. (2001). Frequently forgotten fundamental facts about software engineering, IEEE Software 18(3): 110-112.
21. Herzberg, F. (1987). One More Time: How do you motivate employees? Harvard Business Review 65(5): 109-120.
22. Humphrey, W.S. (1989). Managing The Software Process, New York, NY: Addison-Wesley.
23. Hunton, J.E. and Beeler, J.D. (1997). Effects of User Participation in Systems Development: A longitudinal field experiment, MIS Quarterly 21(4): 359-388.
24. Jiang, J. and Klein, G. (2000). Software development risks to project effectiveness, Journal of Systems and Software 52(1): 3-10.
25. Keil, M., Cule, P.E., Lyytinen, K. and Schmidt, R.C. (1998). A framework for identifying software project risks, Communications of The ACM 41(11): 76-83.
26. Leffingwell, D. and Widrig, D. (2000). Managing Software Requirements: A unified approach, New York, NY: Addison-Wesley.
27. Linberg, K.R. (1999). Software Developer Perceptions About Software Project Failure; A case study, The Journal of Systems and Software 49(2/3): 177-192.
28. Maddala, G.S. (1983). Limited-Dependent and Qualitative Variables In Economics, Cambridge, UK: Cambridge University Press.
29. McConnell, S. (1996). Rapid Development, Redmond, Washington: Microsoft Press.
30. McKeen, J.D. and Guimaraes, T. (1997). Successful strategies for user participation in systems development, Journal of Management Information Systems 14(2): 133-150.
31. Neapolitan, R.E. (2004). Learning Bayesian Networks, Upper Saddle River, NJ: Pearson Prentice Hall.
32. Nidumolu, S.R. (1996). Standardization, requirements uncertainty and software project performance, Information & Management 31(3): 135-150.
33. Pinto, J.K. and Slevin, D.P. (1988). Project Success: Definitions and measurement techniques, Project Management Journal 19(1): 67-72.
34. Pressman, R. (1998). Fear of Trying: The plight of rookie project managers, IEEE Software 15(1): 50-51, 54.
35. Procaccino, J.D. and Verner, J.M. (2001). Early risk factors for software development, in K. Maxwell, S. Oligny, R. Kusters and E. van Veenendaal (eds.) Proceedings of the 12th European Software Control and Metrics Conference in London, 2-4th April, 107-116.
36. Procaccino, J.D. and Verner, J.M. (2002). Software Practitioner's Perception of Project Success: A pilot study, International Journal of Computers, The Internet & Management 10(1): 20-30.
37. Procaccino, J.D., Verner, J.M., Overmyer, S.P. and Darter, M.E. (2002). Case Study: Factors for early prediction of software development success, Journal of Information & Software Technology 44(1): 53-62.
38. Procaccino, J.D., Verner, J.M., Shelfer, K.M. and Gefen, D. (2004). What do software practitioners really think about project success: an exploratory study, Journal of Systems and Software, accepted.
39. Rainer, R.K. and Watson, H.J. (1995). The keys to executive information systems success, Journal of Management Information Systems 12(2): 83-98.
40. Ravichandran, T. and Rai, A. (2000). Quality Management In Systems Development: An organizational system perspective, MIS Quarterly 24(3): 381-416.
41. Saarinen, T. (1996). An expanded instrument for evaluating information system success, Information & Management 31(2): 103-118.
42. Saleem, N. (1996). An empirical test of the contingency approach to user participation in information systems development, Journal of Management Information Systems 13(1): 145-166.
43. Schmidt, R., Lyytinen, K., Keil, M. and Cule, P. (2001). Identifying Software Project Risks: An international Delphi study, Journal of Management Information Systems 17(4): 5-36.
44. Schumacker, R.E. and Lomax, R.G. (1996). A Beginner's Guide To Structural Equation Modeling, Mahwah, NJ: Lawrence Erlbaum Associates.
45. Standish Group, CHAOS,http://www.standishgroup.com/sample_research/chaos_1994_1.php,1994 (accessed 12th January 2005).
46. Subramanian, A. and Lacity, M.C. (1997). Managing Client/Server Implementations: Today's technology, yesterday's lessons, Journal of Information Technology 12(3): 169-186.
47. Tackett, B.D. and Van Doren, B. (1999). Process Control For Error-Free Software: A software success story, IEEE Software 16(3): 24-29.
48. Taylor-Cummings, A. (1998). Bridging The User-IS GAP; A study of major information systems projects, Journal of Information Technology 13(1); 29-54.
49. Verner, J.M., Overmyer, S.P. and McCain, K.W. (1999). In the 25 years since the mythical man-month what have we learned about project management? Information and Software Technology 41(14): 1021-1026.
50. Witten, I.H. and Frank, E. (2000). Data Mining, San Francisco, CA: Morgan Kaufman.