Project Management

© 2006
© 2006 Prentice
Prentice Hall, Inc. Hall, Inc. 3–1
 Project Characteristics

 Single unit
 Many related activities
 Difficult production planning and
inventory control
 General purpose equipment
 High labor skills

© 2006 Prentice Hall, Inc. 3–2

 Examples of Projects
 Building Construction

 Research Project

© 2006 Prentice Hall, Inc. 3–3

 Project Organization
Works Best When
 Work can be defined with a specific
goal and deadline
 The job is unique or somewhat
unfamiliar to the existing organization
 The work contains complex interrelated
tasks requiring specialized skills
 The project is temporary but critical to
the organization

© 2006 Prentice Hall, Inc. 3–4

 Management of Projects
 Planning - goal setting, defining the
project, team organization
 Scheduling - relates people, money,
and supplies to specific activities
and activities to each other
 Controlling - monitors resources,
costs, quality, and budgets; revises
plans and shifts resources to meet
time and cost demands
© 2006 Prentice Hall, Inc. 3–5
 Project Management
Activities
 Planning
 Scheduling
 Objectives
 Project activities
 Resources
 Start & end times
 Work break-down
schedule  Network
 Organization

 Controlling
 Monitor, compare, revise, action
© 2006 Prentice Hall, Inc. 3–6
 Project Planning,
Scheduling, and Controlling

Figure 3.1

Before Start of project During

project Timeline project
© 2006 Prentice Hall, Inc. 3–7
 Project Planning,
Scheduling, and Controlling

Figure 3.1

Before Start of project During

project Timeline project
© 2006 Prentice Hall, Inc. 3–8
 Project Planning,
Scheduling, and Controlling

Figure 3.1

Before Start of project During

project Timeline project
© 2006 Prentice Hall, Inc. 3–9
 Project Planning,
Scheduling, and Controlling

Figure 3.1

Before Start of project During

project Timeline project
© 2006 Prentice Hall, Inc. 3 – 10
 Project Time/cost
Planning,
Budgets
estimates

Scheduling, and Controlling

Engineering diagrams
Cash flow charts
Material availability details

Budgets
Delayed activities report
Slack activities report

CPM/PERT
Gantt charts
Milestone charts
Cash flow schedules

Figure 3.1

Before Start of project During

project Timeline project
© 2006 Prentice Hall, Inc. 3 – 11
 Project Planning
 Establishing objectives
 Defining project
 Creating work
breakdown structure
 Determining
resources
 Forming organization

© 2006 Prentice Hall, Inc. 3 – 12

 Project Organization
 Often temporary structure
 Uses specialists from entire company
 Headed by project manager
 Coordinates activities
 Monitors schedule
and costs
 Permanent
structure called
‘matrix organization’

© 2006 Prentice Hall, Inc. 3 – 13

 A Sample Project
Organization
President

Human Quality
Resources Marketing Finance Design Production
Mgt

Project 1 Project
Manager
Mechanical Test
Technician
Engineer Engineer

Project 2 Project
Manager
Electrical Computer
Technician
Engineer Engineer
Figure 3.2

© 2006 Prentice Hall, Inc. 3 – 14

 Matrix Organization
Marketing Operations Engineering Finance

Project 1

Project 2

Project 3

Project 4

© 2006 Prentice Hall, Inc. 3 – 15

 The Role of
the Project Manager
Highly visible
Responsible for making sure that:

 All necessary activities are finished in order

and on time
 The project comes in within budget
 The project meets quality goals
 The people assigned to the project receive
motivation, direction, and information

© 2006 Prentice Hall, Inc. 3 – 16

 The Role of
the Project Manager
Highly visible
Responsible for making sure
Project that: should be:
managers
 Good coaches
 All necessary activities are finished in order
and on time  Good communicators
 The project comesin Able to organize
within budget activities
from a variety of disciplines
 The project meets quality goals
 The people assigned to the project receive
motivation, direction, and information

© 2006 Prentice Hall, Inc. 3 – 17

 Work Breakdown Structure
Level
1. Project
2. Major tasks in the project
3. Subtasks in the major tasks
4. Activities (or work packages)
to be completed

© 2006 Prentice Hall, Inc. 3 – 18

 Project Life Cycle:
Time Distribution of Project Effort
• Conception
• Selection
• Planning,
scheduling,
monitoring, control
• Evolution and
termination

© 2006 Prentice Hall, Inc. 3 – 19

 Work Breakdown Structure
