how not to manage a project! (lessons learned in project management) pmi wdc kxf 10-26-04
DESCRIPTION
How NOT to Manage a Project! (Lessons Learned in Project Management) PMI WDC KXF 10-26-04. Presented by: A. Scott Dam, P.E. ASD E&C and SPEC [email protected]. Outline. Introduction Project Failures Initiation Planning Execution Controlling Closing Summary. Introduction. - PowerPoint PPT PresentationTRANSCRIPT
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
1
ASD E&C
Engineers & Consultants
How NOT to Manage a Project! (Lessons Learned in Project Management)
PMI WDC KXF 10-26-04
Presented by:A. Scott Dam, P.E.
ASD E&C and [email protected]
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
2
Outline
● Introduction● Project Failures● Initiation ● Planning● Execution ● Controlling● Closing● Summary
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
3
Introduction
● How many of you have worked on a project that was never completed, i.e., cancelled, rescheduled, shelved, and/or forgotten, …?
● Why?● What are you (or your organization) going to do
about it?● We will discuss how not to manage a project as
lessons learned for future projects.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
4
Project Failures
● US Dept. of Energy projects – GAO & NAS-NRC reviews – OECM formed
● NASA Projects
● Large Engineering-Construction Projects
● Commercial projects
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
5
DOE Projects
● A few examples from GAO reports – - Rocky Flats - 100 projects <$2M each; 5 fold
increases (1992)- 1980 to 1996 31 of 80 major projects terminated prior
to completion due to changes in mission, management problems, cost overruns, and schedule slippages
- National Ignition Facility – management and oversight failures caused major overruns ($1.2B to $2.2B)
● National Research Council – Congressional direction - 5 years of reviews of projects - major project management improvements due to management failures (OECM formed; directives)
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
6
NASA Projects
Effect of Requirements Definition Investment on Program Costs – Werner M. Gruhl, NASA
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
7
Large Engineering Projects
● Big transportation projects – BART to SFO: $590M to $1.5B; Boston Big Dig: $7.7B to $14.6B (Guy Span, Bay Crossings)
● Donghai Bridge, China - $350M to $1.2B (UPI)● Shell Russian Oil Project – $10B overrun
(Money)● Westchester County Courthouse $51.5M over
$140MWeb search on Google: Project Cost Overruns –
44,100 hits
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
8
Commercial Projects
● IT and application development projects often fail to be completed on time and budget; 1/3 exceed by 100% (Gartner research)
● IT projects goes from $1M to $3M, before being cancelled (Suzanne Thornberry)
Many articles and consultants offering how to manage projects; PMI training – PMP, etc.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
9
Initiation
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
10
Our project was just approved!
We’re happy now, just wait.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
11
So how to we get started with our project?
?
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
12
Don’t worry, I’ve got it covered!
PM
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
13
Jump in with both feet!
Just start out doing the project, we don’t need to plan ahead or even know what we’re trying to accomplish.
We’ll know we finished when we get there.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
14
What hidden dangers?
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
15
Ok, so now what?● Starting with an Un-achievable Goal, an Ineffective Organization, or a
Project without a clear mission?● Organization & Initiation – we don’t need to bother do we?
- Project Charters – why do we need one of those?▪ Mission – why do we want to do this project?▪ Goals – set unachievable goals - key accomplishments we can never make anyway so
don’t bother to write down now.▪ Who will do it? ▪ Authority to accomplish mission & goals?
- Project Organizations – volunteers wanted - anyone can be the PM!▪ Strong, weak, non-existent PM & PMO▪ Project team – any one know what they’re doing? Why do we need a project controls
person, can’t the PM do it too?▪ I don’t need to go to that PM training class, do I?
● Just start the project and don’t tell anyone what we’re doing, they don’t need to know.
● Should we quit now? YES
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
16
Planning
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
17
Some times the it seems too high to overcome.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
18
Don’t Plan the Project
● Don’t develop a realistic WBS, project cost estimate, or schedule
● Don’t document how you will organize and manage the project; don’t develop project procedures
● What’s a risk analysis?● Don’t listen to experienced people or check any
lessons learned from other projectsMany projects fail due to poor estimating and resulting cost overruns
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
19
If it’s not one hurdle, it’s another
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
20
Execution
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
21
Or Suicide?
● So now you’re into the project delivery activities, do you know what to do when; how?
● Milestones? Due dates? “you’ve got to be kidding”● How much “help” are you getting from “corporate (or the
customer)”?● What’s risk mitigation?● Be sure not to tell anyone how we’re doing, it’s up to
them to find out for themselves.
Other major causes of project failures are poor monitoring of project activities and poor communications
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
22
Project managers must perform the real balancing act - cost, schedule, scope!
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
23
Keep on, you’ll get there
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
24
Controlling
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
25
Project Controls?
● What do you mean actuals to date? Anyone heard of BCWP?
● You want what? Oh, the status of cost & schedule against plan. Someone else was supposed to provide that the information.
● No problem providing an ETC!
Just take the budget and double it.
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
26
Just give us some more time!
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
27
Closing
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
28
Don’t Document Failures (or Successes)
● Why should we help out the next PM or project team?
● Let them learn for themselves – it’s more meaningful that way
● Don’t provide files for anyone else, if anyone wants the info they’ll have to see me!What if it is me wanting to start a new project?
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
29
Summary
● Planning, then execution – it’s hard to achieve the plan if you don’t have one.
● All the “don’ts” are “do’s”● Use proven PM practices● Tailor your PM practices to your specific
project ● Be careful of what you promise
It’s not difficult but requires attention to the details – doing it right will lead to success
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
30
We completed our project on time and budget and with customer acceptance!
10/26/2004 How NOT to manage a project! (c) A. Scott Dam 2004
31
Questions & Discussion