Summary of Software Development Failures

Looking for the book?
We have the summary! Get the key insights in just 10 minutes.

Software Development Failures book summary
Start getting smarter:
or see our plans

Rating

7 Overall

6 Applicability

10 Innovation

5 Style

Recommendation

Here’s a two-ingredient recipe for disaster: take a big organization and mix in ambitious plans for a state-of-the-art software system. The disaster already happened at the IRS and Denver International Airport, both victims of software development missteps. Such failures are common, costly and all-too-avoidable, writes academic Kweku Ewusi-Mensah. While his prose can be dry, the examples he uses prove quite juicy. A little common sense could have saved the IRS billions and the Denver airport millions. Both fell victim to surprisingly basic pitfalls, such as unclear or unrealistic goals and over optimistic expectations that inexperienced people could get the job done. Ewusi-Mensah convincingly argues that organizations need to share such learning experiences, although he acknowledges that would mark a reversal from common practice. getAbstract.com recommends this book to managers and engineers involved in developing software. This cautionary tale could save your neck.

In this summary, you will learn

  • What software development failure is;
  • Why this problem is common, costly and hard to solve; and
  • How your company can avoid software development meltdowns.
 

About the Author

Kweku Ewusi-Mensah is a professor of computer information systems at Loyola Marymount University.

 

Summary

A Costly but Little Understood Problem
Public and private organizations waste billions of dollars every year on software development projects that collapse before completion. The financial consequences can be harsh and can draw very negative media attention. For the most part, organizations...

Get the key points from this book in 10 minutes.

For you

Find the right subscription plan for you.

For your company

We help you build a culture of continuous learning.

 or log in

Comment on this summary

More on this topic

Customers who read this summary also read

More by category