4. People in Death March Projects.
6. Tools and Technology.
7. Death March as a Way of Life.
Uh-oh, it looks like your Internet Explorer is out of date.
For a better shopping experience, please upgrade now.
Pub. Date: 12/06/2003
Publisher: Prentice Hall
In the course of a career, practically every software developer and manager will encounter projects with outrageous staffing, scheduling, budgeting, or feature constraints: projects that seem destined to fail. In the wake of re-engineering, such "Death
The complete software developer's guide to surviving projects that are "doomed to fail."
In the course of a career, practically every software developer and manager will encounter projects with outrageous staffing, scheduling, budgeting, or feature constraints: projects that seem destined to fail. In the wake of re-engineering, such "Death March" projects have become a way of life in many organizations.
Yourdon walks step-by-step through the entire project life cycle, showing both managers and developers how to deal with the politics of "Death March" projects--and how to make the most of the available resources, including people, tools, processes, and technology.
Learn how to negotiate for the flexibility you need, how to set priorities that make sense--and when to simply walk away. Discover how to recognize the tell-tale signs of a "Death March" project--or an organization that breeds them.
If you've ever been asked to do the impossible, Death March is the book you've been waiting for.
See all customer reviews
The story of my life
This book is going to be as influential as 'The Mythical Man-Month'. Yourdon tackles some issues that need to be addressed in the modern software development industry. He does offer some insightful analysis as to why things get as bad as they do, and his strategies and recommendations are useful. However, this book is typical of 'guru' books in that there's enough useful information in it for few brilliant articles, but not enough to fill a whole book. The book is 230 pages long but a good quarter of it is verbatim copy of E-mails Mr. Yourdon received from other contributors. It is right and appropriate for him to cite his sources, but there has to be a better way of doing it. There's also a fair bit of filler material: white space, bulleted lists, diagrams, and unnecessary repetition. The writing is cumbersome, such that if there's a choice between a simple word and a complex word ('use' and 'utilize', for example) Yourdon picks the bigger word every time as if he's getting paid by the letter. The personal anecdotes and stories are interesting, but I buy technical books for useful content, not to 'chew the fat' with the author.