Project mANAGEMENT
Project mANAGEMENT
Project mANAGEMENT
Chapter 8
Scheduling
CHAPTER OVERVIEW
8.1 Background – Per the text, “A schedule is the conversion of a project action plan into
an operating timetable.” A schedule is important because each project is unique in its
own way. The basic process is to identify all tasks and sequential relationships
between them, that is, which tasks must precede or succeed others. There are a
number of benefits to the creation and use of these networks. Some of them are as
follows:
It is a consistent framework for planning, scheduling, and controlling the
project.
It can be used to determine a start and end date for every project task.
It identifies so-called critical activities that, if delayed will delay the project
completion.
8.2 Network Techniques: PERT and CPM – PERT and CPM are the most commonly
used approaches to project scheduling. Both were introduced in the 1950s. PERT
has been primarily associated with R&D projects, while CPM with construction
projects. Today PERT is not used much since project management software
generates CPM style networks. The primary difference between them is that PERT
uses probabilistic techniques to determine task durations, while CPM relies on a
single duration estimate for each task. Both techniques identify the critical path
(tasks that cannot be delayed without delaying the project) and associated float or
slack in the schedule. In 2005 the Project Management Institute (PMI) deemed it
necessary to change the names of these techniques. According to PMI, PERT is
called ADM/PERT (Arrow Diagram Method) and CPM is PDM/CPM (Precedence
Diagramming Method).
Terminology – Following are the key terms associated with the development
and use of networks:
o Activity – A specific task or set of tasks that have a start and end, and
consume resources.
o Event – The result of completing one or more activities. Events don’t
use resources.
o Network – The arrangement of all activities and events in their logical
sequence represented by arcs and nodes.
o Path – The series of connected activities between any two events in a
network.
o Solving the Network – The text illustrates the development and solving an
AON network based on the project detailed in Table 8-1.
o Calculating Activity Times – The sample project in the text has three
duration estimates for each activity: optimistic (a), most likely (m) and
pessimistic (b). Optimistic and pessimistic are defined as the durations
that represent 99 percent certainty. In other words the actual duration of
an activity will be less than the optimistic or greater than the pessimistic
only one percent of the time. Then, the expected time (TE) is found with
the formula:
TE = (a + 4m + b)/6
where:
a = optimistic time estimate
b = pessimistic time estimate
m = most likely time estimate, the mode
This formula is based on the beta statistical distribution. In spite of
a flurry of discussion in the 1980s the assumptions used to derive
this formula have stood the test of time. Along with TE, the
variance of the durations can be calculated as:
2 2
σ =( ( b−a ) /6 )
and the standard deviation as:
2
σ= √ σ
o Critical Path and Time – Using the example network, the text describes
the concept of the critical path. For simple projects, the critical path can
be found by determining the longest path through the network.
o Slack (aka, Float) – In the previous section, the earliest possible dates for
each activity were determined. By starting the analysis at the end of the
network and working through it backwards, the latest possible dates for
each activity can be determined. The difference between the early dates
and the late dates is float or slack. Activities on the critical path have zero
float.
o Precedence Diagramming – The Precedence Diagram Method allows for
additional relationships to be established between activities. They are:
Finish to Start – The successor activity cannot begin until the
predecessor finishes. This is the most common relationship
depicted in networks.
Start to Start – The successor activity cannot begin until the
predecessor begins.
Finish to Finish – The successor activity cannot finish until the
predecessor activity finishes.
Start to Finish – The successor activity cannot finish until the
predecessor activity starts. This relationship is rarely used.
Z =( D− μ ) / √σ μ
where:
D = the desired project completion time
µ = the critical time of the project, the sum of the TEs for activities
on the critical path
2
8.3 Risk Analysis Using Simulation With Crystal Ball® – Tools like Crystal Ball® can be
used to model the project and determine the likelihood of completion within a certain
time. Since Crystal Ball® works with Microsoft® Excel, the project network must be
modeled in the spreadsheet. This involves creating cells that calculate the early and
late dates for each activity. Then a distribution (commonly triangular) with the
appropriate parameters can be assigned to each duration. Finally, Crystal Ball® runs
its simulation and the results are displayed.
Incorporating Costs into the Simulation Analysis – The uncertainty related to
projects is better understood when considering both time and cost issues.
Traditional Statistics or Simulation? – With the advent of inexpensive and easy to
use tools, simulation is the recommended way to model uncertainty in project
durations. Both methods require the development of three durations for each
activity. The simulation method, however, does a much better job of handling the
possibility that the critical path will shift due to variation in durations of activities.
This issue can be analyzed with traditional statistics, but it takes considerable
manual effort on the part of an analyst.
8.4 Using These Tools – The text gives an example of the use of the tools on a specific
project.
TEACHING TIPS
The authors correctly applaud the advent of many user-friendly and powerful project
management tools available for PCs. They have performed a great service by integrating
the use of tools like Microsoft® Project into the subject matter. My experience in teaching
these tools, however, reminds me of the story about IBM’s new programming language.
The story goes that IBM, in their marketing campaign for their new language, said that
the language was so easy to use that it would virtually eliminate the position of a
programmer. Anybody would be able to use this language to easily create computer
programs. The punch line is that the new language was FORTRAN, a 1960’s era
product long ago supplanted by other “user-friendly” products. Even today, with all the
marvelous tools we have available, the position of a programmer has not disappeared.
The point of all this is that in the classroom students will have a wide range of skills and
abilities that may or may not be applicable to Microsoft® Project and similar tools. My
experience is that it is unreasonable to expect students to pick up MSP and use it
successfully based solely on the printed examples in the text. Unfortunately, even
students who claim to be experienced in the use of the tool often know how to draw a
Gantt chart and little else. This is due to three reasons:
MSP on the surface may look like a fancy spreadsheet, but “under the
hood” it’s is a very complex tool. Many of its processes are dependent on
complex algorithms, controlled by a seemingly endless series of settings with
mysterious titles.
The training provided by most organizations ranges between non-existent
and abominable. If there is training, it’s usually administered by someone who
has never managed a project and doesn’t understand much more than the
student he/she is teaching. One of my very computer literate colleagues will
probably become homicidal, if he is forced to go to yet another training session
that concentrates on issues vital to the PM like changing the color of the fonts. In
The opportunity then, for any project management instructor, is to provide both the
concept and meaningful tools training in one package. Ideally, lectures on concept
should be alternated with lab sessions using the tool. If this is not possible then, at a
minimum, the instructor must set aside class time to demonstrate the key elements of
MSP needed to complete the homework problems. Then, a week later, be prepared for
the questions and frustrations that will erupt from the class.
Question 1:Define activity, event, and path as used in network construction. What
is a dummy activity?
Activity: Activities have a start and end,and consume resources.
Event:An event can be thought of as the result of completing one or more activities or as
an identifiable end state that occurs at a particular time. Events do not consume
resources. Typically, events designate the start or the completion of an activity or a path
Path: A path traces the predecessor-successor relationships that exist among a set of
interconnected activities and events. The boundaries of a path use a starting event and
a completion event to designate the path’s endpoints.
Dummy Activity: Dummy activities are tasks of zero duration that have no resources
assigned to them. They are used to maintain predecessor/successor relationships in
AOA networks.
Question 2:What characteristic of the critical path times makes them critical?
Activities along the critical path cannot be delayed without delaying the completion of the
project.
Question3:What two factors are compared by Gantt charting? How does the Gantt
chart differ in purpose from the WBS?
Gantt Chart:The Gantt chart compares planned and actual progress for the detailed
tasks in a project.
Master Schedule: The Gantt chart format (bars to represent progress over time) may be
used to display data regarding the master project schedule, but the master schedule is
oriented towards overall management of the project and will only focus on the major
project tasks. For example, the Gantt view in MS-Project can be filtered to only show
summary tasks at a particular level of the WBS hierarchy.
Question 9: Define “late start time,” “early start time,” and “early finish time.”
Late start time: Given the precedence relationships in a network, this is the latest time
that an activity can begin without extending the time required to complete the entire
project.
Early start time: Given the precedence relationships in a network, this is the earliest time
that an activity can begin. In order to begin, all predecessor constraints must have been
satisfied.
Early finish time: Given the precedence relationships in a network and the activities
duration, this is the earliest time that an activity can be completed if all predecessor
constraints are satisfied.
Slack is important for two reasons: 1) Slack tells us that we can be a bit more forgiving
about delays on paths with slack, whereas our primary attention should be focused on
the critical path. 2) If we need additional resources for some reason (such as a delay on
the critical path), the first place to look is at the resources on paths with slack in case
they might be available for use.
Question 12:How do you think the approach of developing 3-time estimates for a
task’s duration could be used to estimate costs for manufacturing?
With a three-time estimate for a task’s duration, the pessimistic, optimistic, and most
likely time estimates are calculated. This is an expression of the risk associated with the
tasks. This could be useful in estimating costs for manufacturing by helping to determine
a more accurate time estimate for manufacturing, which would then relate to the
manufacturing cost. Similar to time estimates utilizing three estimates, costs can be
estimated using pessimistic, optimistic, and most likely. This would provide the same
benefits as seen with the time estimates.
Question 13:What are some benefits of the network approach to project planning?
What are some drawbacks?
1) Benefits:
a) Illustrates task interdependencies
b) Establishes the sequence of activities (precedence)
c) Highlights critical and near-critical paths and their tasks
d) Highlights activities that contain float
2) Disadvantages:
a) It can possibly emphasize time at the expense of other dimensions of
project success
b) Large networks are difficult to print in a convenient format and they may
require significant wall space to view the entire network
c) As the network technique becomes more complex, its effectiveness as a
control tool is reduced
Question 14:What is your position on the statements in the Using These Tools
section?
This is a good question to kick off a lively class discussion. There are no black and white
answers to this question, but here are a couple thoughts:
It’s easy to become obsessed by the use of even more sophisticated tools and
lose sight of the big picture. Project management tools are only useful if they help
projects achieve their cost, schedule, and scope goals. Just because a tool is
more sophisticated doesn’t mean that it will yield a better result for the business.
Organizations have to clearly articulate the goals of a project, put together some
kind of a plan, and then meticulously monitor its execution. Many organizations
gloss over the monitoring part because they believe it smacks of micro-
management. In spite of what Dilbert thinks, managers must have a mechanism
for knowing where their project is every day. This allows corrective action to be
taken before the problem grows beyond recovery. This attention to detail is
boring and repetitive, but it’s far more fundamental to the success of the project
than the sophistication of the simulation tools used to model the plan.
PROBLEMS
NOTE: Many of the AON graphics in this solutions set depict the start day of the
successor activity to be the same day as the completion of the predecessor. This is
consistent with the presentation in the text. It is not consistent with the result that would
be obtained using Microsoft® Project, where the start day of the successor is always the
next working day after the completion of the predecessor.
F
B
A C H
E
D G
1) The arrows cannot form a loop such as the one shown between nodes 2,
3, and 5.
2) The dummy arrow between nodes 6 and 7 is not required because 6
precedes 5 and 5 precedes 7.
3) Nodes 8 and 9 do not have successors, so it appears that this network
has two final termination nodes. This is not a conventional diagramming
technique. An arrow from 8 should point to 9.
Problem 5:Convert the AOA diagram in Problem 4 to an AON diagram. How would
the AON diagram change if there had been a dummy from node 2 to node 3 in
Problem 4?
The diagram would change because now A and B precede E.
Problem 6:Convert each of the following AOA diagrams into AON diagrams.
PDM Diagram 6a
PDM Diagram 6b
Problem 7:Given the following activities and precedences, draw an AOA or AON
diagram:
A C F
G
Start D H End
B E
Problem 9:Given the estimated activity times below and the network in Problem 8
above,
what is the probability that the project will be completed within (based on the path
with the longest expected time):
(a) 21 days?
(b) 22 days?
(c) 25 days?
Task a m b Expected Variance Std Dev.
A 6.5 7.5 14.5 8.5 1.78 1.33
B 8.5 10.5 12.5 10.5 0.44 0.67
C 2.5 3.5 4.5 3.5 0.11 0.33
D 6.5 7.5 8.5 7.5 0.11 0.33
E 5.5 5.5 9.5 6.2 0.44 0.67
F 5.5 7.5 9.5 7.5 0.44 0.67
G 4.5 6.5 8.5 6.5 0.44 0.67
H 2.5 3.5 3.5 3.3 0.03 0.17
Sum of
Expected Variance
Desired Project s Critical
Duration Duration Path Z Probability
Problem 10:
Find
(a) The AOA network and the path with the longest expected duration.
(b) All event slacks.
(c) Critical path to event D.
(d) The probability of completing the path with the longest expected
duration in 14 days.
(e) The effect if CD slips to 6 days; to 7 days; to 8 days.
Sum of
Expecte Variance
Desired d Project s Critical
Duration Duration Path Z Probability
14 16.0 4.00 –1 15.9%
e) If CD slips to six days the critical path is unchanged, but slack on D is reduced. If
CD slips to seven days, then there are two critical paths: AC CB BE EF and AC
CD DF. If CD slips to eight days then the critical path shifts to AC CD DF and the
project duration extends to 17 days.
Problem 11:
10 28 36
B G 8 I
17 28 41
1
3 10
9
4 2
0 7 18 37 43
A 3 C 2 F 11 H 6 J
0 7 18 37 43
1
4 5
6 3
3
3 13
D 8 E
3 13
Figure 8.11 shows duration on the arrow in matching the “(i,j)” notation used to
define the problem’s source data.
b) The critical path is A, D, C, E, F, G, H, and J.
c) The completion time is 43 days.
Problem 12:The Denver Iron & Steel Company is expanding its operations to
include a new drive-in weigh station. The weigh station will be a heated/air-
conditioned building with a large floor and small office. The large room will have
the scales, a 15-foot counter, and several display cases for its equipment.
Before erection of the building, the project manager evaluated the project using
AON analysis. The activities with their corresponding times were recorded in
Table A.
Using AON analysis, find the path with the longest expected duration, the slack
times, and the expected completion time.
Figure 8.12a shows the PDM network for the data from Table A of Problem 8-12
assuming that the data were applied as shown in Figure 8.12b.
Please see note about network depiction preceding Problem 1
1)The critical path is 2,3,4,5,7,8, and 9.
2)The slack for activity 1 is 11.7 days. The slack for activity 6 is 4 days.
2) The following table shows the calculation of the expected completion time:
Expecte
Activity a m b d
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
Expecte
d Project
Duration
66.4
Problem 14:The following chart was prepared at the beginning of a HRM (Human
Resource Management) crash hiring project. The project begins with two
activities: Assemble interview team (A) and Budget resources (B).
The duration, in days, follows the letter of each activity. What is the critical path?
Which activities should be monitored most closely?
At the end of the first week, it was noted that activity A was completed in 2.5 days,
but activity B required 4.5 days. What impact does this have on the project? Are
the same activities critical?
Figure 8.14a shows the original network diagram for problem 14.
Please see note about network depiction preceding Problem 1
1) The critical path activities are A, D, G, and J. Activities B and E should be closely
monitored as a near critical path.
If the venture firm can complete the project for the customer within 18 weeks, it
will receive a bonus of $10,000. But if the project delays beyond 22 weeks, it must
pay a penalty of $5,000 due to lost opportunity. If the firm can choose whether or
not to bid on this project, what should its decision be if the project is only a
breakeven one normally?Figure 8.15a shows the network.
Expecte
Activity a m b d Variance Std Dev.
1–2 5 11 11 10.0 1.00 1.00
1–3 10 10 10 10.0 0.00 0.00
1–4 2 5 8 5.0 1.00 1.00
2–6 1 7 13 7.0 4.00 2.00
3–6 4 4 10 5.0 1.00 1.00
3–7 4 7 10 7.0 1.00 1.00
3–5 2 2 2 2.0 0.00 0.00
4–5 0 6 6 5.0 1.00 1.00
5–7 2 8 14 8.0 4.00 2.00
6–7 1 4 7 4.0 1.00 1.00
Sum of
Expecte Variance
Desired d Project s Critical
Duration Duration Path Z Probability
17 21.0 6.00 –1.63299 5.2%
18 21.0 6.00 –1.22474 11.1%
22 21.0 6.00 0.408248 65.9%
24 21.0 6.00 1.224745 88.9%
24.13 21.0 6.00 1.277817 89.8%
Management can be sure that the project will complete 90% of the time in slightly over
24 weeks.
This analysis suggests that 11% of the time the project will achieve the bonus and
34.1% (100 – 65.9) of the time the project will incur the penalty. Since the project is
expected to generate no profit or loss independent of the bonuses and penalties the
expected value calculation yields:
11% $10,000 + 34.1% (–$5,000) = –$ 605
Strictly based on the expected return management should “no bid” the project. Because
the loss is small, however, the firm may wish to apply other criteria to decide whether to
pursue the project.
find:
(a) The probability of completing the critical path in 12 weeks (or less),
as the client desires.
(b) The probability of completing the critical path in 13 weeks (or less).
(c) The probability of completing the critical path in 16 weeks (or less),
the client’s drop-dead date.
(d) The number of weeks required to assure a 92.5 percent chance of
completing the critical path, as guaranteed by the auditing firm.
Using critical path analysis with the data provided gives the following table:
Expecte
Activity d Std Dev. Variance
A 2.0 2.00 4.00
B 3.0 1.00 1.00
C 4.0 0.00 0.00
D 2.0 3.00 9.00
E 1.0 1.00 1.00
F 6.0 2.00 4.00
G 4.0 2.00 4.00
H 2.0 0.00 0.00
Variances
d Project Critical
Duration Duration Path y
12 13.0 9.00 –0.33 37.1%
13 13.0 9.00 0.00 50.0%
16 13.0 9.00 1.00 84.1%
17.3 13.0 9.00 1.44 92.5%
For this problem, the variance has to be calculated from the standard deviation, and the
durations provided are assumed to be expected durations. As can be seen there is
about an 84% chance of completing the project within the drop dead time. If a little more
than a week is added to the duration, the chance of completing the project on time rises
to 92.5%.
Note that four activities, the biological elements, can start immediately.
Find:
(a) The critical path.
(b) The earliest time to complete the project.
(c) The slack on activities E, F, and H.
Problem 18:The events of the project below are designated as 1, 2, and so on.
(a) Draw the network.
(b) Find the critical path.
(c) Find the slacks on all the activities.
C, F, H is the critical path as indicated in the network. The slack times are as indicated
for all activities.
Problem 20:Given the schedule in Table B for a liability work package done as part
of an accounting audit in a corporation, find:
(a) The critical path.
(b) The slack time on “process confirmations.”
(c) The slack time on “test pension plan.”
(d) The slack time on “verify debt restriction compliance.”
Problem 21:In the website development project network shown in the following
figure, the number alongside each activity designates the activity duration (TE) in
weeks.
Determine:
(a) The ES and LS for each activity.
(b) The earliest time that the website can be completed.
(c) The slack on all activities.
(d) The critical activities.
(e) The critical path.
2 0 5 5 7 9
0 0 2 D H
A 2 3 5 5 0 13 12 4 16
0 2 2 I
2 6 7
5 8 13
E
0 9 4 8 5 13 13 1 15
16
Start B J End
16
9 4 13 3 4 9 14 2 16
F
13 0 16
7 6 13
0 4 3 L
C 3 6 7 13 3 16
4 3 7 G
Legend for Solution
9 4 13 Early Early
Slack
Start Finish
Problem 23:Construct a network for the aerospace launch project below and find
its critical path.
Figure 8.23 shows the network diagram solution for problem 23.
The critical path is A, B, F, H, and I as indicated above.
Please see note about network depiction preceding Problem 1
Problem 25:Resolve part (d) of Problem 10 assuming the values of a and b are
given at the 95 percent level. Repeat, assuming the values are given at the 90
percent level.
Following the discussion in the text, the calculations of TE and σ need to be
modified.For a confidence level of 95%, the calculation for variance would be:
' ' 2
2
σ =( ( b −a ) /3. 29 )
Using these values, the following table can be calculated:
95% Confidence Level
Task a m b Expected Variance Std Dev.
AB 3 6 9 6.0 3.33 1.82
AC 1 4 7 4.0 3.33 1.82
CB 0 3 6 3.0 3.33 1.82
CD 3 3 3 3.0 0.00 0.00
CE 2 2 8 3.0 3.33 1.82
BD 0 0 6 1.0 3.33 1.82
BE 2 5 8 5.0 3.33 1.82
DF 4 4 10 5.0 3.33 1.82
DE 1 1 1 1.0 0.00 0.00
EF 1 4 7 4.0 3.33 1.82
Sum of
Expected Variances
Desired Project Critical
Duration Duration Path Z Probability
14 16.0 13.32 -0.55 29.1%
Note that the expected durations for the critical path remain unchanged, however, the
variances are quite a bit larger indicating that there is a larger chance that any given
duration will fall outside of the optimistic/pessimistic limit. Similarly for the 90%
confidence level, the following equations would be used:
' ' 2
2
σ =( ( b −a ) /2.56 )
and the following table can be calculated:
90% Confidence Level
Task a M b Expected Variance Std Dev.
AB 3 6 9 6.0 5.49 2.34
AC 1 4 7 4.0 5.49 2.34
CB 0 3 6 3.0 5.49 2.34
CD 3 3 3 3.0 0.00 0.00
CE 2 2 8 3.0 5.49 2.34
BD 0 0 6 1.0 5.49 2.34
BE 2 5 8 5.0 5.49 2.34
DF 4 4 10 5.0 5.49 2.34
DE 1 1 1 1.0 0.00 0.00
EF 1 4 7 4.0 5.49 2.34
Sum of
Expected Variances
Desired Project Critical
Duration Duration Path Z Probability
14 16.0 21.96 -0.43 33.4%
Problem 26:Using the information below, draw an AOA network. Find the path with
the longest expected duration and use it to compute the number of days you
would be 95 percent sure the project would be completed. Calculate the slack,
earliest start, and latest start times for each activity and show in table form. Does
any path come close to causing a problem in determining the probability of
project completion based on just using the path with the longest expected
duration?
Figure 8.26a shows the network, critical path and slack times.
The critical path in the above diagram is 1-4, 4-5, 5-6, 6-7, 7-10, 10-11 with a duration of
59 days.
Tabulating the calculations for expected durations and probability looks like this:
Expecte
Task a m b d Variance Std Dev.
1-2 6 8 10 8 0.44 0.67
1-3 5 6 7 6 0.11 0.33
1-4 6 6 6 6 0.00 0.00
2-6 0 0 0 0 0.00 0.00
2-7 10 11 12 11 0.11 0.33
3-6 12 14 16 14 0.44 0.67
4-5 5 8 11 8 1.00 1.00
4-9 7 9 11 9 0.44 0.67
5-6 8 10 12 10 0.44 0.67
5-9 0 0 0 0 0.00 0.00
6-7 14 15 16 15 0.11 0.33
6-8 10 12 14 12 0.44 0.67
7-10 9 12 15 12 1.00 1.00
8-10 0 4 14 5 5.44 2.33
9-11 5 5 5 5 0.00 0.00
10-11 7 8 9 8 0.11 0.33
Expected Sum of
Desired Project Variances Probabilit
Duration Duration Critical Path Z y
61.69 59.0 2.66 1.65 95.0%
The next longest path is 1-3, 3-6, 6-7, 7-10, 10-11 at 55 days. It will only be a concern if
under some circumstances; its duration exceeds the actual critical path of 59 days.
Using the same technique for calculating the probability of exceeding a particular
duration gives the following table for this path:
Probability for path 1-3-6-7-10-11
Expected Sum of
Desired Path Path
Duration Duration Variances Z Probability
59 55.0 1.77 3.00 99.9%
Clearly the chance of exceeding 59 days is quite small. The same technique can be
applied to the next longest path 1-4, 4-5, 5-6, 6-8, 8-10, 10-11 which while relatively
short has high variance:
Probability for path 1-4-5-6-8-10-11
Expected Sum of
Desired Path Path
Duration Duration Variances Z Probability
59 49.0 7.1 3.8 100.0%
Again it is clear that it is unlikely that this path will cause problems with the overall
project duration.
Problem 27:Given the following activities required for staging a community play
on Independence Day,
(a) Construct an AON diagram.
(b) Determine the earliest expected completion time for the play.
(c) Based on the path with the longest expected duration, what completion
date are you 80% confident of achieving? 40% confident?
(d) Will a 1-day delay in this project be serious?
The critical path in the above figure is 1, 4, 6, 8, 12, 15 with a duration of 52 days.
Please see note about network depiction preceding Problem 1
b) See Figure 8.27a for the critical path and its early completion time.
Expected Sum of
Desired Project Variances Probabilit
Duration Duration Critical Path Z y
53.35 52.0 2.54 0.85 80.1%
51.6 52.0 2.54 -0.26 40.1%
d) Since the play is supporting an Independence Day event, a one day delay would be
severe.
Problem 28:Draw an AON network using the following data and find the
probability of completing the path with the longest expected duration of the in 44
days, the official opening date.
Figure 28a shows the PDM network diagram for problem 28.
The critical path in the figure above is 1, 3, and 6 with a duration of 41 days.
The following table tabulates the variances and probability for this project:
Task a m b Expected Variance Std Dev.
1 6 10 14 10 1.78 1.33
2 0 1 2 1 0.11 0.33
3 16 20 30 21 5.44 2.33
4 3 5 7 5 0.44 0.67
5 2 3 4 3 0.11 0.33
6 7 10 13 10 1.00 1.00
7 1 2 3 2 0.11 0.33
8 0 2 4 2 0.44 0.67
9 2 2 2 2 0.00 0.00
10 2 3 4 3 0.11 0.33
11 0 1 2 1 0.11 0.33
12 1 2 3 2 0.11 0.33
Sum of
Expecte Variances
Desired d Project Critical Probabilit
Duration Duration Path Z y
44 41.0 8.22 1.05 85.3%
The path durations are calculated by summing the expected duration of each
Paths Project
1-5-10-13-15 1-4-9-13-15 1-4-6-8-12-15 2-6-8-12-15 2-3-8-12-15 2-3-7-11 2-3-7-14 Completion
46.0 50.0 52.0 43.0 44.0 37.0 34.0 52.0
Then a forecast cell is setup for the Project Completion to view how it changes due to
the simulation. The resulting histogram looks like this:
By adjusting the sliders on the histogram, the 80% and 40% confidence levels can be
checked. They look like this:
These graphs show that a 54-day duration can be achieved with an 80% confidence
level and a 52-day duration with a 40% confidence level. These are slightly worse than
the results calculated with the variance method. The reason is that the simulation
properly takes into account the possibility that the critical path shifts for some possible
combinations of activity durations.
Paths Project
1-2-4-5 1-2-4-7-8-11-12 1-2-4-7-9-10-12 1-3-9-10-12 1-3-6 Completion
19 23 25 39 42 42
Then, similar to problem 29, triangle distributions are established to calculate the
durations for all activities except 9 (no variation in the estimate).
The resulting forecast for the duration of the project and corresponding statistics are:
Note that the probability of completing the project in 44 days has dropped to about 70%.
Problem 31:In the following table are listed tasks, duration in weeks, and
predecessors.
Dec '05 Jan '06 Feb '06 Mar '06 Apr '06
ID Task Name Duration Start Finish 4 11 18 25 1 8 15 22 29 5 12 19 26 5 12 19 26 2 9
1 Start 0 days Sun 12/11/05 Sun 12/11/05 12/11
2 a 2 wks Mon 12/12/05 Fri 12/23/05
3 b 2 wks Mon 12/12/05 Fri 12/23/05
4 c 4 wks Mon 12/26/05 Fri 1/20/06
5 d 3 wks Mon 1/23/06 Fri 2/10/06
6 e 1 wk Mon 1/23/06 Fri 1/27/06
7 f 2 wks Mon 2/13/06 Fri 2/24/06
8 g 3 wks Mon 2/27/06 Fri 3/17/06
9 h 1 wk Mon 3/20/06 Fri 3/24/06
10 End 0 days Fri 3/24/06 Fri 3/24/06 3/24
The figure shows the default Gantt chart view of the problem, with a project start day of
Sunday December 11, 2005. Note that MSP moves the beginning of the first task to the
first workday of Monday the 12th. This display shows the default calendar of 5 day 40 hr.
weeks with no holidays. A “Start” and “End” milestone have been inserted to insure that
all activities have at least one predecessor and successor.
The default “Tracking Gantt” view can be used to display the critical path:
Dec '05 Jan '06 Feb '06 Mar '06 Apr '06
ID Task Name Duration Start 4 11 18 25 1 8 15 22 29 5 12 19 26 5 12 19 26 2 9
1 Start 0 days Sun 12/11/05 12/11
2 a 2 wks Mon 12/12/05 0%
3 b 2 wks Mon 12/12/05 0%
4 c 4 wks Mon 12/26/05 0%
5 d 3 wks Mon 1/23/06 0%
6 e 1 wk Mon 1/23/06 0%
7 f 2 wks Mon 2/13/06 0%
8 g 3 wks Mon 2/27/06 0%
9 h 1 wk Mon 3/20/06 0%
10 End 0 days Fri 3/24/06 3/24
The project duration (in workdays) can be displayed in the “Project” >> “Project
Information” >> “Project Statistics” window, which looks like this:
Problem 32:In the following table, project activities in days are listed with three
time estimates for duration in days and predecessors for the activities.
Using the calculated durations, the Gantt chart looks like this:
Dec '05 Jan '06 Feb '06
ID Task Name Duration Start Finish Predecessors 4 11 18 25 1 8 15 22 29 5 12 19 26
1 Start 0 days Sun 12/11/05 Sun 12/11/05 12/11
2 a 7.5 days Mon 12/12/05 Wed 12/21/05 1
3 b 8 days Mon 12/12/05 Wed 12/21/05 1
4 c 6 days Wed 12/21/05 Thu 12/29/05 2
5 d 14.5 days Thu 12/22/05 Wed 1/11/06 2,3
6 e 7 days Wed 1/11/06 Fri 1/20/06 4,5
7 f 11.5 days Fri 1/20/06 Mon 2/6/06 3,6
8 g 8 days Tue 2/7/06 Thu 2/16/06 7
9 End 0 days Thu 2/16/06 Thu 2/16/06 8 2/16
The figure shows the default Gantt chart view of the problem, with a project start day of
Sunday December 11, 2005. Note that MSP moves the beginning of the first task to the
first workday of Monday the 12th. This display shows the default calendar of 5 day 40 hr.
weeks with no holidays. A “Start” and “End” milestone have been inserted to ensure that
all activities have at least one predecessor and successor.
The tracking Gantt view can be used to display the critical path:
Dec '05 Jan '06 Feb '06
ID Task Name Duration 4 11 18 25 1 8 15 22 29 5 12 19 26
1 Start 0 days 12/11
2 a 7.5 days 0%
3 b 8 days 0%
4 c 6 days 0%
5 d 14.5 days 0%
6 e 7 days 0%
7 f 11.5 days 0%
8 g 8 days 0%
9 End 0 days 2/16
The network diagram can be displayed directly from MSP using the “Network Diagram”
view. A portion of it with the default format settings looks like this:
a
Start
Start: 12/12/05 ID: 2
Milestone Date: Sun 12/11/05 Finish: 12/21/05 Dur: 7.5 days
ID: 1 Res:
b
Start: 12/12/05 ID: 3
Finish: 12/21/05 Dur: 8 days
Res:
The slack values are automatically calculated by MSP. They can be revealed in a
number of different views:
Nov '05 Dec '05 Jan '06 Feb '06 Mar '06 Apr '06
ID Task Name Start Finish Late Start Late Finish Free Slack Total Slack 27 4 11 18 25 1 8 15 22 29 5 12 19 26 5 12 19 26 2 9 16 23
1 Start Sun 12/11/05 Sun 12/11/05 Mon 12/12/05 Mon 12/12/05 0 days 0 days
2 a Mon 12/12/05 Wed 12/21/05 Mon 12/12/05 Wed 12/21/05 0 days 0.5 days
3 b Mon 12/12/05 Wed 12/21/05 Mon 12/12/05 Wed 12/21/05 0 days 0 days
4 c Wed 12/21/05 Thu 12/29/05 Tue 1/3/06 Wed 1/11/06 9 days 9 days 9 days
5 d Thu 12/22/05 Wed 1/11/06 Thu 12/22/05 Wed 1/11/06 0 days 0 days
6 e Wed 1/11/06 Fri 1/20/06 Wed 1/11/06 Fri 1/20/06 0 days 0 days
7 f Fri 1/20/06 Mon 2/6/06 Fri 1/20/06 Mon 2/6/06 0 days 0 days
8 g Tue 2/7/06 Thu 2/16/06 Tue 2/7/06 Thu 2/16/06 0 days 0 days
9 End Thu 2/16/06 Thu 2/16/06 Thu 2/16/06 Thu 2/16/06 0 days 0 days
This view shows the View “Detail Gantt” combined with the “Schedule” Table. Note that
the Gantt chart also displays the slack as a green line.
Questions: Will Gort’s approach work? How much more of a gamble is Gort taking
than any project manager normally takes? What should Gort watch out for?
This incident is a good opportunity to engage the students in a discussion of what’s
important in the planning and scheduling process. The spirit of the case is to not do
dumb things like apply scheduling techniques that aren’t understood by the users.
Gort’s approach won’t work, because he doesn’t understand the scheduling process that
he intends to apply.The sophistication of the technique is not the issue. If he doesn’t use
PERT he can still come up with a useable schedule with any one of several techniques.
The issue is that as the PM he needs to understand why the schedule comes out the
way it does. He should be able to explain the schedule to others. He needs to be able to
understand the implications of uncertain data, and he needs to be able to understand the
impact of a reschedule. If he is using a scheduling technique that he doesn’t understand,
then he won’t be able to perform any of these important management tasks.
Cincinnati Software
Question: If you were the project manager, which method would you use, and
why?
This incident, like the previous one, is an excellent opportunity to engage the students in
a discussion of what’s really important in the project management process. I have seen
discussions similar to this incident take place many times in business situations. The
flavor of the discussion is, “What’s the latest technology and how much can we apply to
this project?” The real question should be, “Which technology is appropriate for the goal
we are trying to achieve?” In business we fall prey to the fallacy that the sophistication of
the technology will make up for our lack of planning and discipline. As the text has
discussed the keys to a good planning and scheduling process are:
Solid understanding of senior management’s and the customer’s goals in
pursuing the project
A complete listing of all the activities and products the project must accomplish
A schedule that provides a start and complete date for each identified task
A budget for each task
A clear understanding of the outcome of each task
A system for monitoring the progress of each task
A process for identifying and managing change to the project scope
Note that the schedule is only one element, and as the text has explained, there are
several ways to get there. I will take a project that has every one of these in place, but
creates the schedule on a white board over a project that uses other methods, but has
no clear idea of what the customer’s expectations are.
That being said the options look like this:
I would reject the Gantt chart as being too simplistic for the large plan and
schedule that will have to be maintained for a project as complicated as an ERP
system.
I would work with the PERT and CPM camps to reach a compromise and use
the best of both worlds. That would be a CPM based network using PERT for
estimating durations.
As can be seen, the project would end on 14 Jan 11 well before the penalty would be
due. This date will be used as the baseline for all subsequent analysis.
The next step is to understand the impact on the schedule of the shutdown announced
by the utility company. For the first scenario eight weeks of non-working time was added
to the calendar between 29 Nov 10 and 21 Jan 11. The new schedule looks like this:
Note that now the completion date is delayed until 7 Apr 11. This causes the following
additional costs to be incurred:
Overhead costs: 12 weeks at ¥3,000/week = ¥36,000
Penalty costs: 8 weeks at ¥100,000/week = ¥800,000
Total: ¥836,000
Next, the expected value of each possible outcome is calculated. The four possible
scenarios are:
What happens if there is an 8 week shutdown?
What happens if there is a 12 week shutdown?
What happens if there is no shutdown and the weather in December is cold?
PROPOSAL No No Expected
5 - DO Expected stoppage, stoppage, value with Overall
NOTHING Planned 8 week 12 week value with cold warm no expected
value stoppage stoppage stoppage December December stoppage value
Planned
value ¥2,000,000
Impact of
option -¥424,000 -¥836,000 -¥12,000 ¥0
Revised
value ¥1,576,000 ¥1,164,000 ¥1,988,000 ¥2,000,000
Probability 0.70 0.30 0.33 0.67
Factored
value ¥1,103,200 ¥349,200 ¥656,040 ¥1,340,000
Derived
value ¥1,452,400 ¥1,996,040
Probability 0.50 0.50
Factored
value ¥726,200 ¥998,020
Expected
value ¥1,724,220
What happens if there is no shutdown and the weather in December is warm?
The various proposals are examined using spreadsheets as follows. The first
spreadsheet looks at the outcome if the project just carries on as planned. This is the
same as the fifth of the proposals suggested to the project team and shows the
consequences of making no special arrangements to mitigate risks but simply reacting to
whatever happens. The convention is that extra costs are preceded by a minus sign;
savings are positive.
¥349,200. The expected value for the stoppage scenario is the sum of those factored
values, ¥1,452,400. Note that we do not need to consider any extra costs due to
working in December (e.g. heaters) because no work will take place if there is a
shutdown.
The same process applies to the examination of what happens if there is no shutdown,
but the weather in December may be cold or warm. If the weather is cold, an additional
cost of ¥12,000 would be incurred for heating equipment during the pouring of the seats.
By the same process as before we arrived at an expected value if there is no stoppage
of ¥1,996,040.
We know that the chance of a shutdown is reckoned at 50%, so the net expected value
for the whole project if no special measures are taken to mitigate risk is ¥1,724,220.
This is in fact the expected value of the fifth proposal, doing nothing.
The next step is to evaluate the expected value of the other four proposals.
Proposal one is to expedite (speed up) the pouring of the concrete for the seats. It
improves the project completion time to 3 Dec 10 if there is no shutdown, 28 Jan 11 if
there is an 8-week shutdown and 25 Feb 11 if there is a 12 week shutdown. This
reduces the additional costs to ¥6,000 for the 8-week (two weeks of overhead and zero
weeks of penalty) and ¥218,000 for the 12-week (six weeks of overhead and two weeks
of penalty). Note that once again a shutdown and cold weather problems in December
are mutually exclusive. Also, because of the earlier completion with no shutdown, no
concrete pouring activity will take place in December and in fact the overhead costs are
reduced because the project completes six weeks before the baseline date. This allows
a cost savings for the no shutdown branches of 6 times ¥3,000 or ¥18,000.
The updated expected value chart looks like this:
PROPOSAL 1
-
ACCELERATE No No Expected
SEAT Expected stoppage, stoppage, value with Overall
GALLERY Planned 8 week 12 week value with cold warm no expected
POURING value stoppage stoppage stoppage December December stoppage value
¥1,870,00
Planned value 0
Impact of
option -¥6,000 -¥218,000 ¥18,000 ¥18,000
¥1,864,00 ¥1,652,00 ¥1,888,00 ¥1,888,00
Revised value 0 0 0 0
Probability 0.70 0.30 0.33 0.67
¥1,304,80 ¥1,264,96
Factored value 0 ¥495,600 ¥623,040 0
¥1,800,40 ¥1,888,00
Derived value 0 0
Probability 0.50 0.50
Factored value ¥900,200 ¥944,000
Expected ¥1,844,20
value 0
Note that the total maximum value of the project has been reduced to ¥1,870,000
because proposal one requires an additional ¥130,000 of expense for all four possible
scenarios. The expected value of the project, however, rises to ¥1,844,200 with this
proposal.
For proposal two, examination of Figures 2 and 3 shows that building the main floor
foundation is not on the critical path. Hence money spent to accelerate completion
would be wasted. Specifically, it lowers the expected value of proposal one by ¥65,000
to $1,761,200.
Similarly proposal three also reduces the duration of a task off the critical path. As in
proposal two, this expense simply lowers the expected value of proposal one by ¥60,000
to ¥1,766,200.
Proposal four is harder to evaluate. If there was an 8-week or 12-week shutdown the
same two activities would benefit from expediting; Pour Seats and Paint Seats. For the
8-week shutdown a smaller amount of expediting will be used to reduce the extra cost
incurred. Specifically, Pour Seats could be reduced to 2 weeks from 4 weeks for a cost
of ¥40,000 and Paint Seats could be reduced to 1 week from 3 weeks also for a cost of
¥40,000. The Gantt chart for the 8-week shutdown looks like this:
PROPOSAL No No Expected
4 - WAIT Expected stoppage, stoppage, value with Overall
UNTIL 1 Planned 8 week 12 week value with cold warm no expected
DECEMBER value stoppage stoppage stoppage December December stoppage value
Planned
value ¥2,000,000
Impact of
option -¥92,000 -¥445,900 -¥12,000 ¥0
Revised
value ¥1,908,000 ¥1,554,100 ¥1,988,000 ¥2,000,000
Probability 0.70 0.30 0.33 0.67
Factored cost ¥1,335,600 ¥466,230 ¥656,040 ¥1,340,000
Derived value ¥1,801,830 ¥1,996,040
Probability 0.50 0.50
Factored
value ¥900,915 ¥998,020
Expected
value ¥1,898,935
Figure 8: Project Expected Value for Proposal 4
This analysis shows that proposal four has the best expected value and, on cost benefit
grounds, should be selected.
Question 2:What other basis might be used to make a decision besides expected
costs? What might the decision be in that case?
Other solution techniques drawn from decision analysis can be used, such as the
minimax decision rule. To employ this technique a table will be built of the possible
payouts for proposals 1, 4 and 5 (the others can be safely eliminated as no better than
one of these three):
No No
stoppag stoppag
8 week 12 week e, cold e, warm
stoppag stoppag Decemb Decemb
Outcome e e er er
No No
stoppage stoppage
8 week 12 week , cold , warm
stoppag stoppag Decemb Decemb
Outcome e e er er
- - -
Proposal 1 ¥44,000 ¥0 ¥100,000 ¥112,000
-
Proposal 4 ¥0 ¥97,900 ¥0 ¥0
- -
¥332,00 ¥488,00
Proposal 5 0 0 ¥0 ¥0
Using the minimax regrets criteria we compare the maximum regrets of each proposal
and choose the smallest one. In this case, proposal 4 has the smallest maximum regret
at - ¥97,900 so on this basis it would also be chosen.
Question 3:What other factors might enter into the decision such as behavioral,
organizational and political?
There are a number of non-financial factors that could be considered in making the
decision including:
The political and marketing implications of not completing the job on time.
The organization’s ability to quickly change and then execute an updated project
plan in response to events.
The company’s overall ability to execute any project, let alone one with problems
The benefits of keeping the team working on the project, rather than interrupting
their work on the arena.
Demonstrating a competent and professional approach to a serious problem.
Lotus Construction would want to behave in an assertive way towards the utility
company, to ensure it realized the effects of the shutdown and the need to
complete its work quickly and with the least disruption.
Lotus could consider changing the specification of the arena to speed up
construction, but there is not really time to do this.
Lotus might consider whether there are grounds for a legal action against the
utility company to recover some of its unexpected costs.
Question 4:What decision would you make if you were the project director?
The president would decide to go with proposal four, based on its highest expected
value.