Tutorial 8 WithSolution
Tutorial 8 WithSolution
Tutorial 8 WithSolution
Chapter Outline
Review Questions
Resource scheduling ties to project priority because resources are limited. Remember, the
priority system ranks projects which then determines which project each resource should work
on first.
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?
Outsourcing can be used to reduce project slippage, improve utilization of critical resources,
and avoid resource bottlenecks. For example, project delays can be avoided by contracting
key activities when resources are not available internally. Likewise, hiring consultants to help
with Y2K problems allows critical IT people to work on specific problems, while the outsiders
work on standard programs. Not only does the project get done on time, but the company
avoids hiring IT personnel to meet a short term need.
5. Explain the risks associated with leveling resources, compressing or crashing projects,
and imposed durations or “catch-up” as the project is being implemented.
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
1. Given the network plan that follows, compute the early, late, and slack times. What is
the project duration? Using any approach you wish (e.g., trial and error), develop a
loading chart for resources Electrical Engineers (EE), and resource, Mechanical
Engineers (ME). Assume only one of each resource exists. Given your resource schedule,
compute the early, late, and slack times for your project. Which activities are now
critical? What is the project duration now? Could something like this happen in real
projects?
Instead of taking 9 days the duration has been extended to 11 days and all activities are critical.
Resource shortages are common in real projects and this problem demonstrates the impact
resource constraints can have on project schedules.
2. Given the network plan that follows, compute the early, late, and slack times. What is
the project duration? Using any approach you wish (e.g., trial and error) develop a
loading chart for resource resources Carpenters (C) and Electricians (E). Assume only
one Carpenter is available and two Electricians are available. Given your resource
schedule, compute the early, late, and slack times for your project. Which activities are
now critical? What is the project duration now?
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.