Chapter 08 HW
Chapter 08 HW
Chapter 08 HW
Review Questions
Resource scheduling systems usually reduce flexibility because when resources are
considered, computer routines use slack to get an “efficient” schedule. When slack is
used up, flexibility is lost and the risk of delaying the project increases. If the
resource conflict occurs on the critical path, the project is delayed.
Students should not be limited to these reasons; there are many more reasons for
scheduling resources.
4. How can outsourcing project work alleviate the three most common problems
associated with multiproject resource scheduling?
The risks associated with leveling, crashing, and “catch-up” are similar to those noted
in question 2. Flexibility is decreased and risk of delay is increased. For example,
slack is used up and may cause other bottlenecks later in a sequence of activities.
Having time buffers at merge points before the project begins could help avoid some
of the need to crash activities. Decoupling critical activities can help to cut time if
decoupling is possible and resources can be shifted; however, the risk is typically
reduced only slightly.
Other systems do not measure how much work is accomplished for the money spent!
Hence, without time-phasing cost to match your project schedule, it is impossible to
have reliable information for control purposes.
Exercises
Resource constraints extend the project duration from 12 days to 14 days and Activity
2 which was part of the original critical path is no longer critical path. All other
activities are critical which illustrates the key point that resource constraints tend to
increase the sensitivity of project networks.