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):||9 December 2005|
|PDF File Size:||17.73 Mb|
|ePub File Size:||20.49 Mb|
|Price:||Free* [*Free Regsitration Required]|
This edition’s new and updated coverage includes: This chapter is from the book. But most commonly, the reason for the high risk assessment is a combination of the constraints described above. In this book Yourdon discusses through anecdotes, musings, and conversations with his industry peers aspects of a death march that help the readers make sense of the challenges they too know about.
May 26, Alex Railean rated it liked it Shelves: I read this one specifically because of a project I was on at the time. Selected pages Title Page. An unfortunate survival guide to some projects, over and over again. I read this the year I lived a death march project. Ever been on a big computer project? Yourdon used dewth his research.
Software development and software engineering are the fields in which practitioners first desth the term to these project management practices. How common are death marches? Thus, if the normal work-week is 40 hours, then a death march project team is often found working hour days, six days a week.
Want to Read Currently Reading Read. Dec 03, KevinS rated it really liked it. Return to Book Page.
Want to Read saving…. Despite the subtitle, there are no simple, clear cut solutions in this book. In project managementa death march is a project yourdpn the participants feel is destined to fail, or that requires a stretch of unsustainable overwork. The general yoyrdon of the project reflects that of an actual death march because project members are forced to continue the project by their superiors against their better judgment. It also reminded me of the major important points he covered that I had forgotten because of his verbose prose.
Crunch Mode: programming to the extreme – What Causes a Death March?
This article relies largely or entirely on a single source. You can see the original posting of this review on my website: Feb 28, Todd rated it liked it. It’s good to know why projects fail and how to lower the risk of failure. Often, the discomfort is heightened by the knowledge that “it didn’t have to be this way”; [ tone ] that is, that if the company wanted to achieve the goal of the project, it could have done so in a successful way had it been managed competently such as by devoting the obviously required resourcesincluding bringing all relevant expertise, technology, or applied science to the task rather than just whatever incomplete knowledge a few employees happened to possess.
Death march (project management)
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.
Politics, politics, politics Deqth promises made by marketing, senior executives, naive project managers, and so on Naive optimism of youth: Relevant discussion may be found on the talk page. By Edward Yourdon Feb 6, This work covers the project lifecycle, addressing every key issue participants face: Lists with This Book.
For the war crime, see death march. Like Peoleware, it’s often oriented at the human side of things. My library Help Advanced Book Search. What makes IT organizations create such things? Quite simply, a death march project is one whose “project parameters” exceed the norm by at least 50 percent.
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. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more. 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.
Prentice Hall Professional Amazon. Views Read Edit View history. Apr 06, James Snook rated it liked it. But doubling the functionality—i.
Books by Edward Yourdon. Why would anyone in his right mind agree to participate in such a project? This is about how to survive a software development project when management has not allocated sufficient resources e. Of course, there are much more topics that are important.
Mwrch think it was because I was put off by some of the author’s statements that felt like accusations. 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 eddard. Goodreads helps you keep track of books you want to read. One of the most intelligent books for managing real world situations marcy we all face. The author stated that a lot of software engineering projects end up in failure and that this won’t change much in the future.