Why Project Management - Pearson Higher Education

SUCCESSFUL PROJECT MANAGEMENT
OVERVIEW
*
Introduction
Definitions
Constraints
Process GOALS & OBJECTIVES
The Golden Rules
SMART Goals
Commitment
Objectives
Checkpoints & Activities
**
NETWORK ANALYSIS - I
*
Scheduling
Work Breakdown Structure
Precedence
Charts
Networks
***
NETWORK ANALYSIS - II
*
Duration Estimating
Solving the Network
Critical Path
Slack/Float
Activity Crashing
Time-Scaled Networks
**
RESOURCE MANAGEMENT
*
***
Trust and Teams
Time/Cost Trade-offs
Leveling
PROJECT CONTROL
*
**
Purposes
Philosophies
Control Process
Meetings
Reporting
Continuous Control Techniques
Cost Control
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
1
 2001 by Pearson Education Inc.
All rights reserved.
WHY PROJECT MANAGEMENT?
A.
Short product life cycles
B.
Flatter organizations
C.
Time-based competition
E.
More frequent change/need for flexibility
F.
Imposed deadlines/short/late starts/needed yesterday
G.
Limited/shared resources
H.
Multiple responsibilities
I.
Involve different people/depts./priorities
J.
Regular conflict about work/approaches/budgets
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
2
 2001 by Pearson Education Inc.
All rights reserved.
Worry Level
THE WORRY CURVE
0
3
6
9
12
15
Weeks
A.
Uninformed Optimism
B.
Vague Concern
C.
Panic
D.
Heroism
E.
Desperate Negotiation
F.
Never Again!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
3
 2001 by Pearson Education Inc.
All rights reserved.
KEY OBJECTIVES AND DOCUMENTS
OBJECTIVE
DOCUMENT
I. Quality Requirements
Specifications
A.
Definition of the end product
B.
Form, fit & function
C.
Description of the end state
II. Deadlines
A.
Must complete by:
B.
Must start by:
C.
Can’t start before:
D.
Can’t have it untill:
Schedules
III. Cost limits
A.
We can only spend ...
B.
Bring it in under...
C.
If you can beat their price
D.
Our minimum margin is ...
E.
The market will bear ...
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
Budget
4
 2001 by Pearson Education Inc.
All rights reserved.
DEFINITIONS
I. PROJECT:
A combination of multiple interdependent activities requiring multiple
people and other resources necessary for the achievement of a set
of desired results.
Examples;
II. TASK:
A combination of activities leading to the achievement of definable result.
Examples;
III. ACTIVITY:
A time-consuming piece of work with a definite beginning and end.
Examples;
IV. DURATION:
The time elapsed between the beginning and the end of an activity, task or
project.
Examples;
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
5
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT CONSTRAINTS
I. TIME:
A.
We just found out!
B.
The competition is already introducing it
C.
We must make the trade show
D.
Opening day is set for...
E.
We promised to have it ready
F.
Our biggest client has to have it by ...
G.
Our newest client...
H.
Etc.
II. RESOURCES:
A.
We can’t spare him until ...
B.
The cash won't be available before ...
C.
The facility is booked untill ...
D.
The other project is a higher priority
III. OTHER CONSTRAINTS:
A.
Approval
B.
Permits
C.
Space
D.
Location
E.
Regulations
F.
Etc.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
6
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT PLANNING PROCESS
Objectives
&
Constraints
Project
Plan
Control
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
Re-Plan / Reschedule
Discover
Problems
Diagnosis
7
Resolution
Decisions
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT MANAGEMENT SYSTEMS
A.
Get a computer
B.
Someone buys a cheap package
C.
Things don't get better
D.
Bring a consultant
E.
Find appropriate software
F.
You need a bigger computer
G.
Get appropriate hardware
H.
Get appropriate training
I.
Begin to get organized!!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
8
 2001 by Pearson Education Inc.
All rights reserved.
THE GOLDEN RULES
1.
Goals
2.
Objectives
3.
Checkpoints
4.
Activities
5.
Relationships
6.
Time estimates
7.
Schedules
8.
Develop your team
9.
Reinforce commitment
10.
Inform all
11.
Vitalize agreements
12.
Empower self & others
13.
Risk creativity
GO CART DRIVER
"The Road to The Checkered Flag"
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
9
 2001 by Pearson Education Inc.
All rights reserved.
GOALS & OBJECTIVES
THE GOAL: BUILD AN ARK ... WE ARE STARTING OVER!
I. WHY IS IT CRITICAL?
A.
Doing the right things vs. doing things right.
B.
The jigsaw puzzle/working backwards.
C.
The activity trap/the well managed bankruptcy.
II. KEYS:
A.
Focus
B.
Commitment
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
10
 2001 by Pearson Education Inc.
All rights reserved.
THE FOCUS
I. HOW:
A.
Ask
1.
B.
Serious Dialogs

End users; who are they?

Upper management

Who signs the checks?

