HomeGroupsTalkMoreZeitgeist
Search Site
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.

Results from Google Books

Click on a thumbnail to go to Google Books.

Loading...

Software Failure: Management Failure: Amazing Stories and Cautionary Tales (Wiley Series in Software Engineering Practic

by Stephen Flowers

MembersReviewsPopularityAverage ratingConversations
12None1,614,642 (4)None
It?s fine to celebrate success but it is more important to heed the lessons of failure Bill Gates Good judgement is usually the result of experience. And experience is frequently the result of bad judgement. But to learn from the experience of others requires those who have the experience to share the knowledge with those who follow Barry LePatner Many millions are wasted every year on building, extending and fixing information systems that either do not perform as expected, do not work at all or are abandoned before they are implemented. Details of the events that contribute are too often shrouded in non-disclosure contracts and confidentiality agreements, the causes of errors never to be aired and analysed by those in a position to prevent similar blunders in future. Newspaper reports of spectacular fiasco?s provide as much hard evidence as most are likely to hear, but what proportion of substandard and unwieldy IS developments come into being and continue in use simply because they are not so flawed as to be totally useless? The purpose of this book is to bring together material about a number of significant information systems which did not perform as originally envisaged and to provide a coherent account of the surrounding events. The author identifies major causal events and draws from them management lessons. In case after case critical factors point out strategic, organizational or resource problems rather than technical bugs. The value of comparing these woeful tales is to become aware of the way that organizations can become locked in a cycle of failure, condemned to repeat the mistakes of others. Read and be warned! Learn from the experiences of? The Performing Right Society The Confirm Development Socrates Reservation System California?s DMV The London Ambulance Service Denver Airports? Baggage System TAURUS at the London Stock Exchange The Pineapple Group B of A Masternet The IRS and, unfortunately, more?… (more)
None
Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

No reviews
"In the final chapter he develops the concept of critical failure factors and shows, quite conclusively, that there is more to failure than systems failure: indeed, that the causes of failure lie as much with failures of management and project direction as with the software."
 
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Epigraph
Dedication
First words
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Original language
Canonical DDC/MDS
Canonical LCC

References to this work on external resources.

Wikipedia in English

None

It?s fine to celebrate success but it is more important to heed the lessons of failure Bill Gates Good judgement is usually the result of experience. And experience is frequently the result of bad judgement. But to learn from the experience of others requires those who have the experience to share the knowledge with those who follow Barry LePatner Many millions are wasted every year on building, extending and fixing information systems that either do not perform as expected, do not work at all or are abandoned before they are implemented. Details of the events that contribute are too often shrouded in non-disclosure contracts and confidentiality agreements, the causes of errors never to be aired and analysed by those in a position to prevent similar blunders in future. Newspaper reports of spectacular fiasco?s provide as much hard evidence as most are likely to hear, but what proportion of substandard and unwieldy IS developments come into being and continue in use simply because they are not so flawed as to be totally useless? The purpose of this book is to bring together material about a number of significant information systems which did not perform as originally envisaged and to provide a coherent account of the surrounding events. The author identifies major causal events and draws from them management lessons. In case after case critical factors point out strategic, organizational or resource problems rather than technical bugs. The value of comparing these woeful tales is to become aware of the way that organizations can become locked in a cycle of failure, condemned to repeat the mistakes of others. Read and be warned! Learn from the experiences of? The Performing Right Society The Confirm Development Socrates Reservation System California?s DMV The London Ambulance Service Denver Airports? Baggage System TAURUS at the London Stock Exchange The Pineapple Group B of A Masternet The IRS and, unfortunately, more?

No library descriptions found.

Book description
Haiku summary

Current Discussions

None

Popular covers

Quick Links

Rating

Average: (4)
0.5
1
1.5
2
2.5
3 1
3.5
4
4.5
5 1

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 204,402,719 books! | Top bar: Always visible