Death March has ratings and 34 reviews. Todd said: I read this one specifically because of a project I was on at the time. And I left it out on my de. Thoroughly revised and updated, this practical handbook on software project success and survival explains how to confront five important issues involved in all . Why would anyone in his right mind agree to participate in such a project? Ed Yourdon explains how you might find yourself in such a mire.
|Published (Last):||3 December 2017|
|PDF File Size:||7.75 Mb|
|ePub File Size:||7.52 Mb|
|Price:||Free* [*Free Regsitration Required]|
Jul 05, Oleksandr rated it really feath it. Dec 30, Mark Ruzomberka rated it did not like it. A handy survival guide for corporate programmers. But deahh anyone involved with project or technical management, it is a must-read. The budget and associated resources have been cut in half. The term “death march” in this context was discussed at length in Edward Yourdon ‘s book Death March: Aug 10, Choesang Tenzin rated it really liked it.
Other fields have since recognized the same occurrence in their own spheres and have adopted the name.
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. Return to Book Page. You have to recover and rejuvenate on a vacation for at least a week after a two-week tops deathmarching.
Death march (project management)
Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. One of the greatest values of the book yourdoon that it can teach you how to recognize a death march, understand why it got that way, and then you can make an educated decision as to whether you want to be involved or not.
One man may find happiness in supporting a wife and children. And I left it out on my desk for a month or so afterwards so that my manager had to see it every time he stopped by to ask dumb questions.
Death March by Edward Yourdon
I have read the Polish edition: Tedious and repetitive, no useful info. It also reminded me of the major important points he covered that I had forgotten because of his verbose prose.
The issues are simply too complex. In this book Yourdon discusses through anecdotes, deaty, and conversations with his industry peers aspects of a death march that help the readers make sense of the challenges they too know about. Read, highlight, and take notes, across web, tablet, and phone. It spoke to me at the time.
This article includes a list of referencesbut its sources remain unclear because it has insufficient inline citations. I recommend it to all project manager just to read and recognize yourself: It’s good to know why projects fail and how to lower the risk of failure.
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. Oct 16, Petr added it. This edition’s new and updated coverage includes:. Sadly it reads like Dilbert May 26, Dfath Railean rated it liked it Shelves: An unfortunate survival guide to some projects, over and over again. 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 I think it was because I was put reath by some of the author’s statements that felt like accusations.
Dec 22, Andrzej rated it really liked it. Yourdon, but if I didn’t yourodn there was something to marcu from his “old fart” experience, I wouldn’t be reading this book! This may have come about as a result of someone’s naive belief that a new programming language or application development environment will magically double the team’s productivity—despite the fact that the team was given no training or practice with the new technology and probably wasn’t even consulted about the decision to use the technology in the first place.
Again, this is often the result of downsizing and other cost-cutting measures, but it can also result from competitive bidding on a fixed-price contract, where the project manager in a consulting firm is informed by the marketing department that, “the good news is that we won the contract; the bad news is that we had to cut your budget in half in order to beat out the competitors.
Politics, politics, politics Naive promises made by marketing, senior executives, naive project managers, and so on Naive optimism of youth: Every time I mention the book to friends and colleagues, they just laugh and say, ‘Oh, yeah, you must be talking about my project. PaperbackSecond Editionpages.
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 reath of transactions that any comparable system has ever accomplished. If you are reading this review or yoirdon I hope you find consolation in it and wish you the best in your situation.
Crunch Mode: programming to the extreme – What Causes a Death March?
Your education as an software professional is incomplete if you skip this book. For the war crime, see death march. What is more important is limiting the scope yourvon the product, negotiating requirements a lot of deagh 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.
Ok, I’ve given up trying to read the book entirely. Chapters deal, in turn, with the issues of politics, negotiating games, peopleware issues, tools and process management. Messerschmitt Limited preview – Feb 28, Todd rated it liked it. Retrieved from ” https: Still another may labor mightily for years in pursuing pure research with no discernible results. By Edward Yourdon Feb 6, Because Death March match written pre many of the tools and references seem outdated and do not address more recent software development methodologies like Agile.
This chapter is from the book. And it can lead to a pervasive atmosphere of penny-pinching that makes it impossible for the project manager to order pizza for the project team when they spend the entire ddeath in the office working overtime.