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 .
|Published (Last):||12 June 2013|
|PDF File Size:||13.30 Mb|
|ePub File Size:||6.42 Mb|
|Price:||Free* [*Free Regsitration Required]|
Retrieved from ” https: Your education as an software professional is incomplete if you yoyrdon this book. I do not think that CBS is on a true death march, but we are certainly on some variation of one. Chapters deal, in turn, with the issues of politics, negotiating games, peopleware issues, tools and process management. This article is about the use of the term in project management.
Oct 01, Bernie May rated it it was amazing Shelves: Business mardh pressures, such as the corporate pursuit of short-term maximization of profits, may play a role in addition to mere incompetence. 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.
By Edward Yourdon Feb 6, I feel that in this chapter, Mr. This is about how to survive a software development project when management has not allocated sufficient resources e. Apr 06, James Snook rated it liked it. Oct 17, Alex Ott rated it it was amazing Shelves: Because of the competitive pressures edawrd business competition in today’s global marketplace, along with the concept of “Internet time” from the dot-com era of the computer industry, this is probably the most common form of death dath project.
Goodreads helps you keep deah of books you want to read. Otherwise you’re just wasting your project’s LoE.
That probably wasn’t fair to expect, but golly it would have been nice. It confirmed much of what I knew was wrong with the project. Happiness lies in being privileged edwsrd work hard for long hours in doing whatever you think is worth doing. Death March Edward Yourdon Snippet view – Not really focused on developers, it stands on the POV of the project manager most of the time, having little practical knowledge to be gathered by developers.
Death March by Edward Yourdon
Ever been on a big computer project? If you think the answers to these questions are obvious, feel free to jump to the next chapter.
Yourdon has spent a great deal of time laying the blame on others and offering no good solutions nor any helpful advice. Some projects are just like this, in big corporations. Lots of good suggestions and analysis that is still valid.
The issues are simply too complex. Ed comes to the sobering conclusion that there are no silver bullets. It’s good to know why projects fail and how to lower the risk of failure.
Dec 06, Hrishikesh Choudhari rated it it was amazing. But most commonly, the reason for the high risk assessment is a combination of the constraints described above. Well, maybe I’ll go back and try to finish it one day. We went down, but we went down together and in good spirits. I’ve given up on trying to review each chapter individually.
Death March by Edward Yourdon
Writing a review for each chapter makes this book more burdensome than it already is. 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. See All Related Store Items. Feb 28, Todd rated it liked it. Patent under-resourcing is especially offensive at a large corporation with sufficient financing.
The functionality, features, performance requirements, or other technical aspects of the project are twice what they would be under normal circumstances. Nov 24, Jeff Keehr rated it liked it.