Level ID
Level Number Activity
1 1.0 Develop/launch Windows Longhorn OS
2 1.1 Development of GUIs
2 1.2 Ensure compatibility with earlier
Windows versions
3 1.21 Compatibility with Windows ME
3 1.22 Compatibility with Windows XP
3 1.23 Compatibility with Windows 2000
4 1.231 Ability to import files

Figure 3.3

© 2006 Prentice Hall, Inc. 3 – 20

 Project Scheduling
 Identifying precedence
relationships
 Sequencing activities
 Determining activity times & costs
 Estimating material and worker
requirements
 Determining critical activities

© 2006 Prentice Hall, Inc. 3 – 21

 Purposes of Project
Scheduling
1. Shows the relationship of each activity to
others and to the whole project
2. Identifies the precedence relationships
among activities
3. Encourages the setting of realistic time
and cost estimates for each activity
4. Helps make better use of people, money,
and material resources by identifying
critical bottlenecks in the project
© 2006 Prentice Hall, Inc. 3 – 22
 Project Management
Techniques
 Gantt chart
 Critical Path Method
(CPM)
 Program Evaluation
and Review
Technique (PERT)

© 2006 Prentice Hall, Inc. 3 – 23

 A Simple Gantt Chart

Time
J F M A M J J A S

Design
Prototype
Test
Revise
Production

© 2006 Prentice Hall, Inc. 3 – 24

 Service For A Delta Jet
Deplaning
Passengers
Baggage claim
Baggage Container offload
Pumping
Fueling
Engine injection water
Cargo and mail Container offload
Main cabin door
Galley servicing
Aft cabin door
Lavatory servicing Aft, center, forward
Drinking water Loading
First-class section
Cabin cleaning
Economy section
Cargo and mail Container/bulk loading
Galley/cabin check
Flight services
Receive passengers
Operating crew Aircraft check
Baggage Loading
Passengers Boarding
0 15 30 45 60
Figure 3.4 Minutes
© 2006 Prentice Hall, Inc. 3 – 25
 Project Control Reports
 Detailed cost breakdowns for each task
 Total program labor curves
 Cost distribution tables
 Functional cost and hour summaries
 Raw materials and expenditure forecasts
 Variance reports
 Time analysis reports
 Work status reports

© 2006 Prentice Hall, Inc. 3 – 26

 PERT and CPM
 Network techniques
 Developed in 1950’s
 CPM by DuPont for chemical plants (1957)
 PERT by Booz, Allen & Hamilton with the
U.S. Navy, for Polaris missile (1958)
 Consider precedence relationships and
interdependencies
 Each uses a different estimate of
activity times

© 2006 Prentice Hall, Inc. 3 – 27

 Six Steps PERT & CPM

1. Define the project and prepare the

work breakdown structure
2. Develop relationships among the
activities - decide which activities
must precede and which must follow
others
3. Draw the network connecting all of
the activities

© 2006 Prentice Hall, Inc. 3 – 28

 Six Steps PERT & CPM

4. Assign time and/or cost estimates

to each activity
5. Compute the longest time path
through the network – this is called
the critical path
6. Use the network to help plan,
schedule, monitor, and control the
project

© 2006 Prentice Hall, Inc. 3 – 29

 Questions PERT & CPM
Can Answer
1. When will the entire project be
completed?
2. What are the critical activities or tasks in
the project?
3. Which are the noncritical activities?
4. What is the probability the project will be
completed by a specific date?

© 2006 Prentice Hall, Inc. 3 – 30

 Questions PERT & CPM
Can Answer
5. Is the project on schedule, behind
schedule, or ahead of schedule?
6. Is the money spent equal to, less than, or
greater than the budget?
7. Are there enough resources available to
finish the project on time?
8. If the project must be finished in a shorter
time, what is the way to accomplish this
at least cost?

© 2006 Prentice Hall, Inc. 3 – 31

 A Comparison of AON and
AOA Network Conventions
Activity on Activity Activity on
Node (AON) Meaning Arrow (AOA)
A comes before
(a) A B C B, which comes
before C A B C
A A
A and B must both
(b) C be completed
before C can start C
B B
B
B and C cannot
(c) A begin until A is B
completed A
Figure 3.5
C C
© 2006 Prentice Hall, Inc. 3 – 32
 A Comparison of AON and
AOA Network Conventions
Activity on Activity Activity on
Node (AON) Meaning Arrow (AOA)

C and D cannot
A C begin until A A C
(d) and B have
both been
B D completed B D

C cannot begin
until both A and B
A C are completed; D A C
(e) cannot begin until Dummy activity
B is completed. A
B D dummy activity is
introduced in AOA B D
Figure 3.5
© 2006 Prentice Hall, Inc. 3 – 33
 A Comparison of AON and
