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 Thoroughly revised and updated, this practical handbook on software project success and survival explains how to confront five important issues involved in all .

Author: Nejas Tugal
Country: Netherlands
Language: English (Spanish)
Genre: Art
Published (Last): 8 April 2010
Pages: 72
PDF File Size: 13.88 Mb
ePub File Size: 18.12 Mb
ISBN: 202-9-87726-239-6
Downloads: 9451
Price: Free* [*Free Regsitration Required]
Uploader: Tokree

PaperbackSecond Editionpages. Nov 24, Jeff Keehr rated it liked it. Dec 06, Hrishikesh Choudhari rated it it was amazing.

The book is so so. It was interesting to read and skim through the e-mails Mr. It spoke to me at the time. Trivia About Death March.

Death March by Edward Yourdon

I have decided that I don’t care for Yourdon’s view of things: Of course, there are much more topics that are important. There is too much cultural difference. Tedious and repetitive, no useful info. I think it was because I was put off by some of the author’s statements that felt like accusations. To ask other readers questions about Death Marchplease sign up. Yourdon, but if I didn’t think there was something to gained from his “old fart” experience, I wouldn’t be reading this book!


Thanks for telling us about the problem. From Wikipedia, the free encyclopedia.

Don’t get me wrong, I’m sure Mr. My library Help Advanced Book Search. How to recognize when your project has gone wrong.

Dec 30, Mark Ruzomberka rated it did mardh like it. Quite simply, a death march project is one whose “project parameters” exceed the norm by at least 50 percent.

Death march (project management) – Wikipedia

This article relies largely or entirely on a single source. Writing a review for each chapter makes this book more burdensome than it yourdln is. So I borrowed it from the Thomson Library.

A handy survival guide for corporate programmers. His favorite catchphrase, “battle-scarred veteran,” has already become annoying, and I’m hardly on page Jan 22, Troy Swinehart rated it it was amazing Shelves: That probably wasn’t fair to expect, but golly it would have been nice. From the thought-leader of technical productivity, still applicable today.

Thus, the project team may have been told that it needs to squeeze twice as many features into a fixed amount of RAM or disk space as its competitor; or it may have been told its system has to handle twice the volume of transactions that exward comparable system has ever accomplished. This article is about the use of the term in project management.


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

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.

Oct 17, Alex Ott rated it it was amazing Shelves: I feel that in this chapter, Mr. 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.

The term “death march” in this context was discussed at length in Edward Yourdon ‘s book Death March:

Related Posts