REVIEW - Death March - The Complete Software Developer's Guide to Surviving "mission Impossible" Projects

Title:

Death March - The Complete Software Developer's Guide to Surviving "mission Impossible" Projects

Author:

Edward Yourdon

ISBN:

0137483104

Publisher:

Prentice Hall Ptr (1997)

Pages:

218pp

Reviewer:

X

Reviewed:

April 1999

Rating:

★★★☆☆

Is it useful? I found it so. Its easily read and fairly concise (roughly 200 pages). I'd give it "3 out of 5", with the possibility of that score rising if it proves to be useful in the long term.

Hell. Edward Yourdon describes different kinds of project hells in this book.

It catalogues death march projects as "Kamikaze", "Mission Impossible", "Suicide" and "Ugly" - those descriptions are used as a short hand throughout the book.

At the end of each chapter is a set of references and lengthy e-mail quotes from people who have been on Death Marches.

There are 7 chapters - Introduction (to Death Marches), Politics, Negotiations, People in Death March Projects, Processes, Tools and Technology and Death March as a way of Life.

The "politics" and "negotiations" chapters were interesting - there are plenty of lessons to be learnt there - concentrating on software engineering has left me inexperienced in these topics. I always wondered why key people laughed at recommendations from PeopleWare . Maybe if I understand these chapters better, I'll be able to get more PeopleWare things done to get projects running more smoothly.

Ed Yourdon's main message (to me) seemed to be !TRIAGE! - that wasn't particularly useful as I'm already an expert at triage. It was nice to see that others use the same term, as well.

The thing I liked about it most was Ed describing the differing views and positions of the different players in the project (Owner, Customer, Shareholder, Stakeholder, Champion). This book can be a very good tool to maintain a sense of perspective and help appreciate the concerns of non- developers involved with the project.

Is it useful? I found it so. Its easily read and fairly concise (roughly 200 pages). I'd give it "3 out of 5", with the possibility of that score rising if it proves to be useful in the long term.

There's more to this book. It was hard enough getting time to read the book. There is even less time available to write polished reviews about it.


Book cover image courtesy of Open Library.