Professional Documents
Culture Documents
CH 08
CH 08
Scheduling
6-1
Outline
• Introduction
• Advantages of scheduling
• Scheduling techniques
• PERT and CPM
• Terminologies
• AOA vs AON
• Constructing networks
• Precedence relationships
• Calculating time for activities
• Solving network
• Uncertainty
• Simulation
6-2
Introduction
Schedule is the conversion of a project action plan (WBS) into an operating
timetable
Scheduling is one of the major project management tools
Basis for monitoring a project
8-3
Introduction
The advantages and benefits of the network scheduling
technique
Consistent framework
Shows interdependences
8-4
Network Techniques: PERT and CPM
The most common techniques to use are In CPM, projects can be expedited by
the Critical Path Method (CPM), and the crashing activity times.
Program Evaluation and Review Both can identify the project’s critical
Technique (PERT) path with activities that cannot be
Both techniques were developed almost delayed and activities with a float or
at the same time. slack that can be delayed without
PERT is oriented to the time element of affecting project duration.
the project and used probability estimates Microsoft Project (and others) have
to determine if a project could be blended CPM and PERT into one approach
completed at a given time.
CPM used deterministic time estimates
and is used to control the time and cost
aspects of the project
8-5
Network Techniques: PERT and CPM
Terminology
Activity - A specific task or set of tasks that are required by the project, use up resources and take time to
complete
Event - The result of completing one or more activities. An identifiable end state that occurs at a particular
time. Events use no resources.
Network - The combination of all activities and events that define a project
Critical - An activity, event, or path which, if delayed, will delay the completion of the project
Critical Path - The path through the project where, if any activity is delayed, the project is delayed
Predecessor - That activity that must be completed just before a particular activity can begin
Successor - Activity following a specific activity
8-6
Network Techniques: PERT and CPM
Terminology
An activity can be either in any of these
conditions, starting activity, an ending
activity, or in between. See Fig. 8-1
When there are multiple activities with
no predecessors they are shown
emanating from a single starting node
“START”. Similarly, when multiple
activities have no successors, they are
connected to an ending node “END”.
Fig 8-2
Figure 8-2 Activity network, AON format
8-7
Network Techniques: PERT and CPM
Terminology
There are two formats to use in
building a network
Activity on Node (AON): where
activities are placed within nodes Figure 8-2 Activity network, AON format
Activity on Arrow (AOA) where
activities are placed on arrows
Throughout this chapter we follow the
AON format, nevertheless, AOA will
be illustrated.
Figure 8-3 Activity network, AOA format
8-8
Network Techniques: PERT and CPM
Terminology
All the information we need is
contained in the WBS.
The WBS shows a list of all
activities, the time for each
activity, resources that will be
used, and the successor–
predecessor relationships between
activities. For example, see
Figure 8-4
8-9
Constructing the Network, AON Version & AOA
With the WBS (Fig 8-4),
Begin with the START activity. Activity a
and b have no predecessors, so we draw
arrows out of START to each (AON), or
arrows labeled a and b from the START to
nodes 2, and 3 (AOA). (Figure 8-5 a and b) Figure 8-5
Sample of a
Activity c follows a, and activities d and e network
follow b. Now activity f follows both c construction
and d. (see Fig. 8-6 a)
For AOA, we draw arrows labeled c, d,
and e following activities a, and b. (see
Fig. 8-6 b)
8-10
Constructing the Network, AON Version & AOA
The WBS does not indicate any further
activity is required to complete the task,
so we have reached the End of the plan.
We thus draw arrows from activities e
and f to the node END, as shown in
Figure 8-7a.
For AOA, we should have both c and d
terminate at the same node such that
activity f is preceded by both. Finally,
activities e and f are connected to node
5 (the END). Figure 8-7b
8-11
Constructing the Network, AON Version & AOA
In our example, a and b
Generally, AON is much simpler and they would appear to be the
same, both starting at node
are used in most popular computer 1 and ending at node 2.
software.
AOA are sometimes harder to draw as they Activities a, b, and c
must precede activity d,
require the use of dummy activities. but only a and b
must precede activity e.
Dummy activities have zero duration and
use no resources. Its sole purpose is to
indicate the technological relationships.
Figure 8-10 illustrates the
Figures 8-10,8-9, and 8-10 shows instances use of dummy activities in a
at which the dummy activity is needed, and more complex setting
8-12
Gantt (Bar) Charts
It is one of the most useful methods of presenting
project schedule information
It was developed around 1917 by Henry L. Gantt, a
pioneer in the field of scientific management.
Shows planned and actual progress
Easy-to-read method to know the current status
Advantages
Easily understood
Disadvantage
Difficult to follow complex projects
8-13
Gantt (Bar) Charts
Another advantage is that Gantt charts are easily
constructed as a network
Figure 8-12 shows the previous example to
construct such a chart.
8-14
Solving the network
8-15
Calculating Activity Times
8-16
Critical Path and Time
Consider again the project shown in Fig. 8-15. For convenience, assume
the time is in days. The first figure is the expected time, and the second
figure is the variance. How long will it take to complete the project?
First we need to determine the ES-EF schedule, where
ES: is the earliest starting time of activity and it can be determined to be
equal to the latest early finish (EF) time leading to that activity. The ES
value is shown on the top left of the activity node.
EF: the earliest finish time of an activity and is always equal to the ES
time + activity duration and is shown at the top right.
Moving from left to right, and starting at time zero, we assign the values
of the ES-EF at the top of each node.
Note activities Start and END have no durations, therefore their ES=EF.
After adding the ES-EF times to the network, we can see that the project
should end within 43 days
The critical path is the longest path from START to END and is easy to
see that it passes over a-d-j
8-17
Slacks or Floats
Next, we need to estimate the Latest start (LS) –latest finish
(LF) schedule by moving from the END node to the START
node.
LF is the latest finish time of an activity and it should equal
to the lowest late start time for all activities preceding it.
Typically it is shown at the lower right side of the activity
node
LS is the latest starting time of activity and it should equal
to LF-activity duration. And it is shown at the lower left side
of the activity node.
Moving from the END node, we see that LF time for
activities I, and J should be 43 days in order to delay the
project further.
Moving further till all the LS and LF times are assigned. We
see that The START node typically has to start at time zero.
8-18
Slacks or Floats
The slack of an activity can be determined
through
Slack = LF-EF or
Slack = LS-ES
It is clear that all critical path activities have
zero slacks, i.e. their ES =EF and LS=LF
Table 8-3 summarizes the slack values for all
activities in Figure 8-16
Critical path activities cannot be delayed
without making the project late.
Activities that have a slack can be delayed
without impacting the project duration
8-19
Precedence Diagramming Restrictions
The 4 types of logical relationships in the precedence diagramming method are:
Finish start: an activity cannot start before a previous activity has ended. This is the most
commonly used dependency.
Start to start: the predecessor activity must have started before the successor activity can
start.
Finish to finish: a successor activity requires the predecessor activity to be finished
before it can be completed.
Start to finish: This logical relationship requires
8-20
Precedence Diagramming Restrictions
Activity 2 would be scheduled to start at least two days after
the completion of Activity 1. for example: pouring of concrete
sidewalk.
Activity 5 cannot begin until Activity 4 has been underway
for at least two days. Example: setting electrical wires cannot
begin until two days after framing has begun.
Activity 7 must be completed at least one day before Activity
8 is completed. For example: if activity 7 is priming the walls
of a house, activity 8 could be selecting, purchasing, and
delivering the wallpaper. It is important that wallpapers are
hung after the primer has dried by 24 hours
Activity 11 cannot be completed before 7 days after the start
of Activity 10. if activities 10 and 11 are two major cruising
activities in a pre-paid week-long vacation. The total time
cannot exceed the promised week
Class practice
8-22
Class practice (cont.)
Activity a m b Expected
1 8 10 13 10.2
2 5 6 8 6.2
3 13 15 21 15.7
4 10 12 14 12.0
5 11 20 30 20.2
6 4 5 8 5.3
7 2 3 4 3.0
8 4 6 10 6.3
9 2 3 4 3.0
8-23
Uncertainty of Project Completion Time
Assume activities are statistically independent
Variance of a set of activities is the sum of the
individual variances.
Recall our earlier example, the critical path is
a-d-j. the variances of these activities are 4, 25,
and 4 respectively. Therefore, the variance of
the critical path is 4+25+4=33 days.
Assume that the PM has promised to
complete the project in 50 days. What is the
chance of meeting this deadline?
8-25
Uncertainty of Project Completion Time
8-26
Uncertainty of Project Completion Time
8-27
Uncertainty of Project Completion Time
8-28
Toward Realistic Time Estimates
8-29
Toward Realistic Time Estimates
8-30
Risk Analysis Using Simulation with Crystal Ball
8-31
Risk Analysis Using Simulation with Crystal Ball
8-33
Risk Analysis Using Simulation with Crystal Ball
8-34
Risk Analysis Using Simulation with Crystal Ball
Simulation can provide more information about the
project completion time
Figures 8-30, and 8-31 provide statistical
information about the distribution shown in Fig. 8-
28
The mean of the completion time is 47.8 days and
the median is 47.6 days.
Recall that the expected completion time over the
critical path was 43 days.
The difference between the two means is due to
possible path mergers. The probability of path
mergers is not possible to account for through
regular spreadsheets. But it can be handled easily
through simulation
8-35
Final note: Projects are dynamic
8-36