Your management
2.
Too General ... Lose weight!
3.
What not to do ... No more waste!
Clarify
1.
State results
2.
Get it in writing
3.
Get confirmation
4.
S.M.A.R.T.
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
11
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
CHECKLIST FOR SUCCESSFUL GOAL SETTING:
SPECIFIC
MEASUREABLE
AGREED UPON
REALISTIC
TIME & COST FRAMED
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
12
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
I. SPECIFIC:
A.
Can the casual participant understand it? Build an Ark ... We’re
starting over!
B.
Ask a lot of questions
What capacity?
How long will it last?
What dimensions?
Which animals?
C.
Nail down the Scope. Who will design it?
Who gets the wood?
Who gets the animals?
What about testing?
Public relations
D.
Simplify
E.
Test it on others for clarity
F.
Example;
Improve Quality
Reduce scrap of process X by 50%
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
13
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
II. MEASUREABLE:
The easier the better!
X cubits long by Y cubits wide by Z cubits high, to hold so many animals and people
for 150 days.
A.
B.
Most are easy, specific goals with common definitions;
1.
Margin
2.
Return on investment
3.
Number of returns
4.
Profit before tax
5.
Miles per gallon
6
$ purchased per customer
7.
% Canceled appointments
Fuzzy Goals;
1.
Just harder to measure!
2.
Must find a way
3.
Example;
Friendly tellers...
Frequency of small talk with customers!
Comment cards from customers.
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
14
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
III. AGREED UPON:
A.
Everyone sees project goal as desirable and fills the need! The flood is coming
and the ark will save us!
B.
Who Must Agree?
1.
Customer/end User;
Noah's descendants
Confirm usefulness
2.
Ensure success
Upper management;
GOD
Ensure fit with long term plans
3.
For back-up, support & clout
Your immediate management;
Noah's Wife
Ensure fit with immediate plans
Ensure day to day support
4.
Access to resources
The "Check signer";
Smooth compensation
Smooth invoice approval/processing
5.
Keep your suppliers/contractors happy
Peers;
Operating support/coordination
Synergies
6.
Come through in a jam
Subordinates/subcontractors;
Wood suppliers & sons
Commitment and results!
suppliers & sons
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
15
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
IV. REALISTIC:
"IT WAS A TALL ORDER AND WE GAVE IT OUR BEST SHOT"
–a failed project manager
A.
There is no honor in goals which can't be met!
B.
Beware of these traps;
What is the best you can do ...
C.
D.
1.
If you have complete freedom ...
2.
If everything went right ...
3.
If you have everything you need, exactly when you need it
MUST HAVE ...
1.
the required expertise
carpentry, veterinary
2.
adequate time
more than a few months
3.
access to needed resources
sons and forest
4.
sufficient funding
God's total support
5.
acceptable constraints
DO A REALITY CHECK!
1.
How long does it take to build an oil tanker?
2.
Usually must adjust;
schedules
Can the flood be put off a
century?
resources
Will you send subcontractors?
OR
the Goal!
Can we drop the dinosaurs?
THE FOCUS—Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
16
 2001 by Pearson Education Inc.
All rights reserved.
THE S.M.A.R.T. GOAL
V. TIME AND COST FRAMED:
A.
B.
Reasonable deadlines;
1.
for project completion
2.
for major milestones
3.
does not require crashing all major activities
4.
does not assume crashing activities out of your control
5.
flexibility to further crash activities
6.
flexibility for the sunshine rule
Reasonable budgets;
1.
adequate capital provision
2.
adequate expense provisions
3.
consolidated and under your control
4.
allows for critical premium costs
5.
identified contingency fund/sum
6.
flexibility for the unexpected
7.
flexibility between line items
S.M.A.R.T. GOALS TAKE LOTS OF TIME AND ENERGY.
THEY ARE WELL WORTH IT.
THEY CANNOT BE REPLACED.
JUST DO IT!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
17
 2001 by Pearson Education Inc.
All rights reserved.
THE COMMITTMENT
Consider the bacon and eggs breakfast . . .
the chicken was involved,
but the pig was committed!
I. GET THE COMMITTMENT:
BUILDING A WALL VS. BUILDING A CATHEDRAL!
A.
Create a vision!
1.
Distinctive
2.
Relate to a basic aspiration
3.
Build on a common discontent
4.
Touch on a basic/noble cause
5.
Clear, concise, and complete
II. MAINTAIN THE COMMITTMENT:
B.
Communicate the vision;
1.
write it down
2.
send it to everyone
3.
post it every where
4.
repeat it often
5.
restate it in meetings
6.
remind others during problem solving
7.
check and verify that every one knows it!
8.
update it if major conditions change!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
18
 2001 by Pearson Education Inc.
All rights reserved.
OBJECTIVES
I. What are they ?
A.
Sub-goals of the project goal
B.
The beginning of work breakdown structure.
II. Why Have Objectives?
A.
More manageable chunks leading to the overall Goal.
procurement of x board feet of gopher wood
making x planks 7 ft by 1 ft by 3 inches each
acquiring and maintaining the animals
B.
Clarifies the role of functional group.
Real estate group will get football field nearby
Lumberjack union will provide all lumber
C.
Identifies which skills/resources are needed.
carpenters
haulers
veterinary
sailors
D.
Identifies who needs to be on the team.
E.
builds commitment and ownership by participants.
We told Noah we'd get the animals by next week and that's exactly
what we will do.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
19
 2001 by Pearson Education Inc.
