Software Development Failures: Anatomy of Abandoned Projects (Mit Press) by Kweku Ewusi-Mensah

Software Development Failures: Anatomy of Abandoned Projects (Mit Press)

Kweku Ewusi-Mensah
290 pages
MIT Press
Aug 2003
Hardcover
Computers & Internet WSBN
0
Readers
0
Reviews
0
Discussions
0
Quotes
An empirically based study of why software development failures happen, and the lessons we can learn.Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable riskthat it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved.
Join the conversation

No discussions yet. Join BookLovers to start a discussion about this book!

No reviews yet. Join BookLovers to write the first review!

No quotes shared yet. Join BookLovers to share your favorite quotes!

Earn Points
Your voice matters. Every comment, review, and quote earns you reward points redeemable for Bitcoin.
Comment +5 pts Review +20 pts Quote +7 pts Upvote +1 pt
BookMatch Quiz
Find books similar to this one
About this book
Pages 290
Publisher MIT Press
Published 2003
Readers 0