Death March: The Complete Software Developer’s Guide to Surviving Mission Yourdon walks step-by-step through the entire project life cycle, showing both. Death March: The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects. Author: Edward Edward Yourdon. Death March by Edward Yourdon. Notes taken by Matthias Günther | 2 minutes read. p Marine Corps mentality => real programmers don’t need sleep; p
|Published (Last):||26 October 2013|
|PDF File Size:||11.37 Mb|
|ePub File Size:||19.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
My library Help Advanced Book Search. Often, the death march will involve desperate attempts to right the course of the project by marcj team members uourdon work especially grueling hours hour days, 7-day weeks, etc. Still another may labor mrch for years in pursuing pure research with no discernible results.
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. 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.
Aug 08, Anton Kan rated it liked it.
Dec 06, Hrishikesh Choudhari rated it it was amazing. Do whatever you need to do to get a copy! Having been exposed to other literature in the past, this book did not teach me a lot of new things.
I feel that in this chapter, Mr. Oct 16, Petr added it. Feb 28, Todd rated it liked it. How did we get into this mess? Yourdon, but if I didn’t think there was something to gained from his “old fart” experience, I wouldn’t be reading this book! Jan 22, Troy Swinehart rated it it was amazing Shelves: Because, as consultant Dave Kleist observed in an e-mail note, “Death march projects are rarely billed as such, and it takes a lot of work when being hired from the outside to discover if your hiring company is prone to creating death march projects.
From Wikipedia, the free encyclopedia.
What is a Death March Project and Why Do They Happen?
The term “death march” in this context was discussed at length in Edward Yourdon ‘s book Death March: It may not be Death March but it sometimes feels like the Lost Battalion. A death march project is one for which an unbiased, objective risk assessment which includes an assessment of technical risks, personnel risks, legal risks, political risks, dath. Oct 01, Bernie May rated it it yordon amazing Shelves: 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 required to deliver its results in six months or less.
Account Options Sign in. In most projects, this means one or more of the following constraints have been imposed upon the project:. Tedious and repetitive, no useful info. Related Resources Store Articles Blogs. The book doesn’t give too revolutionary advice of how to lead such projects to a success and they hardly exist but at least helps to understand that you’re not alone and gives some ways to identify such projects on an early stage.
Death March by Edward Yourdon
Views Read Edit View history. An internationally recognized consultant, he is author or coauthor of more than 25 books, including Byte WarsManaging High-Intensity Internet Projectsand Decline and Fall of the American Ylurdon. 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.
Yourdon used in his research. It spoke to me at the time.
I have decided that I don’t care for Yourdon’s view of things: Of course, there are much more topics that are important. Dec 30, Mark Ruzomberka rated it did not like it. Jul 05, Oleksandr rated it really liked it.
Death march (project management)
A handy survival guide for corporate programmers. Oct 23, JefferyG rated it it was amazing. Lists with This Book. An unfortunate survival guide to some projects, over and over again. Yes, I am young and naive and optimistic and not-as-experienced as Mr.
A good book on software management culture and how it looks on the big picture when corp, business and sponsors are involved. Describes the reasons why companies spawn Death Marches and provides you with guidance to identify and survive death march projects. No trivia or quizzes yet. Please help improve this article by introducing citations to additional sources. Chapters deal, in turn, with the issues of politics, negotiating games, peopleware issues, tools and process management.
Software project management Dysphemisms. This chapter is from the book. There is too much cultural difference.