Book description
Death MarchSecond Edition
The #1 guide to surviving "doomed" projects...Fully updated and expanded, with powerful new techniques!
At an alarming rate, companies continue to create death-march projects, repeatedly! What's worse is the amount of rational, intelligent people who sign up for a death-march projectsaeprojects whose schedules, estimations, budgets, and resources are so constrained or skewed that participants can hardly survive, much less succeed. In Death March, Second Edition, Ed Yourdon sheds new light on the reasons why companies spawn Death Marches and provides you with guidance to identify and survive death march projects.
Yourdon covers the entire project lifecycle, systematically addressing every key issue participants face: politics, people, process, project management, and tools. No matter what your role--developer, project leader, line-of-business manager, or CxO--you'll find realistic, usable solutions. This edition's new and updated coverage includes:
Creating Mission Impossible projects out of DM projects
Negotiating your project's conditions: making the best of a bad situation
XP, agile methods, and death march projects
Time management for teams: eliminating distractions that can derail your project
"Critical chain scheduling": identifying and eliminating organizational dysfunction
Predicting the "straw that breaks the camel's back": lessons from system dynamics
Choosing tools and methodologies most likely to work in your environment
Project "flight simulators": wargaming your next project
Applying triage to deliver the features that matter most
When it's time to walk away
This isn't a book about perfectly organized projects in "textbook" companies. It's about your project, in your company. But you won't just recognize your reality: you'll learn exactly what to do about it.
Table of contents
- Copyright
- Mission Statement for Yourdon Press Series
- About the Series Editor
- Selected Titles from the Yourdon Press Series
- Preface
-
1. Introduction
- Death March Defined
- Categories of Death March Projects
-
Why Do Death March Projects Happen?
- Politics, politics, politics
- Naive promises made by marketing, senior executives, naive project managers, and so on
- Naive optimism of youth: “We can do it over the weekend”
- The “startup” mentality of fledgling entrepreneurial companies
- The “Marine Corps” mentality: Real programmers don't need sleep
- Intense competition caused by globalization of markets
- Intense competition caused by the appearance of new technologies
- Intense pressure caused by unexpected government regulations
- Unexpected and/or unplanned crises
-
Why Do People Participate in Death March Projects?
- The risks are high, but so are the rewards
- The “Mt. Everest” syndrome
- The naiveté and optimism of youth
- The alternative is unemployment
- It's required in order to be considered for future advancement
- The alternative is bankruptcy or some other calamity
- It's an opportunity to escape the “normal” bureaucracy
- Revenge
- Summary
- Notes
- 2. Politics
- 3. Negotiations
- 4. People in Death March Projects
- 5. Death March Processes
- 6. The Dynamics of Processes
- 7. Critical-Chain Scheduling and the Theory of Constraints
- 8. Time Management
- 9. Managing and Controlling Progress
- 10. Death March Tools and Technology
- 11. Simulators and “War Games”
Product information
- Title: Death March, Second Edition
- Author(s):
- Release date: November 2003
- Publisher(s): Pearson
- ISBN: 013143635X
You might also like
book
Release It!, 2nd Edition
A single dramatic software failure can cost a company millions of dollars - but can be …
book
The Phoenix Project
Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into …
audiobook
The Design of Everyday Things
First, businesses discovered quality as a key competitive edge; next came science. Now, Donald A. Norman, …
book
Design It!
Don't engineer by coincidence-design it like you mean it! Filled with practical techniques, Design It! is …

