Catastrophe Disentanglement: Getting Software Projects Back on Track (Paperback)

~ (Author)

Editorial Reviews

Product Description

"There are many books available on software risks and software failures. There are very few books that provide step-by-step information on getting troubled software projects back on track. This book provides detailed guidelines for software project recovery. Some of the steps the author recommends may be unpleasant, but all are important." --Capers Jones, chief scientist emeritus at Software Productivity Research LLC "This is a well-conceived, well-written, interesting book about an important topic. The author is right in saying that no one else has covered this particular facet of project failure." --Robert L. Glass, publisher of the Software Practitioner A 10-STEP PROCESS TO IDENTIFY SEVERELY TROUBLED PROJECTS AND AVOID COSTLY FAILURE It's a software development nightmare: a project that's rapidly spiraling out of control...or already a disaster. Conventional project management techniques won't save these projects: there are no standard rescue processes to follow. You need something radically different: Catastrophe Disentanglement. Drawing on in-depth data from hundreds of development organizations, E.M.Bennatan presents a proven, 10-step program for rescuing any project that's worth saving. You'll find specific guidance for addressing massive budget overruns, schedule slippage, poor quality--or all three at once. Using practical examples drawn from decades of hands-on experience as a software development leader and consultant, Bennatan shows how to *Evaluate where your project really stands *Align your project's developers, managers, and customers *Defi ne the minimum acceptable project goals that are achievable *Replan your project to successfully deliver the new minimum goals *Identify risks in your revised project and create effective contingency plans *Install an "early warning system" to keep your rescued project from slipping back toward catastrophe Catastrophe Disentanglement is an effective, comprehensive approach to software project rescue. Whenever projects are in trouble--whether you are a senior manager, project manager, team member, or software customer--this book could save your career. Preface xi Chapter 1 An Introduction to Catastrophe Disentanglement 1 Chapter 2 When Is a Project a Catastrophe?1 5 Chapter 3 Step 1--Stop 43 Chapter 4 Step 2--Assign an Evaluator 57 Chapter 5 Step 3--Evaluate the Project 73 Chapter 6 Step 4--Evaluate the Team 95 Chapter 7 Step 5--Define Minimum Goals 113 Chapter 8 Step 6--Can Minimum Goals Be Achieved? 133 Chapter 9 Step 7--Rebuild the Team 147 Chapter 10 Step 8--Risk Analysis 169 Chapter 11 Step 9--Revise the Plan 189 Chapter 12 Step 10--Create an Early Warning System 209 Chapter 13 Epilogue: Putting the Final Pieces in Place 233 References 245 Glossary 255 About the Author 257 Index 259 A(c) Copyright Pearson Education. All rights reserved.

From the Back Cover

“There are many books available on software risks and software failures. There are very few books that provide step-by-step information on getting troubled software projects back on track. This book provides detailed guidelines for software project recovery. Some of the steps the author recommends may be unpleasant, but all are important.”

—Capers Jones, chief scientist emeritus at Software Productivity Research LLC

 

“This is a well-conceived, well-written, interesting book about an important topic. The author is right in saying that no one else has covered this particular facet of project failure.”

—Robert L. Glass, publisher of the Software Practitioner

 

A 10-STEP PROCESS TO IDENTIFY SEVERELY TROUBLED PROJECTS AND AVOID COSTLY FAILURE

It’s a software development nightmare: a project that’s rapidly spiraling out of control...or already a disaster. Conventional project management techniques won’t save these projects: there are no standard rescue processes to follow. You need something radically different: Catastrophe Disentanglement.

 

Drawing on in-depth data from hundreds of development organizations, E.M. Bennatan presents a proven, 10-step program for rescuing any project that’s worth saving. You’ll find specific guidance for addressing massive budget overruns, schedule slippage, poor quality—or all three at once. Using practical examples drawn from decades of hands-on experience as a software development leader and consultant, Bennatan shows how to

• Evaluate where your project really stands
• Align your project’s developers, managers, and customers
• Defi ne the minimum acceptable project goals that are achievable
• Replan your project to successfully deliver the new minimum goals
• Identify risks in your revised project and create effective contingency plans
• Install an “early warning system” to keep your rescued project from slipping back toward catastrophe

Catastrophe Disentanglement is an effective, comprehensive approach to software project rescue. Whenever projects are in trouble—whether you are a senior manager, project manager, team member, or software customer—this book could save your career.

 

Preface    xi

Chapter 1  An Introduction to Catastrophe Disentanglement    1

