Register your product to gain access to bonus material or receive a coupon.
Historically, all software projects have involved a certain degree of risk and pressure -- but many of the projects in today's chaotic business environment involve such intense pressure that they are referred to colloquially as "death-march" projects -- i.e., projects whose schedules are so compressed, and/or whose budgets, or resource (people) assignments are so constrained, that the only "obvious" way to succeed is for the entire team to work 16 hours a day, 7 days a week, with no vacations until the project is finished. While the corporate goal of such projects is to overcome impossible odds and achieve miracles, the personal goal of the project manager and team members often shrinks down to mere survival: keeping one's job, maintaining some semblance of a relationship with one's spouse and children, and avoiding a heart attack or ulcer. This new and thoroughly-updated edition of Ed Yourdon's book takes into account many of the changes that have taken place in the more than six years since the publication of the first edition.
Managing a Doomed Software Project: Practical Suggestions for Breaking the Bad News
What is a Death March Project and Why Do They Happen?
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.