How To Survive Doomed Software Projects

June 1, 2004
Before reviewing the second edition of this book, I dusted off my copy of the original. It had served me well as a software-development manager. It had even helped me spot troubled projects that I should avoid. In addition, the first volume of...

Before reviewing the second edition of this book, I dusted off my copy of the original. It had served me well as a software-development manager. It had even helped me spot troubled projects that I should avoid. In addition, the first volume of Death March had several good suggestions for surviving projects that had already gone astray.

The second edition has been expanded to include several new chapters that cover topics like critical-chain scheduling, time management, and software-development process dynamics. Most of the original material has been expanded as well. For example, there is a more detailed discussion of Abdel-Hamid's software process model, which focuses on the challenges of hiring and assimilating new programmers. One of my favorite expanded chapters is titled, "Simulators and 'War Games.'" It includes more specifics as to the benefits of practicing death-march projects before they begin.

One of the more unusual aspects of this book is the inclusion of actual e-mail correspondences from colleagues of the author. These correspondences provide a wealth of real-world observations and wit. I applaud the author for giving credit to these fine contributors.

This is definitely a book for the working software developer and manager. One of the most telling passages comes from the section of best and worst practices. The author writes simply, "If I've recommended something that doesn't make sense and that the project team can't carry out with enthusiasm and sincerity, then ignore it!"

Death March, Second Edition, was written by Edward Yourdon. Prentice Hall is the publisher (ISBN 0-1314-635X). The book sells for $29.95.

About the Author

John Blyler

John Blyler has more than 18 years of technical experience in systems engineering and program management. His systems engineering (hardware and software) background encompasses industrial (GenRad Corp, Wacker Siltronics, Westinghouse, Grumman and Rockwell Intern.), government R&D (DoD-China Lake) and university (Idaho State Univ, Portland State Univ, and Oregon State Univ) environments. John is currently the senior technology editor for Penton Media’s Wireless Systems Design (WSD) magazine. He is also the executive editor for the WSD Update e-Newsletter.

Mr. Blyler has co-authored an IEEE Press (1998) book on computer systems engineering entitled: ""What's Size Got To Do With It: Understanding Computer Systems."" Until just recently, he wrote a regular column for the IEEE I&M magazine. John continues to develop and teach web-based, graduate-level systems engineering courses on a part-time basis for Portland State University.

John holds a BS in Engineering Physics from Oregon State University (1982) and an MS in Electronic Engineering from California State University, Northridge (1991).

Sponsored Recommendations

Comments

To join the conversation, and become an exclusive member of Electronic Design, create an account today!