Catastrophe Disentanglement: Getting 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.”
A 10-Step Process to Identify Severely Trobuled 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 tandard 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
- Define 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
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.
Review By: Mark L. Krug
02/26/2007The author's writing style is practical and organized. Many of the recommendations are fresh approaches to old problems. It is apparent that the author has both theoretical and practical experience within the field and therefore approaches the subject from a more objective point of view.
The book is organized according to the normal thought process a person would go through while managing a project. This allows the reader to concentrate on the material presented rather than flipping pages back and forth to refer to figures, tables, and previously covered materials. The author’s writing style is free-flowing, making it less like a text book and more as if presented in a conference or lecture.
It gives good examples of typical project behavior and suggests practical risk management/remediation practices for common problems found within the typical project/development lifecycle. Many of the recommendations are fresh approaches to old problems. It is apparent that the author has both theoretical and practical experience within the field and therefore approaches the subject from a more objective point of view. The topic is handled with pose and grace. While I did not agree with all of the author’s approaches, it is clear that there was a great deal of research and practical experience behind the suggested actions presented within the book.
The material is free of controversial statements that you often find in books covering this subject, and I was able to read the book free of bias or gut reaction. That reason alone makes the author more credible, and I recommend this book to anyone who oversees the development cycle of any product, whether it be hard or soft in nature.
While not lengthy, this book has a lot to say. It doesn't try to cover too much within its pages and therefore covers its topic thoroughly. Even if you do not agree with every assumption, conclusion, or suggested action contained within the pages of this book, you will have contemplated some innovative and viable alternatives to your normal practices.