DEATH MARCH YOURDON PDF

See the latest about a temporary release delay on new titles. Learn more. Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. One man may find happiness in supporting a wife and children. And another may find it in robbing banks.

Author:Makazahn Zuluzragore
Country:Chile
Language:English (Spanish)
Genre:Spiritual
Published (Last):4 October 2008
Pages:153
PDF File Size:12.80 Mb
ePub File Size:15.6 Mb
ISBN:450-8-45348-973-3
Downloads:59130
Price:Free* [*Free Regsitration Required]
Uploader:Yojin



Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book. Refresh and try again.

Open Preview See a Problem? Details if other :. Thanks for telling us about the problem. Return to Book Page. Preview — Death March by Edward Yourdon. Death March by Edward Yourdon. Describes the reasons why companies spawn Death Marches and provides you with guidance to identify and survive death march projects. This work covers the project lifecycle, addressing every key issue participants face: politics, people, process, project management, and tools.

Get A Copy. Paperback , Second Edition , pages. Published November 16th by Prentice Hall first published April 2nd More Details Original Title. Other Editions 7. Friend Reviews. To see what your friends thought of this book, please sign up. To ask other readers questions about Death March , please sign up. Lists with This Book. Community Reviews. Showing Average rating 3. Rating details. More filters. Sort order. Start your review of Death March. Feb 28, Todd rated it liked it. I read this one specifically because of a project I was on at the time.

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. It spoke to me at the time. It confirmed much of what I knew was wrong with the project.

But, it didn't have the magic bullet I was looking for. That probably wasn't fair to expect, but golly it would have been nice. The author stated that a lot of software engineering projects end up in failure and that this won't change much in the future. It's good to know why projects fail and how to lower the risk of failure.

However, it's good to know that there are no silver bullets. Typically, to improve the chances of success, it's not crucial to care about tools or particular technology. Often even financial bonuses to employees will not help with the exception of avoiding takeovers from competition. What is more The author stated that a lot of software engineering projects end up in failure and that this won't change much in the future.

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. Of course, there are much more topics that are important. May 26, Alex Railean rated it liked it Shelves: engineering , management , technology , computers , economics , business , programming , work , schedule , estimation.

This review is probably going to be a lot like the one for the previous book - "Practical guide to defect prevention", so please have a look at that one. Having been exposed to other literature in the past, this book did not teach me a lot of new things.

I found multiple spelling errors, even though this is the second edition. I read this the year I lived a death march project. Essentially, that's a project where you have too little resources in terms of time or personnel.

Ironically, it was the most fun project of my career. We went down, but we went down together and in good spirits. Oct 17, Alex Ott rated it it was amazing Shelves: sw-development. I was expecting a lot more; this is a well-reputed classic, but it didn't really cover much that isn't elsewhere in the literature.

Oct 16, Petr added it. Can't rate it as I read this book very long time ago. But I remember it been mildly entertainig and mostly unpractical. There is too much cultural difference. Tedious and repetitive, no useful info. Dec 03, KevinS rated it really liked it. 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.

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. Still, Yourdon modestly succeeds to persuade the reader to have a more mature view that if a culture of death marches can be refuted in many cases for the reader and if not then coping strategies the reader can adopt to co-exist with them.

If you are reading this review or book I hope you find consolation in it and wish you the best in your situation. Apr 24, Max Wolffe rated it it was ok. The Good: - This is the first book Ive read which acknowledges that projects fail. A star for that alone. The Bad: - I have never read a more cynical, depressing book about software engineering.

The tone of the book is fairly evident from the title and it was a slog to read as a result. Nov 14, Q. The result, a Death March. Suicide, divorce, and mental breakdowns were not unheard of. His prediction was that such a way of project management would continue into the 21st century. His tips on how to survive the industry are helpful, as they come out of his own experience as a consultant. I have been working in startup environments since and the last 5 years I engaged in several categories of death march projects without knowing this term.

This book is very acurate and what is most interesting it's dated around or so. Jun 14, Jeff Foster rated it it was amazing. I really enjoyed this book as it resonates strongly with the work I was doing at the time! Nov 10, Kate rated it liked it. Can't say i found this book useful. Very generic and all advice is based on simple common sense. Could be shortened by half. Dec 30, Mark Ruzomberka rated it did not like it.

I strongly disliked this book. I knew going in, as the title suggested, it would be a depressing topic, but geez, the reader is in for a slew of negative stories and thoughts on how to solve difficult projects. I realize the point is to help the reader cope with how to handle difficult projects where there is no way to really "win". 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 s I strongly disliked this book.

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. Unless you are truly trapped in a "Death March" project with no way out and just need something to help you cope, I would move on from this book, or at least read the other two I mentioned first.

There are much better ways to spend your time learning than to suffer through this book unnecessarily. Good book, but I've read the edition, and felt some of the issues were a bit outdated. Lots of good suggestions and analysis that is still valid. Nov 19, Rafael Bandeira rated it liked it.

A good book on software management culture and how it looks on the big picture when corp, business and sponsors are involved. A good overview of many concepts of what would soon become "Agile". Not really focused on developers, it stands on the POV of the project manager most of the time, having little practical knowledge to be gathered by developers.

BODHIDHARMA BLOODSTREAM SERMON PDF

Death march (project management)

Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book. Refresh and try again.

KOMATSU D355 PDF

Death March

Conference Paper Risk Management 13 May Here, you will learn the traits of a troubled project early enough to turn it around. We will identify the specific actions needed and how to implement them. You will learn what to do if you have to finish the project, but cannot turn it around.

Related Articles