Professional Documents
Culture Documents
Chapter Outline
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
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.
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.
Without consideration of resources the project is estimated to take 13 time units and
the critical path is 2 → 4 → 6 (see Network Diagram).
Assume you have only three resources and you are using a computer using a
computer that uses software that schedules projects by the parallel method and
following heuristics. Schedule only one period at a time!
Minimum slack
Smallest duration
Lowest identification number
Keep a log of each activity change and update you make each period—e.g.,
period 0-1, 1-2, 2-3, etc. (Use a format similar to the one on page 241.) The log
should include any changes or updates in ES and slack times each period,
activities scheduled, and activities delayed. (Hint: Remember to maintain the
technical dependencies of the network.) Use the resource load chart to assist you
in scheduling (see pages 260-261).
List the order in which you scheduled the activities of the project. Which
activities of your schedule are now critical?
Recompute your slack for each activity given your new schedule. What is the
slack for activity 1? 4? 5?
You should not spend time planning how you are going to spend your bonus. The
schedule will take 16 days.
Note: Activity F needs to be scheduled ahead of G because the delay in its start has
caused its slack to be negative.
This case points to a very typical problem in practice. Students will come up with a wide
variety of approaches depending on their experience and business acumen. After some
discussion, the authors break the class into small teams and ask each team to come up
with a simple system of rules which can be used with current project management
software and which attacks the issues found in the Power Train case. Some of the issues
mentioned below need to be considered when developing any resource scheduling
system.
The heuristics suggested in the text are indeed very efficient in minimizing project
delays. A major key to their use is the breakdown of people skills and/or equipment
type—for example, mechanical, civil, electrical engineers. Unfortunately, there is a
tradeoff. The larger the classification, the less discriminate the heuristic is in selecting
the “right” people for projects. If the classification is more detailed, the heuristics will do
a better job of selecting, but project delays (because of required resources) will likely be
increased.
The better software companies have built in flexibility for assigning people to projects.
As project priority systems and project offices become more popular in project driven
organizations, scheduling systems which link projects to priority and people assignments
are showing up in multiproject environments. A common student format and sequence
for their approach and scheduling rules are shown below:
Clearly, this general system above has a strong link to strategy by using the priority
portfolio as a cutting criterion. Again, care should be taken to see that manual selection
Notice that a system such as the one suggested above allows management to estimate
types of resources that may be needed in the future. The system also keeps track of
resource availability by skill type.
Below is an undergraduate response to the case setting. MBA’s and executives are more
creative and detailed. Their systems usually cover more exceptions and include more
detail, but they also frequently miss the point that all their “special cases” contribute to
delays in other projects and reduce the effectiveness of resource utilization.
Student Response
Inputs:
In place of complexity, factors such as technology, size, product class, risk, and speed
could be used.
The moral of the case is “Don’t let priority drive selection of key people,” or “Don’t
waste super stars on low priority projects.”
Time is wasted by people finishing an activity early and not warning the resource of
the next activity to prepare to start early. Or, time is wasted by simply using safety
time to work on other tasks.
Feeder buffers exist to avoid delays in the critical chain. They are placed at the end
of a chain of non-critical activities that merge into the critical chain. Project buffers
exist to cover uncertainty or interruptions and to ensure the project duration is met.
Buffers are not expected to be used. They are used when delays force their use.
Slack can be used for almost any reason. Buffers can be only used to protect the
critical chain or project from being delayed.
Appendix Exercises
At press time the Goldratt Institute’s homepage features several cases the successful
application of CCPM.
Below is the CCPM network drawn for the Printer Software project.
Students’ work will vary depending upon the software they use to draw the Gantt
chart.
Key differences between Critical Chain (CC) and CCPM schedules include:
• The project duration for CC is 115 while for CCPM it is 58 with a 22 project
buffer. So even if all of the buffer is used, the project will be 35 days earlier than
CC.
• The CC schedule is driven by ES while the CCPM is driven by LF.
• Buffers are strategically located on CCPM schedule while slack is shared across
non-critical activities.
Problems:
1. Buy in is not apparent.
2. There is clear evidence of little or ineffective training.
3. Senior management is altering the CC methodology.
4. Multitasking is prevalent and inefficient.