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):||18 October 2013|
|PDF File Size:||10.12 Mb|
|ePub File Size:||19.64 Mb|
|Price:||Free* [*Free Regsitration Required]|
Death March by Edward Yourdon
Edwarf favorite catchphrase, “battle-scarred veteran,” has already become annoying, and I’m hardly on page Otherwise you’re just wasting your project’s LoE. Note the individual and subjective nature of each case.
The performance constraints may or may not lead to a death march project; after all, we can always take advantage of cheaper, faster hardware, and we can always search for a more clever algorithm or design approach to accomplish the improved performance. Like Peoleware, it’s often oriented at the human side of things.
To ask other readers questions about Death Marchplease sign up. I recommend it to all project manager just to marchh and recognize yourself: May 26, Alex Railean rated it liked it Shelves: A handy survival guide for corporate programmers. An unfortunate survival guide to some projects, over deaht over again. Unless you are truly marchh in a “Death March” project with no way out and just need something to help you cope, I would move on from this book, or at least read the other two I mentioned first.
Feb 28, Todd rated it liked it.
What Causes a Death March?
In other words, a death march is just about every project in these crazy days of compressed development cycles. Ever been on a big computer project? The author stated that a lot of software engineering projects end up in failure and that this won’t change much in the future.
This article includes a list of referencesbut its sources remain unclear because it has insufficient inline citations. Account Options Sign in. Jan 09, Weavx4 rated it really liked it.
Because of the competitive pressures of 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 march project. 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 edwqrd.
Dec 30, Mark Ruzomberka rated it did not like it. To many grizzled IT veterans, these are rhetorical questions. What is a death march project?
Lists with This Book. Oct 16, Petr added it. Writing a review for each chapter makes this book more burdensome than it already is. Trivia About Death March. Jan 22, Troy Swinehart rated it it was amazing Shelves: Oct 23, JefferyG rated it it was amazing. What is more The author stated that a lot of software engineering projects end up in failure and that this won’t change much in the future.
How did we get into this mess? But doubling the functionality—i. Refresh and try yourdno. No two are alike and there is no reason to expect them to be.
Software development and software engineering are the fields in which practitioners first applied the term to these project management practices. Despite the subtitle, there are no simple, clear cut solutions in this book. Apr 06, James Snook rated it liked it. I’ve just lost interest in his book. Yourdon is a great, smart, knowledgeable guy. It’s good to know why projects fail and how to lower the risk of failure. The book doesn’t give too revolutionary advice of how to lead such projects to a success and they hardly exist but at least helps to understand that you’re not alone and gives some ways to identify such projects on an early stage.
And it’s not a bad idea for the marketing and sales people who sometime spawn the death marches to give it a look, too.