Professional Documents
Culture Documents
Basic Concepts
Basic Concepts
Basic Concepts
Basic Concepts
1
Opermgt 345 Shannon January, 2001
What is a Project?
2
Opermgt 345 Shannon January, 2001
Typical Project Structure
Project
Definition
Project
Monitoring
Project
Planning
Project Project
Implementation Evaluation
Project
Adjustment 3
Opermgt 345 Shannon January, 2001
Resources and Effort Project Life Cycle
Time Cost
Constraints
Performance
6
Opermgt 345 Shannon January, 2001
Triple Constraint Trade-offs
$
Budget Better
Performance
Worse Specifications
8
Opermgt 345 Shannon January, 2001
Project Definition
9
Opermgt 345 Shannon January, 2001
Form Project Team
•Select Project Leader
•Identify Key People (TEAM)
10
Opermgt 345 Shannon January, 2001
Project Manager
11
Opermgt 345 Shannon January, 2001
Project Manager Skills
• Scheduling and time mgt. skills
• Technical skills ( scope of project )
• Leadership skills ( goals, performance measures)
• Resource mgt., human relationship skills.
• Communication skills
• Negotiation skills
• Marketing, Contracting, customer relationship skills
• Budgeting and cost skills.
12
Opermgt 345 Shannon January, 2001
Major Interactions of project stakeholders
13
Opermgt 345 Shannon January, 2001
Project Manager Responsibilities
1. Responsibility to the parent Org.
2. Responsibility to the project and client
3. Responsibility to the member of the
project team
14
Opermgt 345 Shannon January, 2001
Selecting Project Manager
List of some of the most popular attributes:
15
Opermgt 345 Shannon January, 2001
Selecting the PM
• Credibility
– Technical credibility ( technical knowledge )
– Administrative credibility ( managing resources( money, people,
material) keeping the project on scheule.
• Sensitivity
– It is related to the ability of the manager to discover the problems
at early stages and solve the team’s problems if we have some
conflects
• Leadership and management style
– Leadership is defined as the ability of affecting others in away
that gurantees the project profitability to the org. and sociey.
• Ability to work under stress
16
Opermgt 345 Shannon January, 2001
Project Planning
18
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Objectives:
– More detailed statement of general goals noted
on the overview section.
– The statement should include profit and
competitive aims as well as technical goals.
• General approach:
– Describes both the managerial ( style of mgt. )
and the technical approaches ( required
equipments, technology ) to the work.
19
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Contractual aspects: ( list for )
– All reporting requirements
– Customer-supplied resources.
– Advisory commitees
– Project review
– Cancellation procedures.
– Specific management agreements
– subcontracts
20
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Schedules:
– Various schedules.
– Lists all milestones events.
– All tasks, and their durations…..
• Resources:
– The budget
– Both capital and expense requirements are detailed
by task. ( Project budget )
– Cost monitoring and control procedures.
21
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Personnel :
– Expected personnel requirements
– Special skills needed
– Types of training needed
– Possible recruiting problems.
– Legal and political restrictions.
22
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Evaluation Methods:
– Every project should be evaluated against
standards and by methods established at the
project inception.
– This section include :
• A brief description of the procedure to be followed
in monitoring , collecting, storing, and evaluating
the history of the project.
23
Opermgt 345 Shannon January, 2001
Project plan Elements:
• Potential problems:
– External and internal potential problems.
24
Opermgt 345 Shannon January, 2001
Work-Breakdown- Structure (WBS)
25
Opermgt 345 Shannon January, 2001
Work-Breakdown- Structure (WBS)
• We have 2 types of
WBS:
– Managerial level
– Technical level
26
Opermgt 345 Shannon January, 2001
Earned Value Analysis
• It is a continuous comparison between the
plan of the project data and the actual data.
Budgeted and Committed Cost:
Variance = Budgeted cost – committed cost
Variance (+ve ) = Unconsumed Cost
Variance ( -ve ) = Over spend activities
27
Opermgt 345 Shannon January, 2001
Cost and Schedule Variances
28
Opermgt 345 Shannon January, 2001
Cost and Schedule Variances
29
Opermgt 345 Shannon January, 2001
BCWS
Budgeted Cost of Work Schedule
A B C D E F G H I J
X1 X2 X3 X4 X5 X6 X7 X8 X9 X1
0
NOW
BCWS = X1 + X2 + X3 + X4 + X5 $
This is the sum of all the costs up to the specific activity that is
stated in budget plan.
30
Opermgt 345 Shannon January, 2001
BCWP
Budgeted Cost of Work Performed
A B C D E
100% 100% 100% 80% 50%
X1 X2 X3 X4 X5
BCWP = X1 + X2 + X3 + 0.8 X4 + 0.5 X5 $
This is the sum of all the costs up to the specific activity in
relation with its completion percentage.
31
Opermgt 345 Shannon January, 2001
ACWP
Actual Cost of Work Performed
ACWP = Actual cost of work done.
This is the total costs of the work done on reality provided by
project manager on the financial monitor.
32
Opermgt 345 Shannon January, 2001
33
Opermgt 345 Shannon January, 2001
• If BCWP > BCWS ( over spend )
• If BCWP < BCWS ( time is late -ve )
• If BCWP > BCWS
( +ve time is more than sufficient )
34
Opermgt 345 Shannon January, 2001
35
Opermgt 345 Shannon January, 2001
Forecasting
• It is the process of prediction of the future
events.
• Benefits of forecasting:
1. To estimate the cost of remaining parts
of a project ( forecasted value ).
2. To identify the source and places of
certain problems in the budget plan.
3. It is a tool for corrective actions.
36
Opermgt 345 Shannon January, 2001
Forecasting
Mathematical Expressions
• The Cost Performance Index ( CPI ):
CPI = BCWP / ACWP
• It gives a good indication whether the
project is performing financially well or
not.
• CPI > 1 : Good performance.
• CPI < 1 : Bad performance ( shortages
• Overspend ).
37
Opermgt 345 Shannon January, 2001
Forecasting
Mathematical Expressions
• The Schedule Performance Index ( SPI ):
SPI = BCWP / BCWS
• It is a good indicator for the project
timing.
• SPI > 1 : Good performance.
• SPI < 1 : Bad performance (Poor ).
38
Opermgt 345 Shannon January, 2001
Forecasting
Mathematical Expressions
• Budgeting Cost to Completion ( BCC ):
• The Amount of money needed to
completion.
• BCC = BAC – BCWP
• It is defined as the amount of money
required to complete a project where it is
partially completed ( remaining money ).
39
Opermgt 345 Shannon January, 2001
Forecasting
Mathematical Expressions
• Estimated Cost to Completion ( ECC ):
• Its more realistic value than budgeted.
• ECC = BCC / CPI
• It depends on CPI which is a by product of
the actual cost of work performed.
• Forecasted Cost to Completion ( FCC ):
• FCC = ACWP + ECC
40
Opermgt 345 Shannon January, 2001
41
Opermgt 345 Shannon January, 2001
Example
• The R&D department of a company has
been developing a new product line, the
project manager is concerned whether the
following provided data is exhibiting a
good project performance, calculate the
following and comment on the project
status to convince the project manager.
1. CPI,BCC, ECC, SPI, FCC.
42
Opermgt 345 Shannon January, 2001
Work Budgeted Cost Completion Actual % Complete
Package Time month Cost
45
Opermgt 345 Shannon January, 2001
Comments
• We do not have any financial problem i.e the
budgeted cost (money resources) is larger
than the forecasted values, we conclude that
the money is available , it is more than
sufficient as the indicators were positive, the
only problem we have is the time.
46
Opermgt 345 Shannon January, 2001
Comparing Projects
Project SPI CPI
A 0.78 (2) 0.68 (2)
B 0.96 (1) 0.98 (1)
C 0.46 (3) 0.51 (4)
D 0.46 (4) 0.64 (3)
47
Opermgt 345 Shannon January, 2001
Problem : Compare between the following projects
according to the time and cost consumed:
Project A Project B
WP budget actual %comp WP budget actual %comp
d 570 - D 700 -- --
48
Opermgt 345 Shannon January, 2001
Scheduling
• Scheduling : is the process of converting a project
action plan into an operating time table.
• Why scheduling ? To answer the following questions:
– If each activity goes according to plan , then when will the
project be completed?
– Which tasks are most critical to ensure the timely completion
of the project?
– Which tasks can be delayed , if necessary , without delaying
project completion and by how much?
– More specifically , at what times should each activity begin
and end?
– At any given time during the project, how much money
should have been spent?
– Is it worthwhile to incur extra costs to accelerate some of the
activities? If so, then which ones?
49
Opermgt 345 Shannon January, 2001
Network Techniques
• PERT
• CPM
• PERT/CPM is based on a diagram that
represents the entire project as a network of
arrows and nodes.
• Two most popular approaches are :
– AOA : activity on arrow ( PERT )
– AON : activity on node ( CPM )
50
Opermgt 345 Shannon January, 2001
Project Representation
• A network is a form of project
representation schemes that use arrows and
nodes to represent activities and their
relationships.
»A
1 5
» 3 days
51
Opermgt 345 Shannon January, 2001
Rules for constructing a network
1. Arrow represents the activity
2. Circles represents time event ( start, finish)
3. Any activity can be represented by one arrow only
4. All activities having no predecessor should start at
the same “start node” of the network.
5. All activities having no successors should finish in
one “finish node” in the network.
6. Two nodes can only represent one activity
52
Opermgt 345 Shannon January, 2001
Notes for constructing a network
53
Opermgt 345 Shannon January, 2001
Forward Path Calculation
• Early Start ( ES )
• Early Finish ( EF )
• The earliest possible start time of an
activity leaving a node equals the
maximum of the early finish time of all
activities entering that node
• EF = ES + duration
54
Opermgt 345 Shannon January, 2001
Backward Path Calculation
• Late Finish ( LF )
• Late Start ( LS )
• The latest possible finish time of an
activity entering a node equals the
minimum of the late start time of all
activities leaving that node
• LS = LF - duration
55
Opermgt 345 Shannon January, 2001
4 questions must be answered to
begin modeling process:
• What are the major project activities?
• What are the sequencing requirements or
constraints for these activities?
• Which activities can be conducted
simultaneously?
• What are the estimated time requirements
for each activity?
56
Opermgt 345 Shannon January, 2001
Estimating the duration of project
activities
• The length of each activity should be
approximately in the range 0.5% to 2% of
the length of the project.( 1 year -> between
a day and week)
• If the number of activities is very large
( above 250 ) then the project should be
divided into subprojects.
57
Opermgt 345 Shannon January, 2001
Two approaches are used for estimating the
length of an activity
• Deterministic approach
– Past data
– If not exist :
• Modular approach
• Benchmark job technique approach
• Parametric technique ( cause-effect analysis , reg. analysis )
• Stochastic approach
– Expected time estimation for an activity depends on:
– a: Optimistic time : which will be required if execution goes
extremely well
– m:most likely time, which will be required if execution is normal
– b: pessimistic time , which will be required if everything goes
badly.
– Et(A) = ( a + 4 m + b ) / 6
58
Opermgt 345 Shannon January, 2001
Difference Between PERT and CPM
59
Opermgt 345 Shannon January, 2001
The Top Level Project Tasks
Brainstorm
the
Major Tasks
C
B G
Establish
A
Work Flow
D E F
60
Opermgt 345 Shannon January, 2001
Define Top Level Tasks
Canoe Example
Site Preparation
Build Dock
Build Building
61
Opermgt 345 Shannon January, 2001
Sequence Top Level Tasks
Build Dock
Build Building
62
Opermgt 345 Shannon January, 2001
Detailed
Sub-Tasks
Tasks
C
G
B
D E F
Frame
Landscape
Building Site Build Dock
Roof
Assemble
Power
Canoes
Paint
64
Opermgt 345 Shannon January, 2001
Work Breakdown Structure
3rd Level 3rd Level 3rd Level 3rd Level 3rd Level
Task Task Task Task Task
65
Opermgt 345 Shannon January, 2001 Lower Level Tasks
Sequence Sub-Tasks
Task Description Immediate Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
C Install Dock Pilings A
D Foundation for Hut B
E Build Dock C
F Frame Hut D
G Power to Hut D
H Side the Hut F
I Roof the Hut F
J Order Canoes and Receive Canoes -
K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
N Open for Business M
66
Opermgt 345 Shannon January, 2001
Build Network Diagram
(PERT Chart)
(Activities on Arrows)
Task Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
C Install Dock Pilings A
D Foundation for Hut B
E Build Dock C
F Frame Hut D
G Power to Hut D
H Side the Hut F
I Roof the Hut F
J Order Canoes and Receive Canes -
K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
N Open for Business M
67
Opermgt 345 Shannon January, 2001
Build Network Diagram
(PERT Chart)
A
1 3
Prep Dock
Site
Task Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
C Install Dock Pilings A
D Foundation for Hut B
E Build Dock C
F Frame Hut D
G Power to Hut D
H Side the Hut F
I Roof the Hut F
J Order Canoes and Receive Canes -
K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
N Open for Business M
68
Opermgt 345 Shannon January, 2001
Build Network Diagram
(PERT Chart)
2
J o es
C an
r der
O
A
1 3
Prep Dock
Site
Task Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
C Install Dock Pilings A
D Foundation for Hut B
E Build Dock C
F Frame Hut D
G Power to Hut D
H Side the Hut F
I Roof the Hut F
J Order Canoes and Receive Canes -
K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
N Open for Business M
69
Opermgt 345 Shannon January, 2001
Build Network Diagram
(PERT Chart)
2
J o es
C an
r der
O
A
1 3
Prep Dock
Site
B Task Predecessor
Prep te
Hut S
J o es
C an
r der
O
A C E
1 3 5 9
Prep Dock Install Pilings Build Dock
Site
B Task Predecessor
Prep te
Hut S
J o es
C an
r der
O
A C E
1 3 5 9
Prep Dock Install Pilings Build Dock
Site
B Task Predecessor
Prep te
Hut S
B Task Predecessor
Prep te
Hut S
B Task Predecessor
Prep te
Hut S
of
P o
4
Ro
E Build Dock C
D I F Frame Hut D
G Power to Hut D
H Side the Hut F
Hut F I Roof the Hut F
Foundation 6 7 J Order Canoes and Receive Canes -
Frame Hut K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
N Open for Business M
74
Opermgt 345 Shannon January, 2001
Task Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
B
Prep te
Hut S
t
G o Hu
are
rT
i
we Paint
of
P o K
4
Ro
D I Hut
Hut F H
Foundation 6 7 8
Frame Hut Side Hut
75
Opermgt 345 Shannon January, 2001
Task Predecessor
Diagram
E Build Dock C
F Frame Hut D
G Power to Hut D
H Side the Hut F
(PERT Chart)
I Roof the Hut F
J Order Canoes and Receive Canes -
2 K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
Ass L
oe s
N Open for Business M
J em
Can ble
r Ca
de noe
Or s
A C E M N
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B
Prep te
Hut S
G H ut
o
are
rT
i
we Paint
of
P o K
4
Ro
D I Hut
Hut F H
Foundation 6 7 8
Frame Hut Side Hut
76
Opermgt 345 Shannon January, 2001
Build Network Diagram Task Description Time
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
77
Opermgt 345 Shannon January, 2001
Build Network
Task Predecessor
A Prepare Dock Site -
B Prepare Hut Site -
C Install Dock Pilings A
(PERT Chart)
H Side the Hut F
I Roof the Hut F
J Order Canoes and Receive Canes -
2 K Paint Hut H
L Assemble Canoes J
M Finish Landscaping L,I,K,E,G
Ass L
oe s
N Open for Business M
J em
Can ble
r Ca
de noe
Or s
A C E M N
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B
Prep te
Hut S
G H ut
o
are
rT
i
we Paint
of
P o K
4
Ro
D I Hut
Hut F H
Foundation 6 7 8
Frame Hut Side Hut
78
Opermgt 345 Shannon January, 2001
Build Network Diagram Task Description Time
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
79
Opermgt 345 Shannon January, 2001
Determining Project Length
Sum = 52 days
Anything wrong with this approach?
80
Opermgt 345 Shannon January, 2001
Determining Project Length
81
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram
A-C-E-M-N = 19 days
Project Paths
2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
82
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram
A-C-E-M-N = 19 days
B-D-F-H-K-M-N = 22 days Project Paths
2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
83
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram
A-C-E-M-N
B-D-F-H-K-M-N
= 19 days
= 22 days Project Paths
B-D-F-I-M-N = 18 days
2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
84
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram
A-C-E-M-N
B-D-F-H-K-M-N
= 19 days
= 22 days Project Paths
B-D-F-J-M-N = 18 days
B-D-G-M-N = 15 days
2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
85
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram
A-C-E-M-N
B-D-F-H-K-M-N
= 19 days
= 22 days Project Paths
B-D-F-J-M-N = 18 days
B-D-G-M-N = 15 days
J-L-M-N = 18 days 2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
J (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
86
Opermgt 345 Shannon January, 2001
Critical Path
87
Opermgt 345 Shannon January, 2001
Paths:
Network Diagram Canoe Example
A-C-E-M-N = 19 days
B-D-F-H-K-M-N = 22 days
Critical Path
B-D-F-J-M-N = 18 days
B-D-G-M-N = 15 days
J-L-M-N = 18 days
2
Ass L (10)
J (2)
n oes e mb
a le C
de rC ano
Or es
A (3) C (6) E (4) M (4) N (2)
1 3 5 9 10 11
Prep Dock Install Pilings Build Dock Finish Open for
Site Landscape Business
B (4)
Prep te
Hut S
t
G (2) o Hu
are
rT
i
we Paint
of
P o
4
Ro
I (2) K (4) Hut
D (3)
Hut F (3) H (2)
Foundation 6 7 8
Frame Hut Side Hut
88
Opermgt 345 Shannon January, 2001
Completed
Task Timetable
Task Description Immediate Predecessor Time ES LS EF LF
89
Opermgt 345 Shannon January, 2001
Slack Time
91
Opermgt 345 Shannon January, 2001
Critical Path Tasks
92
Opermgt 345 Shannon January, 2001
Critical Path Tasks
Task Description Immediate Predecessor Time ES LS EF LF Slack
Critical Path = B - D - F - H - K - M - N
93
Opermgt 345 Shannon January, 2001
CPM ( A-O-N) : Example
CPM network for computer Design Project:
B D E
4 2 5
95
Opermgt 345 Shannon January, 2001
Determine the Critical path
• Forward pass:
– ES : the earliest possible time the activity can
begin.
– EF : the early start time the time needed to
complete the activity. ( EF = ES + Dur )
Backwards pass
96
Opermgt 345 Shannon January, 2001