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: Gorg Fenririsar
Country: Brazil
Language: English (Spanish)
Genre: Personal Growth
Published (Last): 28 April 2009
Pages: 245
PDF File Size: 18.64 Mb
ePub File Size: 19.68 Mb
ISBN: 398-9-91445-655-3
Downloads: 22489
Price: Free* [*Free Regsitration Required]
Uploader: Manris

I was expecting a lot more; this is a well-reputed classic, but it didn’t really cover much that isn’t elsewhere in the literature.

Death march (project management)

Lists with This Book. Despite the subtitle, there are no simple, clear cut solutions in this book. Books by Edward Yourdon. I’m sometimes think they are obvious, since most people never ask me what I mean by “death march. I strongly disliked this book. Often even financial bonuses to employees will not help with the exception of avoiding takeovers from competition.

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.

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

A death march project is one for which an unbiased, objective risk assessment drath includes an assessment of technical risks, personnel risks, legal risks, political risks, etc. Aug 08, Anton Kan rated it youtdon it. Account Options Sign in. Prentice Hall Professional Amazon. Writing a review for each chapter makes this book more burdensome than it already is. It spoke to me at the time. Death March Edward Yourdon Snippet view – By using this site, you agree to the Terms of Use and Privacy Policy.


It also reminded me of yourdn major important points he covered that I had forgotten because of his verbose prose. Trivia About Death March. There are no discussion topics on this book yet. This article is about the use of the term in project management.

Software project management Dysphemisms. But, it didn’t have the magic bullet I was looking for.

Some projects are just like this, in big corporations. Retrieved from ” https: Which makes it a classic. Yourdon used in his research. Although, I’m more inclined to say that at times he rattled on about it needlessly.

I’ve just lost interest in his book. Oct 16, Petr added it. The performance constraints may or may not lead to a death march project; after all, we can always yourdob advantage of cheaper, faster hardware, and we can always search for a more clever algorithm or design approach to accomplish the improved performance.

Yes, I am young and naive and optimistic and not-as-experienced as Mr.

The staff has been reduced to less than half the number that would normally be assigned to a project of this size and scope; thus, instead of being given a project team of 10 people, the project manager has been told that only five people are available.

That probably wasn’t fair to expect, but golly it would have been nice. Dec 03, KevinS rated it really liked it. Although software development is populated with intelligent programmers and managers, death marches occur “because the competitive business pressure demands it and the new technical opportunities invite it,” he says.

Jan 09, Weavx4 rated it really liked msrch. What makes IT organizations create such things? 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 yohrdon s I strongly disliked this book.


If you think the answers to these questions are obvious, feel free to jump to the next chapter. I do not think that CBS is on a true death march, but we are certainly on some variation of one. This chapter is from the book. Thanks for telling us about the problem.

Death March – Edward Yourdon – Google Books

Chapters deal, in turn, with the issues of politics, negotiating games, peopleware issues, tools and process management. And the really disturbing conclusion: By Edward Yourdon Feb 6, 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.

Otherwise you’re just wasting your project’s LoE. It’s obvious that Mr.

Return to Book Page. Why do they happen? Please help to improve this article by introducing more precise citations.

Yourdon has spent a great deal of time laying the blame on others and offering no good solutions nor any helpful advice. Articles needing additional references from August All articles needing additional references Articles lacking in-text citations from August All articles lacking in-text citations All articles with style issues Wikipedia articles with style issues from February All articles with unsourced statements Articles with unsourced statements from May A handy survival edwardd for corporate programmers.

It was interesting to read and skim through the e-mails Mr. So I borrowed it from the Thomson Library.