AOA Network Conventions
Activity on Activity Activity on
Node (AON) Meaning Arrow (AOA)

B and C cannot
begin until A is
completed. D
A B D cannot begin A B D
until both B and
(f) C are completed. Dummy
A dummy activity
C
C
activity is again
introduced in
AOA.

Figure 3.5
© 2006 Prentice Hall, Inc. 3 – 34
 AON Example
Milwaukee Paper Manufacturing's
Activities and Predecessors
Immediate
Activity Description Predecessors
A Build internal components —
B Modify roof and floor —
C Construct collection stack A
D Pour concrete and install frame A, B
E Build high-temperature burner C
F Install pollution control system C
G Install air pollution device D, E
H Inspect and test F, G

Table 3.1
© 2006 Prentice Hall, Inc. 3 – 35
 AON Network for
Milwaukee Paper

Activity A
A
(Build Internal Components)

Start

Activity B
Start B (Modify Roof and Floor)
Activity

Figure 3.6
© 2006 Prentice Hall, Inc. 3 – 36
 AON Network for
Milwaukee Paper
Activity A Precedes Activity C

A C

Start

B D

Activities A and B
Precede Activity D Figure 3.7
© 2006 Prentice Hall, Inc. 3 – 37
 AON Network for
Milwaukee Paper

F
A C

E
Start H

B D G

Arrows Show Precedence

Relationships
Figure 3.8
© 2006 Prentice Hall, Inc. 3 – 38
 AOA Network for
Milwaukee Paper
C
2 4
(Construct
Stack)

H
1 Dummy 6 7
Activity (Inspect/
Test)

D
3 5
(Pour
Concrete/
Install Frame) Figure 3.9
© 2006 Prentice Hall, Inc. 3 – 39
 Determining the Project
Schedule
Perform a Critical Path Analysis
 The critical path is the longest path
through the network
 The critical path is the shortest time in
which the project can be completed
 Any delay in critical path activities
delays the project
 Critical path activities have no slack
time
© 2006 Prentice Hall, Inc. 3 – 40
 Determining the Project
Schedule
Perform a Critical Path Analysis
Activity Description Time (weeks)
A Build internal components 2
B Modify roof and floor 3
C Construct collection stack 2
D Pour concrete and install frame 4
E Build high-temperature burner 4
F Install pollution control system 3
G Install air pollution device 5
H Inspect and test 2
Total Time (weeks) 25
Table 3.2
© 2006 Prentice Hall, Inc. 3 – 41
 Determining the Project
Schedule
Perform a Critical Path Analysis
Earliest start (ES) = earliest time at which an activity can
Activity Descriptionstart, assuming all predecessors Time (weeks)
have
A Build internal components
been completed 2
EarliestBfinish (EF)
Modify roof and
= earliest floor
time at which an activity can3
C be finished
Construct collection stack 2
LatestD start (LS)
Pour=concrete
latest timeandat install
which frame
an activity can4
E start so as to not delay
Build high-temperature burnerthe completion
4
F Install time of thecontrol
pollution entire project
system 3
LatestGfinish (LF) = latest
Install time bydevice
air pollution which an activity has 5 to
be finished so as to not delay the
H Inspect and test 2
completion time of the entire project
Total Time (weeks) Table
25 3.2
© 2006 Prentice Hall, Inc. 3 – 42
 Determining the Project
Schedule
Perform a Critical Path Analysis
Activity Name
or Symbol
A Earliest
Earliest ES EF Finish
Start

Latest LS LF Latest
Start 2 Finish

Figure 3.10 Activity Duration

© 2006 Prentice Hall, Inc. 3 – 43
 Forward Pass
Begin at starting event and work forward
Earliest Start Time Rule:

 If an activity has only one immediate

predecessor, its ES equals the EF of the
predecessor
 If an activity has multiple immediate
predecessors, its ES is the maximum of
all the EF values of its predecessors

ES = Max (EF of all immediate predecessors)

© 2006 Prentice Hall, Inc. 3 – 44

 Forward Pass
Begin at starting event and work forward
Earliest Finish Time Rule:

 The earliest finish time (EF) of an activity

is the sum of its earliest start time (ES)
and its activity time

EF = ES + Activity time

© 2006 Prentice Hall, Inc. 3 – 45

 ES/EF Network for
Milwaukee Paper

ES EF = ES + Activity time
Start
0 0

© 2006 Prentice Hall, Inc. 3 – 46

 ES/EF Network for
Milwaukee Paper
EF of A =
ES ES of A + 2
of A
A
Start 0 2
0 0

