Software developer perceptions about software project failure: a case study

Abstract Software development project failures have become commonplace. With almost daily frequency these failures are reported in newspapers, journal articles, or popular books. These failures are defined in terms of cost and schedule over-runs, project cancellations, and lost opportunities for the organizations that embark on the difficult journey of software development. Rarely do these accounts include perspectives from the software developers that worked on these projects. This case study provides an in-depth look at software development project failure through the eyes of the software developers. The researcher used structured interviews, project documentation reviews, and survey instruments to gather a rich description of a software development project failure. The results of the study identify a large gap between how a team of software developers defined project success and the popular definition of project success . This study also revealed that a team of software developers maintained a high-level of job satisfaction despite their failure to meet schedule and cost goals of the organization.

[1]  Robert L. Glass,et al.  Building Quality Software , 1991 .

[2]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

[3]  T. M. Amabile.  The social psychology of creativity: A componential conceptualization. , 1983 .

[4]  Luke Hohmann,et al.  Journey of the Software Professional , 1996 .

[5]  Robert C. Ford,et al.  Successful project teams: a study of MIS managers , 1992 .

[6]  J. D. Couger,et al.  Creativity/Innovation in Information Systems Organizations Introduction to Session , 1996, Proceedings of HICSS-29: 29th Hawaii International Conference on System Sciences.

[7]  Nancy G. Leveson,et al.  Safeware: System Safety and Computers , 1995 .

[8]  D. Keirsey.  Please Understand Me II: Temperament, Character, Intelligence , 1998 .

[9]  Teresa M. Amabile,et al.  Assessing the Work Environment for Creativity , 1996 .

[10]  Ephraim R. McLean,et al.  The importance of salary on job and career attitudes of information systems professionals , 1996, Inf. Manag..

[11]  Steve McConnell.  Avoiding Classic Mistakes , 1996, IEEE Softw..

[12]  W. Wayt Gibbs,et al.  Software's Chronic Crisis , 1994 .

[13]  D. Keirsey,et al.  Please Understand Me: Character and Temperament Types , 1978 .

[14]  Charles K. Woodruff.  Managing for results: An examination of professional group perceptions of organizational practices , 1990, Inf. Manag..

[15]  Watts S. Humphrey,et al.  Managing Technical People: Innovation, Teamwork, and the Software Process , 1996 .

[16]  Stanley H. Cohen,et al.  Change: Principles of problem formation and problem resolution. , 1975 .

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

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

[19]  Anthony M. Armocida.  The Seven Habits of Highly Effective People , 1992 .

[20]  Ronald H. Rasch,et al.  Factors Affecting Software Developers' Performance: An Integrated Approach , 1992, MIS Q..

[21]  Larry Constantine,et al.  Constantine on Peopleware , 1995 .

[22]  Edward Edward Yourdon,et al.  Death March: The Complete Software Developer's Guide to Surviving Mission Impossible Projects , 1999 .

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

[24]  P. Watzlawick,et al.  Change. Principles of Problem Formation and Problem Resolution. New York (Norton) 1974. , 1974 .

[25]  Gerald M. Weinberg,et al.  Quality software management: volume 4: anticipating change , 1997 .

[26]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[27]  A. Maslow.  The Farther Reaches of Human Nature , 1971 .

[28]  R. Likert,et al.  New ways of managing conflict , 1977 .

[29]  J. Daniel Couger,et al.  Motivating and managing computer personnel , 1980 .

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

[31]  D. Weiss,et al.  Manual for the Minnesota Satisfaction Questionnaire. , 1967 .

[32]  S. Covey.  Principle-Centered Leadership , 1989 .