Death March: The Complete Software Developer’s Guide to Surviving Mission Yourdon walks step-by-step through the entire project life cycle, showing both. Death March: The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects. Author: Edward Edward Yourdon. Death March by Edward Yourdon. Notes taken by Matthias Günther | 2 minutes read. p Marine Corps mentality => real programmers don’t need sleep; p
|Published (Last):||11 June 2015|
|PDF File Size:||1.24 Mb|
|ePub File Size:||15.49 Mb|
|Price:||Free* [*Free Regsitration Required]|
Every programmer should have read this once before getting stuck ddeath a death march project. One of the greatest values of the book is that it can teach you how to recognize a death march, understand why it got desth way, and then you can make an educated decision as to whether you want to be involved or not. Or geeking in a sideshow. The functionality, features, performance requirements, or other technical aspects of the project are twice what they would be under normal circumstances.
I found multiple spelling errors, even though this is the second edition.
As Ed Yourdon says in the preface to Death March “The wonderful thing about the title is that I don’t even have to explain it. But, after reading inspirational books like “The Mythical Man Month” and “Peopleware” in the past this book seems like one I wish I would have just given up on and shelved.
Essentially, that’s a project where you have too little resources in terms of time or personnel. This review is probably going to be a lot like the one for the previous book – “Practical guide to defect prevention”, so please have a look at that one. Lots of good suggestions and analysis that is still valid. I’m having a hard enough time just reading them.
It was interesting to read and skim through the e-mails Mr. It confirmed much of what I knew was wrong with the project. And it’s not a bad idea for the marketing and sales people who sometime veath the death marches to give it a look, too. Software development and software engineering are the fields in which practitioners first applied the term to these project management practices.
Death March by Edward Yourdon
Contrariwise, if you are looking for shorter hours and longer vacations and early retirement, you are in the wrong job. No two are alike and there is no reason to expect them to be. I recommend it to all project manager just to read and recognize yourself: But, after reading inspirational books like “The Mythical Man Month” and “Peopleware” in the past this book seems like one I wish I would have just given up on and s I strongly yourxon this book.
The book is so so. Perhaps you need to take up bank robbing. The general feel of the project reflects that of an actual death march because project members are forced to continue the project by their superiors against their better judgment.
Crunch Mode: programming to the extreme – What Causes a Death March?
A death march project is one for which an unbiased, objective risk assessment which includes an assessment of technical risks, personnel risks, legal risks, political risks, etc. This article is about the use of the term in project management. That probably wasn’t fair to expect, but golly it would have been nice. I have read the Polish edition: To be less pessimistic, I will give the author credit for being very thorough in explaining his argument.
Because, as consultant Dave Kleist observed in an e-mail note, “Death march projects are rarely billed as such, and it takes a lot of work when being hired from the outside to discover if your hiring company is prone to creating death march projects.
Typically, to improve the chances of success, it’s not crucial to care about tools or particular technology. It also reminded me of the major important points he covered that I had forgotten because of his verbose prose. Goodreads helps you keep track of books you want to read.
And another may find it in robbing banks. Why would anyone in his right mind agree to participate in such a project? But I remember it been mildly entertainig and mostly unpractical.
Jan 22, Troy Swinehart rated it it was amazing Shelves: Having been yourddon to other literature in the past, this book did not teach me a lot of new things. Books by Edward Yourdon. There are no discussion topics on this book yet. The author stated that a lot of software engineering projects end up in failure and that this won’t change much in the future.
No trivia or quizzes yet. Other fields have since recognized the same occurrence in their own spheres and have adopted the name.