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):||2 February 2004|
|PDF File Size:||7.35 Mb|
|ePub File Size:||4.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
That probably wasn’t fair to expect, but golly it would have been nice. I think it was because I was put off by some of the author’s statements that felt like accusations. No trivia or quizzes yet. Although, I’m more inclined to say that at times he rattled on about it needlessly.
Death March – Edward Yourdon – Google Books
Refresh and try again. Articles needing additional references from August All articles deatth additional references Articles lacking in-text citations from August All articles lacking in-text citations All articles with style issues Edwaed articles with style issues from February All articles with unsourced statements Articles with unsourced statements from May Apr 01, Frank Thun rated it it was ok. There are much better ways to spend your time learning than to suffer through this book unnecessarily.
Ironically, it was the most fun project of my career. Naturally, the tension and pressure escalate in such environments, so that the death march team operates as if it is on a steady diet of Jolt cola. A good overview of many concepts of what would soon become “Agile”. How common are death marches? It’s good to know why projects fail and how to lower the risk of failure. Can’t rate it as I read this book very long time ago.
The schedule has been compressed to less than half the amount estimated by a rational estimating process; thus, the project that would normally be expected to take 12 calendar months is now yojrdon to deliver its results in six months or less. But most commonly, the reason for the high risk assessment is a combination of the constraints described above.
By Edward Yourdon Feb 6, Everythingin their experience, is a death march project. 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. Preview — Death March by Deayh Yourdon. Rod Biggar at CSI reminded me of this book.
Yourdon has spent a great deal of time laying the blame on others and offering no good solutions nor any helpful advice.
You have to recover and rejuvenate evward a vacation for at least a week after a two-week tops deathmarching. 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 shelved. But, it didn’t have the magic bullet I was looking for. It was interesting to read and skim through the e-mails Mr.
Dec 03, KevinS rated it really liked it. Lots of good suggestions and analysis that is still valid. Death March Edward Yourdon Snippet view – Read, highlight, and take notes, across web, tablet, and phone.
And how to maybe turn it around. Or geeking in a sideshow. Because corporations are insane and, as consultant Richard Sargent commented to me, “Corporate insanity is doing the dearh thing again and again, and each time expecting different results. One man may find happiness in supporting a wife and children.
Death March, Second Edition
,arch Despite the subtitle, there are no simple, clear cut solutions in this book. 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 is about the use of the term in project management.
Messerschmitt Limited preview – Yourdon thinks marxh of himself and other like him. Return to Book Page. Jan 22, Troy Swinehart rated it it was amazing Shelves: No matter what your role–developer, project leader, line-of-business manager, or CxO–you’ll find realistic, usable solutions.
I strongly deaht this book. Edwaed comes to the sobering conclusion that there are no silver bullets. At an alarming rate, companies continue to create death-march projects, repeatedly! It’s about your project, in your company. This one, in particular, bothered me: But doubling the functionality—i. 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.
Death marches of the destined-to-fail type usually are a result of unrealistic or overly optimistic expectations in schedulingfeature scopeor both, and often include lack of appropriate documentation or relevant training and outside expertise that would be needed to accomplish the task successfully.
August Learn how and when to remove this template message. To ask other readers questions about Death Marchplease sign up. Open Preview See a Problem? Every programmer should have read this wdward before getting stuck in a death march project. There are no discussion topics on this book yet.