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):||20 January 2004|
|PDF File Size:||2.88 Mb|
|ePub File Size:||5.96 Mb|
|Price:||Free* [*Free Regsitration Required]|
But for anyone involved with project or technical management, it is a must-read. Thanks for telling us about the problem. Writing a review for each chapter makes this book more burdensome than it already is.
No trivia or quizzes yet. The functionality, features, performance requirements, or other technical aspects deward the project are twice what they would be under normal circumstances. 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. The general feel 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.
Death March by Edward Yourdon
But doubling the functionality—i. Yoyrdon Edward Yourdon Feb 6, Books by Edward Yourdon. This is about how to survive a software development project when management has not allocated sufficient resources e.
A good book on software management culture and how it looks on the big picture when corp, business and sponsors are involved. Goodreads helps you keep track of books you want to read.
This isn’t a book about perfectly organized projects in “textbook” companies. Want to Read saving…. I read this one specifically because of a yourcon I was on at the time.
If you are reading this review or book I hope you find consolation in it and wish you the best in your situation. Chapters deal, in turn, with the issues of politics, negotiating games, peopleware issues, tools and process management.
Oct 01, Bernie May rated it it was amazing Shelves: Refresh and try again. Perhaps you need to take up bank robbing. But, it didn’t have the magic bullet I was looking for. Thoroughly revised and updated, this practical handbook on software project success and survival explains how to confront five important issues involved in all software projects–people, politics, process, project management, and tools–and furnishes new sections on estimation, edwsrd, time management, agile concepts, updated references, and real-world examples.
Of course, even a project without the schedule, staff, budget, or functionality constraints described above could have a high risk of failure—e. One man may find happiness in supporting a wife and children. Quite simply, a death march project is one whose “project parameters” exceed the norm by at least 50 percent. Jan 09, Weavx4 rated it really liked it. Selected pages Title Page. What is more important is limiting the scope of the product, negotiating requirements a lot of them 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.
There is too much cultural difference. Prentice Hall Professional- Computers – pages. Every programmer should have read this once before getting stuck in a death march project. Lists with This Book. Yourdon, but if I didn’t think there was something to gained from his “old fart” experience, I wouldn’t be reading this book! I found multiple spelling errors, even though this is the second edition.
At an alarming rate, companies continue to create death-march projects, repeatedly!
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.
Please help improve this article by introducing citations to additional sources. 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 yourrdon 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)
No matter what your role–developer, project leader, line-of-business manager, or CxO–you’ll find realistic, usable solutions. The budget and associated resources have been cut in half. Death March Edward Yourdon Snippet view – To many grizzled IT veterans, these are rhetorical questions.