Death March Mission Impossible Projects By Edward Yourdon

Death March “Mission Impossible” Projects By Edward Yourdon 1

What are they • Death march projects are rarely billed as such. They can be hard to identify. • Project parameters exceed the norm by 100%. • Risk of failure > 50%. • Should be distinguished from hopeless and “waste of time” projects 2

Why do they happen? • When I first started hearing these stories I was puzzled, but after careful analysis I have developed a theory to explain the existence of bizarre workplace behaviour: – People are idiots. – Including me. 3

What are the requirements? • • • Want the job done twice as fast Want the job done with half the people Want the job done at half the cost Want double the functionality Want double the performance 4

Why these requirements? • Politics – Power struggle between departments – Project manager may expect failure! – We do or we die • Naïve promises – Hysterical optimism – Known lies to customer 5

Why (2) • Cuts in project schedules – Assumption that planners pad schedules • We can do it over the weekend – Minor details like input, output, testing documentation don’t count. • Start up mentality – You’re going to change the world. • But you are probably short on qualified people! 6

Why (3) • Marine Corps Mentality – Real programmers don’t need sleep – Every project is like this – We know how to get things done – It works, we’re successful and proud of it – If you can’t handle it, you don’t belong here – [Deliberate decision to create Death March] 7

Why (4) • Outside pressures – System must be operational by arbitrary date • Unexpected crises – Programmers quit over management practices. – Vendor has gone bankrupt. – You are about to be sued for violating. . . • Procrastination 8

Why do people participate? • • • Risks are high but so are the rewards The “Mt. Everest syndrome” The buzz of intensity vs boredom Naivety and youth Want to rise within organization Hero complex. . Want to save the company Regular ego boosts Revenge Avoid being fired 9

Why not to participate? • Most projects are doomed to fail – Beware of ‘negotiations’ (eg hidden maintainability costs, ‘tomorrow I will be gone’): get customer involved! • Not worth sacrificing life for a company – Life (e. g. , family and friends) are more important – https: //www. youtube. com/watch? v=HPfl. LGEHUAI • Health is priceless, beating the odds isn’t 10

Rewards of participating • • • Sense of being valued Pride in the task you are undertaking Belief in the team A real life experience, real life memories Potential career advancement 11