Chapter 2  When Is a Project a Catastrophe?    15

Chapter 3  Step 1–Stop    43
Chapter 4  Step 2–Assign an Evaluator    57
Chapter 5  Step 3–Evaluate the Project    73
Chapter 6  Step 4–Evaluate the Team    95
Chapter 7  Step 5–Define Minimum Goals    113
Chapter 8  Step 6–Can Minimum Goals Be Achieved?    133
Chapter 9  Step 7–Rebuild the Team    147
Chapter 10  Step 8–Risk Analysis    169
Chapter 11  Step 9–Revise the Plan    189
Chapter 12  Step 10–Create an Early Warning System    209
Chapter 13  Epilogue: Putting the Final Pieces in Place    233
References    245
Glossary    255

About the Author    257

Index    259

 

© Copyright Pearson Education. All rights reserved.

See all Editorial Reviews

Product Details

• Paperback: 288 pages
• Publisher: Addison-Wesley Professional; 1 edition (April 21, 2006)
• Language: English
• ISBN-10: 0321336623
• ISBN-13: 978-0321336620
• Product Dimensions: 9.1 x 6 x 0.7 inches
• Shipping Weight: 12.8 ounces (View shipping rates and policies)
• Average Customer Review: 5.0 out of 5 stars  See all reviews (6 customer reviews)
• Amazon.com Sales Rank: #958,527 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

2 of 3 people found the following review helpful:

5.0 out of 5 stars Tackles a problem not well-covered by other books..., May 30, 2006

By	Thomas Duff "Duffbert" (Portland, OR United States) - See all my reviews (TOP 50 REVIEWER)    (REAL NAME)

There are plenty of books that try to help you keep your project on track. But what happens when you are sitting on a catastrophe and you don't know how to salvage it? E. M. Bennatan fills a necessary niche with the book Catastrophe Disentanglement : Getting Software Projects Back on Track.

Contents: An Introduction To Catastrophe Disentanglement; When Is A Project A Catastrophe?; Step 1 - Stop; Step 2 - Assign An Evaluator; Step 3 - Evaluate The Project; Step 4 - Evaluate The Team; Step 5 - Define Minimum Goals; Step 6 - Can Minimum Goals Be Achieved?; Step 7 - Rebuild The Team; Step 8 - Risk Analysis; Step 9 - Revise The Plan; Step 10 - Create An Early Warning System; Epilogue - Putting The Final Pieces In Place; References; Glossary; About The Author; Index

If you're in IT for any length of time, you'll be part of a project that is massively over budget or late. Rather than just continue the death by 1000 cuts or a quick mercy killing, Bennatan presents a ten step process that allows an organization to take a (hopefully) objective look at the project and decide what can possibly be saved from it. I was impressed that it wasn't a long drawn-out procedure either. The plan calls for an evaluator (or a small team for huge projects) to come in and quickly assess the environment... what's been done, the climate of the team, and what could be redefined as a "minimum system". At the end of this process, the organization should be able to either kill it off with the knowledge that it can't be saved, or continue on with a redefined set of deliverables that are achievable. It won't be everything that was originally wanted, but it will be more than you'd get by letting it die. I was also impressed with the "What Can Go Wrong (And What To Do About It)" section in each step. He doesn't present this as some cut and dried panacea that will flow smoothly every time. It may not be an easy task, but the book will give you the help you need to make it all work.

Definitely a book that is worthy to be on every IT project manager's bookshelf, as you *will* need it some day...

2 of 3 people found the following review helpful:

5.0 out of 5 stars A useful addition to my software development library, May 9, 2006

By	Jerry Lessor "Jerry L." (Boca Raton, Florida) - See all my reviews

Good book, good subject, well covered. The book builds an organized process around the rescue of a failed (or failing) software project. The steps are easy to read and understand, and seem well thought out. Some good methods for identifying projects headed for serious trouble. Also, some useful guidance on how to handle political (not just technical) problems. Obviously, the result of significant experience. Well recommended.

5.0 out of 5 stars Good book; well planned and written, June 12, 2007

By	Ken L. Davis "Ken Davis" (Charlotte, NC USA) - See all my reviews (REAL NAME)

I bought this book for general project evaluation purposes, for a project that I was called in on that was in trouble.

Well worth the read - a lot of it is just good common sense, straightforward project management process, but it provided a great roadmap for validation of my plan to put the project back on track.

Definitely would recommend it - it's an easy read; I finished it in under 5 hours on the flight out, complete with note-taking. Kudos to E.M. Brennatan for writing this in a straightforward fashion.