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):||5 May 2005|
|PDF File Size:||6.63 Mb|
|ePub File Size:||2.81 Mb|
|Price:||Free* [*Free Regsitration Required]|
Start Free Trial No credit card required. Note the individual and subjective nature of each case.
Death March, Second Edition
Nov 24, Jeff Keehr rated it liked it. Yourdoj read on death march projects. I recommend it to all project manager just to read and recognize yourself: Want to Read Currently Reading Read. Trivia About Death March. Still another may labor mightily for years in pursuing pure research with no discernible results. Edwzrd 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.
I have decided that I don’t care for Yourdon’s view of things: No matter what your role–developer, project leader, line-of-business manager, or CxO–you’ll find realistic, usable solutions. Refresh and try again.
Death march (project management) – Wikipedia
If you’re the naively optimistic software engineer responsible for making the death march estimate, chances are that you don’t even know what you’re doing. Every time I mention the book to friends and colleagues, they just laugh and say, ‘Oh, yeah, you must be talking about my project. It spoke to me at the time. But you won’t just recognize your reality: An internationally recognized consultant, he is author or coauthor of more than 25 books, including Byte WarsManaging High-Intensity Internet Projectsand Decline and Fall of the American Programmer.
Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. Of course, even a project without the schedule, edwadd, budget, or functionality constraints described above could have a high risk of failure—e.
The issues are simply too complex.
It confirmed much of what I knew was wrong with the project. It’s good to know why projects fail and how to lower the risk of failure. Yourdon used in his research. Fully updated yoirdon expanded, with powerful new techniques!
No two are alike and there is no reason to expect them to be. There is too much cultural difference.
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. Which makes it a classic. As Ed Yourdon says in the preface to Death March “The wonderful thing about the title is that I don’t even have to explain it. Other fields yojrdon since recognized the same occurrence in their own spheres and have adopted the name.
From Wikipedia, the free encyclopedia. Although, I’m more inclined to say that at times he rattled on about it needlessly. From the thought-leader of technical productivity, still applicable today. An unfortunate survival guide to some projects, over and over again.
If you are reading this review or book I hope you find consolation in it and wish you the best in your situation. Edwarr Limited preview –