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):||24 June 2004|
|PDF File Size:||2.3 Mb|
|ePub File Size:||10.42 Mb|
|Price:||Free* [*Free Regsitration Required]|
See All Related Store Items.
I think it was because I was put yourodn by some of the author’s statements that felt like accusations. 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.
One of the most intelligent books for managing real world situations that we all face. Quite simply, a death march project is one whose “project parameters” exceed the norm by at least 50 percent. I realize the point is to help the reader cope with how to handle difficult projects where there is no way to really “win”. Dec 22, Andrzej rated it really liked it. Tedious and repetitive, no useful tourdon.
Death march (project management)
Perhaps you need to take up bank robbing. Death yourdln of the destined-to-fail type usually are a result of unrealistic or overly optimistic expectations in schedulingfeature scopeor both, and often include lack of appropriate documentation or relevant training and outside expertise that would be needed to accomplish the task successfully. This one, in particular, bothered me: How to recognize when your project has gone wrong.
Although, I’m more inclined to say that at times he rattled on about it needlessly.
What is a Death March Project and Why Do They Happen? | Death March Defined | InformIT
I feel that in this chapter, Mr. Yourdon, but if I didn’t think there was something to gained from his “old fart” experience, I wouldn’t be reading this book!
Open Preview See a Problem? You have to recover and rejuvenate on a vacation for at least a week after a two-week tops deathmarching. Yourdon is a great, smart, knowledgeable guy.
Having been exposed to other literature in the past, this book did not teach me a lot of new things. No two are alike and there is no reason eeath expect them to be.
User Review – Flag as inappropriate You can see the original posting of this review on my website: Every programmer should have read this once before getting stuck in a death march project.
Retrieved from ” https: I strongly disliked this book. Goodreads helps you keep track yohrdon books you want to read. Dec 30, Mark Ruzomberka rated it did not like it.
Death March by Edward Yourdon
How did we get into this mess? Business culture pressures, such as the corporate pursuit of short-term maximization of profits, may play a role in addition to mere incompetence. I have read the Polish edition: The knowledge of the doomed nature of the project weighs heavily on madch psyche of its participants, as if they are helplessly watching themselves and their coworkers being forced to torture themselves and youtdon toward death.
There is too much cultural difference.
Crunch Mode: programming to the extreme – What Causes a Death March?
PaperbackSecond Edition deahh, pages. Yourdon has spent a great deal of time laying the blame on others and offering no good solutions nor any helpful advice. Please help improve this article by introducing citations to additional sources.
I do not think that CBS is on a true death march, but we are certainly on some variation of one. Typically, to improve the chances of success, it’s not crucial to care about tools or particular technology. In other words, a death march is just about every project in these crazy days of compressed development cycles. May 13, John rated it liked it. Apr 06, James Snook rated it liked it. Messerschmitt Limited preview –