end the project death march: do more projects and boost team engagement!
DESCRIPTION
This presentation was given at the 2014 Project Management Institute - Central Indiana Chapter professional development day in Indianapolis on October 3rd, 2014. Venue: Wyndham Indianapolis West.TRANSCRIPT
PMI – Central Indiana Chapter Professional Development Day
Joe Cooper, PMP, PMCP
: 1joecooper
PMI – Central Indiana Chapter Professional Development Day
Resolve crisis and high-stress in projects Significantly improve meeting delivery
commitments Simplify with pragmatic estimating Visually report project health early and
objectively
210/3/14
310/3/14
Wait a minute… Something feels wrong!!
410/3/14
In project management, a “death march” is a project where the team feels it is destined to fail, or requires periods of unsustainable work; frequent nights and weekends.
A project like this is usually filled with crisis and panic, particularly toward the end.
Photo from cover of book titled “Death March” by Edward Yourdon
510/3/14
610/3/14
Schedule overruns 74%, up from 71% in 2010
Budget overruns 59%, up from 46% in 2010
Features delivered 69%, down from 74% in 2010
710/3/14
810/3/14
910/3/14
1010/3/14
Schedules cut by sponsors or management Expecting every task to complete "on-time" Expecting later task owners to "make up time" when
earlier tasks slip Cutting testing when project commitment date is in
jeopardy Green to red status overnight Overtime required - nights and weekends Heroics needed to finish the project "No organization can possibly survive if it needs geniuses
to manage it" -Peter Drucker
1110/3/14
Yerkes-Dodson
1210/3/14
1310/3/14
1410/3/14
1510/3/14
10% confidence 50% confidence 95% confidence
2 days 5 days 12 days
.20
.40
.60
.80
1.0
1610/3/14
No progress Panic Work!
Start task Deadline
1710/3/14
Hidden
Padding
Hidden
Padding
Hidden
Padding
Hidden
Padding
Task 1 Task 2 Task 3 Task 4
Task 1 Task 2 Task 3 Task 4 Project BufferTime
Saved
1810/3/14
Hidden
Padding
Hidden
Padding
Hidden
Padding
Hidden
Padding
Task 1 Task 2 Task 3 Task 4
Task 1 Task 2 Task 3 Task 4 Project BufferTime
Saved
1910/3/14
Project Buffer
2010/3/14
2110/3/14
Buffer
consum
ed
.Project 1
.Project 2
.Project 3 .Project 4
.Project 5
.Project 6
Project duration
2210/3/14
Mazda using these methods.
2310/3/14
Chapter 17
www.tocico.org
PMI – Central Indiana Chapter Professional Development Day
Continually strive to create system harmony. Eliminate the stress that degrades performance.
Use 50/50 estimates to eliminate waste, boost team engagement, accelerate projects, and get more done.
Use a project buffer to avoid crisis, protect delivery commitments, and to enhance competitive advantage.
Create environments of FOCUS to eliminate the waste of rework and context switching.
2410/3/14
PMI – Central Indiana Chapter Professional Development Day
2510/3/14
Thank you!
Joe Cooper
email: [email protected]
phone: 309-212-6305
: joecooper1
www.Allegient.com
: 1joecooper
:slideshare.net/JosephCooperPMP