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:
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.
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.
Identifying the Political Players in the Project.
Determining the Basic Nature of the Project.
Levels of Commitment by Project Participants.
Analyzing Key Issues that Lead to Political Disagreements.
Identifying Acceptable Tradeoffs.
What To Do When Negotiating Fails.
Hiring and Staffing Issues.
Loyalty, Commitment, Motivation, and Rewards.
Rewarding Project Team Members.
The Issue of Overtime.
The Importance of Communication.
Workplace Conditions for Death March Project.
The Concept OF Triage.
The Importance OF Requirements Management.
SEI, ISO-9000 and Formal Versus Informal Processes.
Best Practices and Worst Practices.
Death March Meets XP.
Models of Software Development Processes.
Static Versus Dynamic Models.
An Example: Tarek Abdel-Hamid's Software Process Model.
Summary and Conclusions.
What Organizational Behaviors are Dysfunctional?
How Can We Change Dysfunctional Organizational Behavior?
Life in a Rational World.
The Impact of Corporate Culture On Time Management.
Time Slippage from Stakeholder Disagreements.
Helping the Project Team Make Better Use of Time.
The “Daily Build” Concept.
Additional Ideas for Monitoring Progress: Milestone Reviews.
The Minimal Toolset.
Tools and Process.
Risks of Choosing New Tools.
The Concept of War Games.