© 2006 Prentice Hall, Inc. 3 – 47

 ES/EF Network for
Milwaukee Paper
A
0 2

2 EF of B =
ES ES of B + 3
0
Start
0 of B
B
0 0 3

3
© 2006 Prentice Hall, Inc. 3 – 48
 ES/EF Network for
Milwaukee Paper
A C
0 2 2 4

2 2

Start
0 0

B
0 3

© 2006 Prentice Hall, Inc. 3 – 49

 ES/EF Network for
Milwaukee Paper
A C
0 2 2 4

2 2

Start
0 0
= Max (2, 3) D
0
3 7
B
0 3

3
4
© 2006 Prentice Hall, Inc. 3 – 50
 ES/EF Network for
Milwaukee Paper
A C
0 2 2 4

2 2

Start
0 0

B D
0 3 3 7

3 4

© 2006 Prentice Hall, Inc. 3 – 51

 ES/EF Network for
Milwaukee Paper
A C F
0 2 2 4 4 7

2 2 3

Start E H
0 0 4 8 13 15

0 4 2

B D G
0 3 3 7 8 13

3 4 5
Figure 3.11

© 2006 Prentice Hall, Inc. 3 – 52

 Backward Pass
Begin with the last event and work backwards

Latest Finish Time Rule:

 If an activity is an immediate predecessor

for just a single activity, its LF equals the
LS of the activity that immediately follows it
 If an activity is an immediate predecessor
to more than one activity, its LF is the
minimum of all LS values of all activities
that immediately follow it

LF = Min (LS of all immediate following activities)

© 2006 Prentice Hall, Inc. 3 – 53

 Backward Pass
Begin with the last event and work backwards

Latest Start Time Rule:

 The latest start time (LS) of an activity is

the difference of its latest finish time (LF)
and its activity time

LS = LF – Activity time

© 2006 Prentice Hall, Inc. 3 – 54

 LS/LF Times for
Milwaukee Paper
A C F
0 2 2 4 4 7

2 2 3

Start E H
0 0 4 8 13 15
13 15
0 4 2

B D – Activity time
LS = LF G
0 3 3 7 8 13

3 4 5 LF = EF
of Project
Figure 3.12

© 2006 Prentice Hall, Inc. 3 – 55

 LS/LF Times for
Milwaukee Paper
A C F
0 2 2 4 4 7

10 13
2 2 3

Start E H
0 0
LF =4 Min(LS
8 of 13 15
following activity) 13 15
0 4 2

B D G
0 3 3 7 8 13

3 4 5

Figure 3.12

© 2006 Prentice Hall, Inc. 3 – 56

 LS/LF Times for
Milwaukee Paper
LF = Min(4, 10)

A C F
0 2 2 4 4 7

2 4 10 13
2 2 3

Start E H
0 0 4 8 13 15

4 8 13 15
0 4 2

B D G
0 3 3 7 8 13
8 13
3 4 5

Figure 3.12

© 2006 Prentice Hall, Inc. 3 – 57

 LS/LF Times for
Milwaukee Paper
A C F
0 2 2 4 4 7

0 2 2 4 10 13
2 2 3

Start E H
0 0 4 8 13 15

0 0 4 8 13 15
0 4 2

B D G
0 3 3 7 8 13
1 4 4 8 8 13
3 4 5

Figure 3.12

© 2006 Prentice Hall, Inc. 3 – 58

 Computing Slack Time
After computing the ES, EF, LS, and LF times
for all activities, compute the slack or free
time for each activity

 Slack is the length of time an activity can

be delayed without delaying the entire
project

Slack = LS – ES or Slack = LF – EF

© 2006 Prentice Hall, Inc. 3 – 59

 Computing Slack Time
Earliest Earliest Latest Latest On
Start Finish Start Finish Slack Critical
Activity ES EF LS LF LS – ES Path

A 0 2 0 2 0 Yes
B 0 3 1 4 1 No
C 2 4 2 4 0 Yes
D 3 7 4 8 1 No
E 4 8 4 8 0 Yes
F 4 7 10 13 6 No
G 8 13 8 13 0 Yes
H 13 15 13 15 0 Yes

Table 3.3

© 2006 Prentice Hall, Inc. 3 – 60

 Critical Path for
Milwaukee Paper
A C F
0 2 2 4 4 7

0 2 2 4 10 13
2 2 3

Start E H
0 0 4 8 13 15

0 0 4 8 13 15
0 4 2

B D G
0 3 3 7 8 13
1 4 4 8 8 13
3 4 5
Figure 3.13

© 2006 Prentice Hall, Inc. 3 – 61

 ES – EF Gantt Chart