All rights reserved.
OBJECTIVES
I. How?
A.
List the major needs for the project. (Noah's Ark);
a big place to build it
lots and lots of wood
some serious carpentry work
high lifting of big items
waterproofing
animal rounding up
care and feeding of animals
B.
Identify functional groups to fulfill these needs;
real estate group
forestry dept.
C.
Dialogue with each functional group to spell out objectives.
define the three aspects; quality, time, & cost
use the S.M.A.R.T. techniques
D.
Clarity ... pre-requisite to peak performance.
E.
Connection with overall project goal.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
20
 2001 by Pearson Education Inc.
All rights reserved.
OBJECTIVES
I. KEYS:
A.
Maintain a broad focus;
avoid tangents and getting
lost in the details.
B.
C.
insisting on
cedar cabinetry!
Rewards that work;
no internal competitions
team with highest woodpile
wins
clearly support overall goal
this thing must float. All
seamless fits are rewarded!
encourage creativity
easiest way to hoist biggest
planks
Authority to match responsibility;
from upper mgmt. to dept. mgmt.
–formalized co-responsibility
from dept. managers to participants
–shared performance evaluations
build relationships with dept. managers
–valued colleague and ally.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
21
 2001 by Pearson Education Inc.
All rights reserved.
CHECKPOINTS & ACTIVITIES
Remember the Worry Curve?... Small Deliverables!
Objectives are big chunks of the Project ... Need small day-to-day chunks to manage!
Next step in Work Breakdown Structure
Deeper into the Level of Detail
I. CHECKPOINTS:
A.
Events and milestones.
II. ACTIVITIES:
B.
The road between them!
III. WHY HAVE THEM?
A.
Markers along the road to check progress towards the goal
B.
Helps keep participants committed & motivated; the breakfast of
champions ... feedback!
C.
Figuring out the best routes
D.
Contingency planning
IV. HOW:
A.
Ask the functional groups
B.
Appropriate level of detail
C.
defined beginning and end
D.
describe in terms of end-results
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
22
 2001 by Pearson Education Inc.
All rights reserved.
RELATIONSHIPS & TIME ESTIMATES
DETERMINES SHORTEST POSSIBLE TIME TO COMPLETION.
SHOWS NEEDED RESOURCE UTILIZATION PROFILES;
i.e. PEAK LOADS VS. AVAILABLE CAPACITIES!
I. RELATIONSHIPS BETWEEN ACTIVITIES:
A.
Finish to Start
B.
Finish to Finish
C.
Start to Start
concurrent/interdependent
II. HOW:
A.
Ask the participants (those who will do the work!);
necessary order
logical flow
technological requirements
critical resource availability
most efficient sequence
flexibility for contingency planning
B.
Highlight alternatives
C.
Creative and thorough
III. DEALING WITH UNCERTAINTY:
A.
Three estimates
B.
What could go wrong?
C.
Consensus
D.
Ranging
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
23
 2001 by Pearson Education Inc.
All rights reserved.
AGENDA
Project Network Analysis
A.
Building a picture of the project; scheduling
B.
Work breakdown structure
C.
The appropriate level of detail
D.
Identifying meaningful activities
E.
Relationships and precedence analysis
F.
Project networking techniques
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
24
 2001 by Pearson Education Inc.
All rights reserved.
BUILDING A PICTURE OF THE PROJECT; SCHEDULING
Why Spend the Effort?
1.
A more realistic plan ...
more complete picture of what it takes to achieve the Goal
2.
Able to anticipate what needs to happen next
3.
Know where to concentrate your attention
4.
Anticipate Bottlenecks and other Coordination Problems
5.
Enhance coordination and communication among participants
6.
Clear awareness of interdependencies among participants
7.
Build commitment and accountability . . .
clearly identifies responsibilities and deadlines
8.
Flexible, active tool leading to completion of the project . . . On Time,
Within Budget, and Meeting Specifications!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
25
 2001 by Pearson Education Inc.
All rights reserved.
WORK BREAKDOWN STRUCTURE
Definition: A logical hierarchy of work packages involved in the project.
Why?
A.
A thorough method to identify objectives, milestones, events, and
activities.
B.
Assists in the identification of relationships between functions.
C.
Facilitates the development of schedules, budgets, and resource
requirements.
D.
Provides structure for "rolling up" lower level schedules, costs and
resources.
Keys:
A.
Based on how the work will be divided among individuals,
organizational units, or contractors.
B.
Clear assignment of a work package manager, responsible for
successful completion of each work package.
A.
Dividing and sub-dividing a project into smaller and smaller work
packages.
B.
Create a diagram similar to an organization chart.
C.
Segmentation may be according to:
How:
1.
2.
Component, subsystem, or part;

a missile system could be divided into body,

engine, fuel system, warhead and guidance system. the
Ark would be divided into the hull, interior, superstructure,
and habitat.
Work phase or resource type;

R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
development of a computer information system could be
divided into system specification, coding, installation, user
testing/debugging, and documentation.
EXAMPLE; one-car garage
26
 2001 by Pearson Education Inc.
All rights reserved.
WORK BREAKDOWN STRUCTURE
I. The Appropriate Level of Detail
A.
Must be keyed to the level of management using the network.
a top mgmt. network shows high level elements, down to major
organizational units or SBUs.
operational mgmt. network will show elements rolled down to
functional units
project mgmt. network will show full activity detail.
II. Identifying meaningful Activities
B.
When a different resource comes into use.
Prepare site breaks into;
C.

layout site

clear site

grade site
One activity dependent on a portion of another.
divide at the point of dependency
D.
Unusually long activities.
break up to provide visibility into status.
E.
When in doubt, break it down.
analyst can later combine without help.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
27
 2001 by Pearson Education Inc.
All rights reserved.
RELATIONSHIPS AND PRECEDENCE ANALYSIS
Definition: Indication of sequencing requirements between two activities.
I. Reasons for Precedence Relationships:
A.
Technical
1.
2.
B.
Physical or technical requirement

write paper before printing

pour foundation footings before floor slab

test before repair
Safety considerations

disconnect power before disassembly

continuity test before power up

locate utilities before digging
Policy or Preference; ( May increase time and cost!)
1.
Quality and efficiency

2.
Internal policy

3.
capital appropriation before purchase orders
Legal requirements

C.
paint ceiling then lay carpeting
environmental impact study precedes contracting
Restricted resources;
1.
Conflict with other work
2.
Bottleneck facilities

processing time on mainframe computer

scheduling the 400 ton crane
3.
Limited cash flow
4.
Limited space

5.
f-16 cockpit wiring
Separate locations
EXAMPLE; Surprise Cake
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
28
 2001 by Pearson Education Inc.
All rights reserved.
SCHEDULING
Scheduling Tools: Bar Charts and Flow Charts
I. Bar Charts: a.k.a. Gantt Chart, Time Line.
A.
Example; E.V. Conversion project
B.
Basic parts
Time scale
List of activities
Bar for each activity shows when it starts and represents its duration.
C.
D.
Advantages of bar charts
1.
Easy to read visual picture of activities, events, etc.
2.
gives everyone a quick overview of the project
3.
quickly indicates status of the project
4.
great for individual tracking of their own progress
5.
special bar charts help coordinate efforts for handoffs
6.
Great tool to analyze what-ifs and alternative plans
7.
can be drawn to show budgets, people needs, equipment use
Disadvantages of bar charts;
1.
Does not show precedence relationships clearly
2.
Can be tedious to manually reflect changed schedules
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
29
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT NETWORKING TECHNIQUES
I. Flow Charts: a.k.a. Networks
A.
Designed to show the flow of work and highlight precedence
relationships.
B.
Activities-on-Arrows network:
C.
Example - The Cake
Each activity represented by an arrow between two nodes.
Arrows leading to the starting node represent pre-requisites.
Arrows leading from the end node represent post-requisites.
D.
Special Situation;
A precedes B & C. B precedes D & E. C must finish before E can
start. F can’t start till both D & E are finished.
Illustrates need for Dummy Activities.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
30
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT NETWORKING TECHNIQUES
I. Activities-on-Nodes Networks:
A.
Each activity is represented by a node (box). Precedence is indicated
by arrows between the nodes
FS
SS
FF
Composite (to reduce complexity)
Example - The Cake
B.
Shows unique starts and unique ends.
C.
Back to the previous example; A precedes B & C. B precedes D & E.
C must finish before E can start. F can’t start till both D & E are
finished.
Easy, Fast & Readable!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
31
 2001 by Pearson Education Inc.
All rights reserved.
AGENDA
Sample Problems
Project Network Analysis
I. Century Manufacturing Company
II. 2-Car Detached Garage
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
32
 2001 by Pearson Education Inc.
All rights reserved.
SAMPLE PROBLEM # 1
1ST STAGE
I. Century Manufacturing Company
Instructions:
1.
Read the problem text.
2.
Gather in teams of two or three.
3.
Create precedence chart.
4.
Construct network and clean it up.
5.
Keep your work..... we will need it for later exercises.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
33
 2001 by Pearson Education Inc.
All rights reserved.
SAMPLE PROBLEM # 2
1ST STAGE
II. A Two-Car Detached Garage
You are the General Contractor for this first class, turn-key project.
Architectural plans and specs are complete. No permits have been applied for. Site not
yet cleared. You have engaged sub-contractors.
The garage will require interior trim, two windows, workbench, cabinet work, power
outlets, automatic door openers, outside lighting and landscaping and a security
system.
1.
Stay in teams.
2.
Create an activity list, down to trade level.
Need approximately 35 activities.
3.
Create precedence chart.
4.
Construct network and clean it up.
5.
Keep your work. It will be needed in subsequent exercises.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
34
 2001 by Pearson Education Inc.
All rights reserved.
AGENDA
A.
Activity Duration
B.
Duration vs. Cost
C.
Critical Path
D.
Slack and Float
E.
Time-Scaled Networks
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
35
 2001 by Pearson Education Inc.
All rights reserved.
ACTIVITIY DURATIONS
Definition: Elapsed time between the start and finish of an activity. (importance of
properly naming an activity)
I. Keys:
A.
Commitment
B.
Realistic
II. Steps to determine Activity Duration:
A.
Define most cost efficient technical approach;
|(who, how, how many)
B.
Estimate how long it should take.
C.
Selectively adjust for common problems.
1.
STEP I: Define technical approach;

Normal approach. Used in competitive bidding process.

Start with tried and true techniques whenever possible.
2.
STEP II: Estimate Normal Duration;

Based on no problems (conservative, no low balls)

Use more than one estimating technique.

Get agreement! Consult with all concerned.

No need to push for tight estimates yet!
3.
STEP III: Common Problems;

Rain, freeze, etc.

Power spikes, network glitches, etc.

5 day activity with 20% chance of rain.....use 6 days! if no
rain?.....

Do not apply to the whole schedule.
III. Special Cases:
A.
B.
C.
D.
Approvals and permits
Inspections
Deliveries
Breakdown and repairs
no project resources consumed
must allow time
self-fulfilling prophecies
get comfortable commitment
later push if driving the project
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
36
 2001 by Pearson Education Inc.
All rights reserved.
ESTIMATING TECHNIQUES
A.
Get Commitment!
B.
Never fail to consult with those who will do the task!
C.
Suggest and use the following techniques with them;
1.
Experience
2.
Historical data base
3.
Research
4.
Modeling
5.
Break-down/Roll-up
6.
Experiments
7.
Delphi method
8.
Consultant
9.
Three outside estimates
10.
Ranging
11.
S.W.A.G./W.A.G.
12. Others;
TRUTH IS THE ISSUE!
EXAMPLE; THE CAKE – Continued on next pages
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
37
 2001 by Pearson Education Inc.
All rights reserved.
DURATION VS. COST
I. Direct Costs:
Variable; a function of resource usage.
II. Normal Cost:
The direct cost of the most efficient combination of resources.
III. Activity Crashing:
The compression of activity duration beyond the most efficient combination
of resources (normal duration), while maintaining quality
requirements.
Examples
using overtime
doubling up resources, more men on the job!
lot splitting
subcontracting portions
using faster resources, air freight, bigger machines, (high school kid
vs. ditch witch)
IV. Costs of Crashing Activities:
overtime premium
subcontractor's profit
coordination effort
multiple setups
more expensive resources
other...
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
38
 2001 by Pearson Education Inc.
All rights reserved.
DURATION VS. COST
EXAMPLE:
Staff Assigned
Duration (hrs)
2
3
4
5
6
7
8
D. Cost (man-hrs)
25
14
10
9
8
8
8
50
42
40
45
48
56
64
1.
Identify normal point (least cost).
2.
Identify crash point (shortest duration).
Direct
Cost
Planned Duration
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
39
 2001 by Pearson Education Inc.
All rights reserved.
SOLVING THE NETWORK
EXAMPLE:
Given the sample network below:
1.
Perform forward pass calculations.
2.
Determine project duration.
3.
Identify the critical path.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
40
 2001 by Pearson Education Inc.
All rights reserved.
CRITICAL PATH I
I. Definitions:
A.
Path:
Unique sequence of events which connects the start and end of a
project.
B.
Critical Path:
The path(s) with the longest combined event duration in the network.
C.
Characteristics:
No slack
Delay of any C.P. activity will delay the project
Longest duration ( = project duration)
D.
Methods:
Add up all paths and compare
OR
Trace back the EPS
E.
F.
Reality Check:
Verification that planning was good;
1.
Assumptions
2.
Precedences
3.
Duration estimates
4.
Completeness
Questions to ask;
1.
Is project duration reasonable?
2.
Are C.P. activities truly critical?

scarce resources

expensive

high skills
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
41
 2001 by Pearson Education Inc.
All rights reserved.
SLACK/FLOAT
I. Definitions:
A.
EPS: Earliest Possible Start time of an activity.
B.
EPC: Earliest Possible Completion time of an activity.
EPC = EPS + Duration
C.
LAS: Latest Acceptable Start time of an activity.
LAS = EPS + Slack
D.
LAC: Latest Acceptable Completion time of an activity.
LAC = LAS + Duration
II. Path Slack (Total Slack):
TS = LAC – EPC
Delay in any (or several) activity(s) on a path which would not delay
the project.
A.
Dangerous. (See E & H using respective slack delays entire project)
B.
Belongs to the project manager
III. Activity Slack (Free Slack):
FS = EPSs - EPCp
Delay in any ONE activity which would not affect the EPS of the next
activity.
(see E, FS = 16 - 14 = 2)
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
42
 2001 by Pearson Education Inc.
All rights reserved.
CONTINUATION OF SAMPLE PROBLEMS
2ND STAGE
I. Century Manufacturing Co. :
A.
Use durations stated in the problem text.
B.
Perform forward pass calculations.
C.
Perform backwards pass calculations.
D.
Identify critical path and project duration.
E.
Compare to other teams and optimize.
F.
Re-calculate network.
G.
Show free slack and total slack.
II. Two Car Garage:
A.
Estimate and assign normal (most efficient) crew size for each
activity.
B.
Estimate normal activity duration in working hours based on crew
size. Assume 20% chance of rain for weather-contingent activities.
C.
Identify Critical path and project duration.
D.
Compare to other teams and validate the plan.
E.
Re-calculate network.
F.
Show free slack and total slack.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
43
 2001 by Pearson Education Inc.
All rights reserved.
TIME SCALED NETWORKS
I. Rules:
A.
A variety of bar charts.
B.
Keep critical path(s) activities on main center line(s) in precedence
sequence.
C.
Represent duration by bar length.
D.
Plot others above and below C.P.
E.
Use EPS/EPC points.
F.
Use dotted arrows to show precedence.
II. Applications:
A.
Use in project meetings.
B.
Use when solving problems.
C.
Use when crashing activities.
III. EXAMPLE:
A.
Plot a time-scaled network for the C.P. example above.
B.
Find the slack.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
44
 2001 by Pearson Education Inc.
All rights reserved.
BUILDING TRUST & BUILDING TEAMS
A.
The art of motivation!
B.
Must be genuinely interested in the people;
C.
Know thyself...strengths, weaknesses, expectations, what makes you tick!
D.
Examine expectations ... the other participants’ perspective
E.
1.
All are motivated ... find the indirect needs!
2.
Maslow’s hierarchy
3.
Find the overlap between the project goal and the individual's goals
Spend time talking to personnel….
1.
Ask their needs and desires.
2.
Ask what they get out of this project.
3.
Ask what you can do for THEM. Then DO IT!
4.
Ask them for THEIR estimates of duration & contingencies.
5.
Ask what-if questions.
6.
Ask how-else questions.
7.
Absolutely come through on promises!!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
45
 2001 by Pearson Education Inc.
All rights reserved.
BUILDING TRUST & BUILDING TEAMS
I. Stages of a Team:
A.
Orientation..... the honeymoon.
B.
Dissatisfaction
C.
D.
E.
1.
realization of reality
2.
disappointment with shortcomings
3.
jockeying for influence
4.
in-fighting
Resolution...
1.
roles settled
2.
rallying around the leader
3.
cohesion
4.
avoiding disagreement
Productivity...
1.
goal focus
2.
willingness to help one another
3.
frank & open discussion of problems
4.
creative problem solving
5.
respect for each other’s expertise/ability
Dissolution...
1.
anti-climax
2.
slacking off
Leader must nudge and manage the team
through the first two stages in order to get to the 3rd and 4th.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
46
 2001 by Pearson Education Inc.
All rights reserved.
BUILDING TRUST & BUILDING TEAMS
II. Needs from a Leader….
A.
Direction; clear and consistent.
B.
Guidance/coaching; know it or get an expert.
C.
Support
D.
1.
use your clout on their behalf.
2.
recognize their individuality
3.
encourage creativity
Encouragement
1.
show the light at the end of the tunnel.
2.
reward trial & error (when appropriate).
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
47
 2001 by Pearson Education Inc.
All rights reserved.
TIME/COST TRADE-OFF ANALYSIS
I. Cost Definitions
A.
Direct costs
1.
Labor wages
2.
Overtime premium
3.
Material
4.
Equipment rental
5.
Sub-contracting
6.
Travel (some)
7.
Freight, shipping
8.
Sales tax
9.
Specific support services
B.
Indirect Costs
1.
Insurance
2.
Administration
3.
Overhead costs
4.
Start-up costs
5.
Contingencies
6.
Permits
7.
License
8.
Utilities
9.
Office/furniture rent
10. Supervision
11. Inspections
12. Legal fees
13. Security services
14. Lost production
15. Project management
16. Safety/accidents
17. Marketing costs
18. Penalties
19. Cost of funds
20. Strike
21. Good will
22. Travel
23. Intangibles (numerous)
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
48
 2001 by Pearson Education Inc.
All rights reserved.
TIME/COST TRADE-OFF ANALYSIS
Cost
Planned Project Duration
May continue to crash as long as incremental indirect costs exceed incremental direct
costs.
Objective: Minimum Total Cost!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
49
 2001 by Pearson Education Inc.
All rights reserved.
CRASHING ACTIVITIES
I. Characteristics of Good Candidates:
A.
On critical path
B.
Bottle necks/preceding multiple activities
C.
Long duration
D.
Lower cost per period gained
E.
Early in the project;
1.
More choices
2.
Better control
3.
Recovery time if failed
F.
Labor intensive/low skill
G.
Subject to common problems;
1.
Less probability of problems
(make hay while the sun shines)
2.
Subject to frequent change
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
50
 2001 by Pearson Education Inc.
All rights reserved.
EXAMPLE PROBLEM
Activity
A
B
C
D
E
F
G
Normal
Duration
3
6
2
5
2
7
4
Project Duration:
Indirect Cost:
12
$900
Normal
Direct
Crash Cost Slope
Cost
Duration ($/day)
50
2
50
140
4
60
50
1
30
100
3
40
55
2
0
115
5
30
100
2
70
610
11
10
9
8
$820
$740
$700
$660
7
$620
F
A
0
G
B
4
6
C
2
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
7
5
3
START
D
END
0
E
2
51
 2001 by Pearson Education Inc.
All rights reserved.
RESOURCE LEVELING
RESOURCE
REQUIREMENTS
TIME
I. Typical Resources
A.
B.
C.
D.
E.
Personnel
Equipment
Material
Money
Experience; staff
Sub-contractors
F.
Staff services
G.
Project managers
H.
Facilities
II. Why Level Resources:
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.
Costs of hiring/firing
Cost of overtime
Cost of temporaries
Better utilization of personnel
Cash flow considerations
Control/coordination problems
space constraints
Morale
Improved Quality/safety
Limited equipment/facilities availability
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
52
 2001 by Pearson Education Inc.
All rights reserved.
RESOURCE LEVELING
Objective: Flatten the resource profile without impacting cost or duration.
I. HOW:
A.
Use one-hat method (except rare unique resources).
B.
Do not change activity duration.
C.
Do not change precedence relationships.
D.
Use free slack to selectively move activity start times to non-peak
periods.
E.
Move those activities to later start time.
F.
Begin at the end of the project & move backwards.
G.
Generate resource profile.
H.
Generate time-scaled network diagram.
I.
Go to peak. Find activity with lots of slack and move it to valley.
J.
Re-generate resource profile.
K.
Repeat until profile is satisfactory or slack is used-up.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
53
 2001 by Pearson Education Inc.
All rights reserved.
D
A
2
F
1
4
K
3
E
G
5
END
4
0
START
B
0
2
15
H
8
J
5
C
I
1
3
12
10
RESOURCE
RQMT 8
IDEAL PROFILE
6
4
2
1
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
2
3
4
5
6 7 8
9
TIME PERIODS
54
10 11 12 13 14 15
 2001 by Pearson Education Inc.
All rights reserved.
CONTINUATION OF SAMPLE PROBLEMS
3RD STAGE
I. Century Manufacturing Co. :
A.
Re-plot the latest network and Gantt chart.
B.
The project needs to be shortened by 15%. Identify the activities you
would crash and the order in which to do it.
Explain the justification of your decisions.
II. Two Car Garage:
A.
Re-plot the latest network and Gantt chart.
B.
Calculate activity man-hours for each worker type. Assume two
worker types; Electrician @ $25/hr and General labor @ $15/hr.
1.
Plot Resource Profile for general labor.
2.
Perform resource leveling and record your decisions. Show
resulting resource profile.
3.
Re-plot the latest network and Gantt chart.
C.
Calculate labor cost for each activity.
D.
The owner wants the garage completed early. He offers the G.C. a
bonus of $160 per day saved.
1.
Identify likely activities you would crash.
E.
2.
Estimate the daily cost of crashing for each and its fully
crashed duration. Describe how the crashing is to be achieved.
Assume overtime premiums are 50% and hiring costs are $100
for general labor and $200 for electricians.
3.
Determine which activities can be profitably crashed.
4.
Highlight the new critical path(s).
5.
Re-level your general labor resources. Show resulting profile.
Summarize your team effort by recording on your node diagram the
following:
1.
Project duration before crashing.
2.
Project duration after crashing.
3.
Percentage duration improvement
4.
Percentage critical activities vs. total activities after crashing.
5.
Estimated net bonus.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
55
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT CONTROL
I. WHY
A.
The best laid plans go wrong.
B.
To have the best opportunity resolving obstacles towards reaching
the project’s goal on time, at specs and within cost.
C.
To be in control!
D.
The function of the project manager.
II. PURPOSES
A.
B.
C.
Find Problems
1.
Time is the enemy...any problem can be solved given enough
time!
2.
Go out looking for problems ...

some anticipated during planning ... early warning signs.

new unanticipated problems ... must be sniffed out, ask
lots of questions.

the earlier a problem is detected, the less expensive !
Solve Problems
1.
That’s what we are here for.
2.
Get back on track ASAP!!!
3.
This is where YOU need your team!
Update The Plan
1.
New schedule
2.
New agreements
3.
New cost projections
Current Schedule;
A.
Regular updates are best
B.
“Rev.” control is critical
C.
to monitor progress of latest solutions
III. KEY
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
56
 2001 by Pearson Education Inc.
All rights reserved.
PHILOSOPHIES OF PROJECT CONTROL
When problems arise...
I. Two Opposing Philosophies;
A.
B.
Eliminate All Deviations from Plan. (Dogmatic Dan)
1.
Meet activity deadlines at all costs.
2.
No tolerance for variances. Exclusive use results ...?
Accommodate Deviations and Re-plan Project. (Laid-back Lucy)
1.
Accept and make allowance for miss-planning and surprises.
2.
Make-up lost time in other activities. Exclusive use results ...?
MUST USE A COMBINATION OF BOTH PHILOSOPHIES !!
II. KEYS FOR EFFECTIVE CONTROL:
A.
Completion Oriented.
B.
Near-term Commitment ... no fuzzy answers. A hand-over time.
C.
Earliest Possible ...best position to deal with problems. takes care of
little things.
D.
Accountability
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
57
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT CONTROL PROCESS
I. Communication
A.
To update the schedule
B.
Relevant to recipient
C.
Prefer face to face
D.
E-Mail ... frequent, short messages
II. Participation
A.
All responsible parties
B.
Decision-makers and doers only
C.
In-house AND outside members
III. Analysis
A.
Impact of current activities on; project completion and budget.
B.
What-if ... prepare response to potential problems.
IV. Action
A.
Prompt
B.
Coordinated
V. Commitment
A.
To Goal
B.
To Schedule ...
send with bid request
insist on it with responses
include delay penalty and on-time bonus
ask for evidence that they can do it
C.
To Project Management concepts ...
ask for evidence
train all
standardize on software
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
58
 2001 by Pearson Education Inc.
All rights reserved.
THE PROJECT MEETING
Critical Communication Technique !
I. KEYS
A.
CLEAR MEETING GOALS !
What do you want to accomplish in this meeting?
Be specific
B.
KEEP IT SHORT !
20 TO 45 minutes max!
Stick to the Agenda. No deviations/tangents!
II. PURPOSE: PROBLEM-SOLVING !!!!
EVERYONE LEAVES IN AGREEMENT AND WITH NEW ISSUE OF SCHEDULE
SHOWING PROJECT BACK ON TRACK!
III. FREQUENCY
A.
Regular Time and Place ...
(frequency depends on type & length of project.)
B.
At major Checkpoints/events.
C
To Resolve Major Problem.
IV. ATTENDANCE
A.
Only those absolutely essential to the agenda.
B.
Decision makers and Doers only; no reps!
in emergencies, delegate only to project manager.
C.
Inside participants; examples...
functional managers
engineers
accountant
D.
Outside participants; examples...
vendors
sub-contractors
consultants
attorney
architect
E.
Serious consequences for missing project meeting
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
59
 2001 by Pearson Education Inc.
All rights reserved.
V. PREPARATION
A.
By Project Manager;
Define horizon, sub-tasks, and functional areas.
Update schedule
Contingencies for “delegating” members
B.
By Members;
Current status of their activities
Projected completion times.
Cost status: amount spent, balance required to completion
Major needs and recommendations.
VI. FORMAT
A.
Agenda to each member ahead of time.
attach relevant time-scaled network
B.
Stick to Agenda; ... keep it absolutely short and snappy.
START EXACTLY ON TIME with whoever is present!
Insist on everyone being prepared.
Table non-agenda issues for another meeting
Side issues related to agenda need to be resolved off-line! Nail down
who will resolve and by when and add to action items.
C.
Get Updates first;
C.P. activities first.
in order of due date.
then by functional member for activities with float.
show on time-scaled network on overhead
D.
Then get into solutions;
hottest problems first ... on C.P. with soonest due date.
get a clear definition of technical problem.
get specific commitment from decision maker ...
...specific finish date
...specific incremental cost
get reconciliation with schedule ...
...commitments from all affected activities
move on to next hottest problem.
non-C.P. problems need not be resolved in meeting ...
... no technical discussion
... get commitment for acceptable finish or
… resolution date and follow up.
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
60
 2001 by Pearson Education Inc.
All rights reserved.
E.
Document;
record and assign action items only.
print and handout action list at meeting.
have scheduler at hand ...
... live schedule update
... live impact on Finish date & Total cost
... reflect solutions on schedule
... print and hand out updated schedule at meeting!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
61
 2001 by Pearson Education Inc.
All rights reserved.
CONTINUOUS CONTROL TECHNIQUES
Project Meeting is only one part of the control process!!
I. KEY
Preventive Action
A.
If Project Manager waits for problems to be raised/reported,
IT WILL BE TOO LATE!
Consider The following ...Types of team members ...
Ostriches ... discover after failing ... too late
Optimists ... give up too late
Machos ... will die trying; ask for help too late
Timids ... wait till it is too obvious ... too late
B.
Find Potential Problems;
IF IT CAN GO WRONG, IT MOST LIKELY WILL!!.....Murphy.
Listen to people
Walking around
Snap a string
Read your CC messages
Reinforce accountability for raising them by members
Ask, ask, ask ...
C.
Resolve problems on the spot;
At the source
Ask: Where is the extra time coming from ?
Where is the extra cost coming from ?
immediate tête-à-tête’s
Raise red flag to all concerned
Quick mini meetings
Involve technical expert
Involve concerned/affected managers
Negotiate the trade-offs
Close the loop
Keep a running schedule daily
Supply all concerned with the new schedule!!!
D.
Keep the commitment alive ...
Stay focused on the Goal!
Remind everyone often
Differentiate what is important from what is urgent.
Uphold the priorities vehemently!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
62
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT CONTROL II
PROJECT REPORT FORMAT
Date:__________________
Red Flag Items:
Action
Due
Usually None. Say “NONE”!!
This is reserved for still unresolved disasters.
Short and sweet. One sentence each. Describe the cause & result.
Refer to memos, reports, meetings, announcements or proposed solutions.
Be sure to name the decision maker for action.
Be sure to state drop-dead date for action!
Status Summary:
Date issued
Estimated Project Completion Date
Gain (slippage) since last report
Estimated Project Total Cost
Variance since last report; fav./(unfav.)
Original Plan Completion Date: ____________
Original Plan Total Cost: ____________
Significant Occurrences:
LAST REPORT THIS REPORT
____________
____________ ____________
____________
____________ ____________
____________
1.
The good things as well as the bad things.
2.
Recoveries on previous Red Flag Items.
3.
Outstanding performance by specific members.
4.
Bad performance by specific members.
Near Term Schedule/Milestones:
Depends on how high the report will go.
Resources
Activity
Responsible
Assigned
Scheduled
Start
Compl.
Short and sweet. No politics!
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
63
 2001 by Pearson Education Inc.
All rights reserved.
PROJECT COST CONTROL
Key: Design your cost control system to highlight anticipated problems!
Allocation Categories:
1.
By work category ... unknown, unpredictable or incompetent specialists.
2.
By recourse type ... inefficient manager’s area.
3.
By contract ... exceptional or bad contractors.
4.
By final function ... a particular module may be way off budget.
5.
By activity and overhead ... high content of negotiating between activities.
Lifecycle of Project Costs:
EVENT
Sign contract
Notice to proceed
Execution of work
Receipt of payment request (invoice)
Issue payment
COST LEVEL
Contracted cost
Committed cost
Earned value
Invoiced cost
Incurred cost
Accountants track Invoiced and Incurred costs and report them too late for project
managers.
Project managers track committed and earned costs in order to stay in control.
GOOD PROJECT MANAGERS KEEP THIER OWN BOOKS!
TOTAL EST. COST = COST TO-DATE + EST. COST TO COMPLETE
R. G. Ghattas and Sandra McKee
Practical Project Management
First Edition
64
 2001 by Pearson Education Inc.
All rights reserved.