A case study book dealing with software failed projects, e.g. The Denver Airport problem. It categorizes these projects into the following areas: 1)Project objectives were not fully specified. 2)Projects were poorly planned. 3)Enabling project technology was not fully understood. 4)Absence of management methodology. 5)Insufficient expertise. 6)Lack of understanding of the risks involved. These cases will show how failure might have been avoided, how they might have been completed, on time and within budget. This book should be seen as a companion volume to Yourdon's DEATH MARCH book and Jones ASSESSMENT & CONTROL OF SOFTWARE PROJECTS, both of which will be extensively referenced in the book.
"synopsis" may belong to another edition of this title.
What you can learn from 16 colossal software disasters.
If failure teaches more than success, imagine how much you can learn from the most catastrophic software development failures of all time. In Software Runaways, software failure expert Robert Glass shows exactly what went wrong in 16 colossal software disasters -- and how to keep it from happening to you.
Glass goes behind the scenes of those awful projects you've seen on the nightly news -- the Denver Airport baggage system, the IRS modernization --and a host of less well-publicized failures that are equally instructive. Along the way, he identifies six characteristics of projects likely to fail -- and some of them will surprise you.
Software Runaways brings a software engineer's perspective to projects like:
Glass presents specific lessons to be learned from each failure, and shows how to "sniff out" runaway projects early enough to take action. He also considers the typical responses to potential runaways, including risk management and issue management, demonstrating their strengths and weaknesses.
Whether you're an IT executive, project manager or developer, Software Runaways helps you learn from someone else's mistakes -- and that's a whole lot less painful than making them yourself!
"About this title" may belong to another edition of this title.
Book Description Prentice Hall, 1997. Book Condition: New. Brand New, Unread Copy in Perfect Condition. A+ Customer Service! Summary: 1. Introduction.What Is a Software Runaway? The Cries of Software Crisis. "Crunch Mode" and the "Death March" Project. Some Relevant Research Findings.2. Software Runaway War Stories.Project Objectives Not Fully Specified. Bad Planning and Estimating. Technology New to the Organization. Inadequate/No Project Management Methodology. Insufficient Senior Staff on the Team. Poor Performance by Suppliers of Hardware/Software. Other' Performance (Efficiency) Problems.3. Software Runaway Remedies.Risk Management. Issue Management. Remedies Attempted During Runaways. Remedies Envisioned for the Future.4. Conclusions. Index. Bookseller Inventory # ABE_book_new_013673443X
Book Description Prentice Hall, 1997. Paperback. Book Condition: New. New book. May have light shelf wear. Bookseller Inventory # 160719172
Book Description Book Condition: Brand New. Book Condition: Brand New. Bookseller Inventory # 97801367344371.0
Book Description Prentice Hall, 1997. Paperback. Book Condition: New. book. Bookseller Inventory # 013673443X
Book Description Prentice Hall, 1997. Paperback. Book Condition: New. 1. Bookseller Inventory # DADAX013673443X
Book Description Prentice Hall. Book Condition: New. Brand New. Bookseller Inventory # 013673443X
Book Description Prentice Hall, 1997. Paperback. Book Condition: New. Bookseller Inventory # P11013673443X
Book Description Prentice Hall, 1997. Paperback. Book Condition: Brand New. 1st edition. 288 pages. 9.00x6.25x1.00 inches. In Stock. Bookseller Inventory # zk013673443X
Book Description Prentice Hall, 1997. Book Condition: New. Brand new! Please provide a physical shipping address. Bookseller Inventory # 9780136734437
Book Description Prentice-Hall. Book Condition: New. pp. 288. Bookseller Inventory # 4688245