for Milwaukee Paper
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

A Build internal
components
B Modify roof and floor
C Construct collection
stack
D Pour concrete and
install frame
E Build high-
temperature burner
F Install pollution
control system
G Install air pollution
device
H Inspect and test

© 2006 Prentice Hall, Inc. 3 – 62

 LS – LF Gantt Chart
for Milwaukee Paper
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

A Build internal
components
B Modify roof and floor
C Construct collection
stack
D Pour concrete and
install frame
E Build high-
temperature burner
F Install pollution
control system
G Install air pollution
device
H Inspect and test

© 2006 Prentice Hall, Inc. 3 – 63

 Variability in Activity Times

 CPM assumes we know a fixed time

estimate for each activity and there
is no variability in activity times
 PERT uses a probability distribution
for activity times to allow for
variability

© 2006 Prentice Hall, Inc. 3 – 64

 Variability in Activity Times

 Three time estimates are required

 Optimistic time (a) – if everything goes
according to plan
 Most–likely time (m) – most realistic
estimate
 Pessimistic time (b) – assuming very
unfavorable conditions

© 2006 Prentice Hall, Inc. 3 – 65

 Variability in Activity Times
Estimate follows beta distribution
Expected time:
t = (a + 4m + b)/6
Variance of times:
v = [(b – a)/6]2

© 2006 Prentice Hall, Inc. 3 – 66

 Variability in Activity Times
Estimate follows beta distribution
Expected time:
t = (a + 4m + b)/6
Variance of
Probability
1 in 100 of
oftimes:
Probability
Probability

< a occurring v = [(b − a)/6]2 of 1 in 100 of

> b occurring

Activity
Time

Optimistic Most Likely Pessimistic

Time (a) Time (m) Time (b)

© 2006 Prentice Hall, Inc. 3 – 67

 Computing Variance
Most Expected
Optimistic Likely Pessimistic Time Variance
Activity a m b t = (a + 4m + b)/6 [(b – a)/6]2

A 1 2 3 2 .11
B 2 3 4 3 .11
C 1 2 3 2 .11
D 2 4 6 4 .44
E 1 4 7 4 1.00
F 1 2 9 3 1.78
G 3 4 11 5 1.78
H 1 2 3 2 .11

Table 3.4

© 2006 Prentice Hall, Inc. 3 – 68

 Probability of Project
Completion
Project variance is computed by
summing the variances of critical
activities
sp2 = Project variance
= (variances of activities
on critical path)

© 2006 Prentice Hall, Inc. 3 – 69

 Probability of Project
Completion
Project variance is computed by
summing the variances of critical
Project variance
activities
sp2 = .11 + .11 + 1.00 + 1.78 + .11 = 3.11

Project standard deviation

sp = Project variance
= 3.11 = 1.76 weeks

© 2006 Prentice Hall, Inc. 3 – 70

 Probability of Project
Completion
PERT makes two more assumptions:

 Total project completion times follow a

normal probability distribution
 Activity times are statistically
independent

© 2006 Prentice Hall, Inc. 3 – 71

 Probability of Project
Completion
Standard deviation = 1.76 weeks

15 Weeks
(Expected Completion Time)
Figure 3.15

© 2006 Prentice Hall, Inc. 3 – 72

 Probability of Project
Completion
What is the probability this project can
be completed on or before the 16 week
deadline?

Z = due – expected date /sp

date of completion
= (16 wks – 15 wks)/1.76

= 0.57 Where Z is the number of

standard deviations the due
date lies from the mean

© 2006 Prentice Hall, Inc. 3 – 73

 Probability of Project
Completion
From Appendix I
What is the probability
.00 .01 this project
.07 can
.08
be completed on or before the
.1 .50000 .50399
16 week
.52790 .53188
deadline?.2 .53983 .54380 .56749 .57142

.5 = due .69497
Z.69146 − expected.71566
date /s
.71904
p
date of completion
.6 .72575 .72907 .74857 .75175
= (16 wks − 15 wks)/1.76

= 0.57 Where Z is the number of

standard deviations the due
date lies from the mean

© 2006 Prentice Hall, Inc. 3 – 74

 Probability of Project
Completion

0.57 Standard deviations

Probability
(T ≤ 16 weeks)
is 71.57%

15 16 Time
Weeks Weeks
Figure 3.16

© 2006 Prentice Hall, Inc. 3 – 75

 Determining Project
Completion Time

Probability
of 0.99

Probability
of 0.01

2.33 Standard Z
From Appendix I deviations
0 2.33
Figure 3.17

© 2006 Prentice Hall, Inc. 3 – 76