Suche books:   





Death March (2nd Edition) (Yourdon Press Series)
Edward Yourdon

Prentice Hall PTR, 2003 - 256 pages

average customer review:based on 70 reviews
view larger image
 for more information click here

   highly recommended  highly recommended





A critical view from a software engineering advocate

Definitely a must-read for anyone involved with project or technical management.

Yourdon exposes a series of reasons that move organizations into death marches, and also the reason why many employees still embark on those projects.

He also tries to propose some solutions, although many times you will be facing a no-win scenario.

An short book and an eye opener for those who don't have time to read (beacause they are already involved in a death march)

[...]


Death

Mediocre. Uninspired writing, much like his other books. I keep hoping for better but he never delivers. About 200 pages, padded by notes for each chapter that repeat things in the main text.

Occasional interesting points, but not enough to make it a keeper. Borrow it if you can for a quick read.



 for more information click here









 for more information click here


Average

It is mostly a synopsis of ideas from several better books (e.g. Peopleware). I'd suggest reading them instead. Of course, the bibliography from this book is very useful. It is a decent guide to what resources are available for dealing with Death March projects.






A decent read for anyone in IT

I was required to read this book for a Masters-level class in project maanagement. Overall, it provides good insight into the challenges facing IT projects and why they often fail. At times Yourdon shows a slight engineering know-it-all slant in his writing, but in the end Yourdon accurately portrays the fact that IT projects alone do not provide panacea for organizational, social, and business problems.


 for more information click here


Try to never need this book - but when you need it, buy it!

The very first page of this book defines what the author means by a "Death March"; any project whose project parameters exceeds the norm by more than fifty percent. In essence, this book is meant to help you in those unpleasant circumstances when you've got half the amount of time, half the amount of staff, or half the amount of money that you would rationally need to finish a project.

Unsurprisingly, Yourdon advises anyone reading the book to avoid these projects as much as possible, even counseling that it is sometimes better to resign early rather than sacrifice your health and professional reputation trying to do the impossible. But if you feel compelled to embark on a Death March, this book is an invaluable guide to the pain that lays ahead.

One of the reasons the book is so valuable is that it articulates many of the things we would like to think are common sense. These are items that, when you read them for the first time, make you think "of course that's true". But if you ask yourself whether or not you would have instinctively and firmly followed the advice, the answer is often no. I found the chapters on politics and negotiation (2 & 3 respectively) to be particularly helpful in this way. OF COURSE I should negotiate the scope and the specific team members needed at the start of a death march project, but reading Yourdon's words I came to the realization that my first reaction is instinctively "we'll make it happen" rather than the sometimes appropriate "we've only got a chance if I can have..." It's important to get gut checks like this before you find yourself in the middle of a tense situation so that you can anticipate your own feelings and counter them when necessary.

Another very interesting concept is the Triage system described in chapter 5. This is based on the idea that, no matter what else happens in a death march, the team will not be able to deliver 100% of the features that are initially asked for. I actually see a very strong argument here for using some of the newer Agile project management methods, where the items that deliver the most value are implemented first and evaluated by the end users. Combining such a system with a triage effort on behalf of the project manager and management could, on occasion, allow a death march project to produce nearly 100% of the value required without completing 100% of the features.

There is much else in here that is useful, especially on the subjects of why people participate in these sorts of projects and what they expect to get out of them. If it's impossible for you to avoid a Death March, make sure you've read this book before you plunge in.



 for more information click here


reviews: page 1, 2, 3, 4, 5, 6, 7, 8, 9, 10



Death march projects are becoming increasingly common in the software industry. The symptoms are obvious: The project schedule, budget, and staff are about half of what is necessary for completion. The planned feature set is unrealistic. People are working 14 hours a day, six or seven days a week, and stress is taking its toll. The project has a high risk of failure, yet management is either blind to the situation or has no alternative. Why do these irrational projects happen, and what, other than pure idiocy, leads people to get involved in them?

Edward Yourdon has produced a wise and highly readable book on the entire death march phenomenon and the best way to steer through one. He takes a close look at the types of projects that often become death marches and the corporate politics and culture that typically produce them; Yourdon helps you examine your own motivations and those of corporate managers who enable death marches to take shape.

Much of Death March is about the human element of highly stressful projects. The author's plain-spoken observations on the dysfunctional organization--the Machiavellian politics, naive optimism, lust for power, fear, and sheer managerial stupidity that guide so many death marches--make for a refreshing change from other project management books. You'll also find much practical advice to help you survive, everything from negotiating with upper management to breathing life into faltering projects. He'll even help you determine if you should look for another job.

If you've ever worked in a death march situation or been a client of a company addicted to death march management, this book will help you understand what happened. More importantly, it will help you prepare for future encounters with death marches. Death March is highly recommended for anyone involved in software development.


 for more information click here



hot or not?    What's your opinion?     Write a review and share your thoughts!



recommendations

The thinking persons list of books to change your life
Joel's Software Management Training - Part 1
My software development books
Software Project Management
Java Books I read in 2007




edition

HOLY BIBLE/ SCHOOL AND CHURCH EDITION- Regular Print
MLA Handbook for Writers of Research Papers, Sixth Edition
Psychology, Eighth Edition, in Modules
Society: The Basics (10th Edition)
The Tales of Beedle the Bard, Collector's Edition (Offered ...



series

Harry Potter and the Goblet of Fire (Book 4)
The Kingdoms and the Elves of the Reaches (Keeper Martin's Tales ...
Three Cups of Tea: One Man's Mission to Promote Peace . . . One ...
Seabiscuit: An American Legend (G K Hall Large Print Nonfiction ...
Harry Potter and the Sorcerer's Stone (Book 1)



press

Count of Monte Cristo
Rocket Boys (The Coalwood Series #1)
Phantom
Ella Enchanted
Harry Potter and the Sorcerer's Stone (Book 1)



search for books
death march, 2nd, death, edition, march, press, series, yourdon


Impressum / about us


Suche books: