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: Fejinn Doujind
Country: El Salvador
Language: English (Spanish)
Genre: Literature
Published (Last): 24 October 2013
Pages: 439
PDF File Size: 14.71 Mb
ePub File Size: 14.4 Mb
ISBN: 231-3-50345-298-1
Downloads: 88500
Price: Free* [*Free Regsitration Required]
Uploader: Shaktirn

Views Read Edit View history.

How to recognize when your project has gone wrong. There are no discussion topics on this book yet. Business culture pressures, such as the corporate pursuit of short-term maximization of profits, may play a role in addition to mere incompetence. From Wikipedia, the free encyclopedia. Often even financial bonuses to employees will not help with the exception of avoiding takeovers from competition.

I feel that in this chapter, Mr. Apr 01, Frank Thun rated it it was ok. I found multiple spelling errors, even though this is the second edition.

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

Apr 06, James Snook rated it liked it. Related Resources Store Articles Blogs. What is more important is limiting the scope of the product, negotiating requirements a lot of them can be relaxed or even rejected and deadlines, caring about hiring right people, organizing frequent demos for customers and assuring daily and reliable project builds. Despite the subtitle, there are no simple, clear cut solutions in this book. An internationally recognized consultant, he is author or coauthor of more than 25 books, including Byte WarsManaging Yourddon Internet Projectsand Decline and Fall of eddard American Programmer.


I read this one specifically because of a project I was on at the time. I recommend it to yourddon project manager just to read and recognize yourself: To many grizzled IT veterans, these are rhetorical questions.

I knew going in, as the title suggested, it would be a depressing topic, but geez, the reader is in for a slew of negative stories and thoughts on how to solve difficult projects. It was interesting to read and skim through the e-mails Mr. Unfortunately, it’s happening far more often, as this edition of Death March is being written in the spring yoourdonbecause of the ongoing economic recession and the associated cutbacks in IT budgets.

No trivia or quizzes yet. In project managementa death march is a project that the participants feel is destined to fail, or that requires a stretch of unsustainable overwork. I just can’t get motivated from an author whose web site looks like this.

By using this site, you agree to the Terms of Use and Privacy Policy.

In most projects, this means one or more of the following constraints have been imposed upon youron project:. Ed Yourdon explains how you might find yourself in such a mire.


Death March – Edward Yourdon – Google Books

Having been exposed to other literature in the past, this book did not teach me a lot of new things. However, it’s good to know that there are no silver bullets. Contrariwise, if you are looking for shorter hours and longer vacations and early retirement, you are in the wrong mqrch. What is a death march project?

What Causes a Death March?

Please help to improve this article by introducing more precise citations. Thoroughly revised and updated, this practical handbook on software project success and survival explains how to confront five important issues involved in all software projects–people, politics, process, project management, and tools–and furnishes new sections on estimation, negotiation, time management, agile concepts, updated references, and real-world examples.

Why do they happen? And how to maybe turn it around. Because Death March was written pre many of the tools and references seem outdated and do not address more recent software development methodologies like Agile.