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

Author: Arashigrel Durisar
Country: Somalia
Language: English (Spanish)
Genre: Travel
Published (Last): 18 April 2013
Pages: 73
PDF File Size: 13.38 Mb
ePub File Size: 15.88 Mb
ISBN: 247-5-44243-250-3
Downloads: 49425
Price: Free* [*Free Regsitration Required]
Uploader: Moogugor

User Review – Flag as inappropriate You can see the original posting of this review on my website: I realize the point is to help the reader cope with how to handle difficult projects where there is no way to really “win”.

The knowledge of the doomed nature of the project weighs heavily on the psyche of its participants, as if they are helplessly watching themselves and their coworkers being forced to torture themselves and march toward death. And the really disturbing conclusion: I feel that in this chapter, Mr.

Read, highlight, and take notes, across web, tablet, and phone. 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 disliked this book. But I remember it been mildly entertainig and mostly unpractical.

Feb 28, Todd rated it liked it. Sadly it reads like Dilbert Often even financial bonuses to deafh will not help with the exception of avoiding takeovers from competition. An internationally recognized consultant, he is author or coauthor of more than 25 books, including Byte WarsManaging High-Intensity Internet Projectsand Decline and Fall youron the American Programmer.

Death March Edward Yourdon Snippet view – If you think the answers to these questions are obvious, feel free to jump to the next chapter.

Death March is a short and disturbing book–usefully short, because if you really need to read the book, you probably don’t have time to read it. So I borrowed it from the Thomson Library. It confirmed much of what I knew was wrong with the project.


Jul 05, Oleksandr rated it really liked it. The issues are simply too complex.

And it can lead to a pervasive atmosphere of penny-pinching that makes it impossible for the project manager to order pizza for the project team when they spend the entire weekend in the office working overtime.

Ed Yourdon explains how you might find yourself in such a mire. Again, this is often the result of downsizing and other cost-cutting measures, but it can also result from competitive bidding on a fixed-price contract, where the project manager in a consulting firm is informed by the marketing department that, “the good news is that we won the contract; the bad news is that we had to cut your budget in half in order to beat out the competitors.

To many grizzled IT veterans, these are rhetorical questions. Writing a review for each chapter makes this book more burdensome than it already is.

What is a Death March Project and Why Do They Happen?

Why would anyone in his right mind agree to participate in such a project? Despite the subtitle, there are no simple, clear cut solutions in this book.

It’s good to know why projects fail and how to lower the risk of failure. Do whatever you need to do to get drath copy!

Death march (project management) – Wikipedia

Typically, to improve the chances of success, it’s not crucial to care about tools or particular technology. Want to Read saving…. Relevant discussion may be found on the talk page.

From Wikipedia, the free encyclopedia. Want to Read Currently Reading Read. One of the most intelligent books for managing real world situations that we dsath face.

Because corporations are insane and, as consultant Richard Sargent commented to me, “Corporate insanity is doing the same thing again and again, and each time expecting different results. If you like books and love to build cool products, we may be looking for you.


In most projects, this means one or more of the following constraints have been imposed upon the project:. I have yourodn that I don’t care for Yourdon’s view of things: Aug 08, Anton Kan rated it yougdon it. How did we get into this mess? This review is probably going to seath a lot like the one for the previous book – “Practical guide to defect prevention”, so please have a look at that one.

Death March by Edward Yourdon. Thus, if the normal work-week is 40 hours, then a death march project team is often found working hour days, six days a week. The budget and associated resources have been cut in half. Often, the death march will involve desperate attempts maech right the course of the project by asking team members to work especially grueling hours hour days, 7-day weeks, etc.

Crunch Mode: programming to the extreme – What Causes a Death March?

I knew going in, as the title suggested, it would be a dewth topic, but geez, the reader is in for a slew of negative deat and thoughts on how to solve difficult projects. I read this the year I lived a death march project. How common are death marches?

Tedious and repetitive, no useful info. 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?

This may have come about as a jarch of someone’s naive belief that a new programming language or application development environment will magically double the team’s productivity—despite the fact that the team was given no training or practice with the new technology and probably wasn’t even consulted about the decision to use the technology in the first place.