Resource Loading & Leveling Flashcards
7 cards from real CST practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Resource Loading & Leveling flashcards as text
Which resource leveling technique delays non-critical activities within their float to reduce peak resource demand?
Answer: Resource smoothing
Resource smoothing shifts activities within existing float without extending the project end date.
A resource histogram shows a technician allocated at 140% for two consecutive weeks. What does this represent?
Answer: Resource over-allocation requiring resolution
Allocation exceeding 100% indicates over-allocation, which must be resolved through leveling or smoothing.
What is the primary difference between resource-limited and time-limited scheduling?
Answer: Resource-limited fixes resources and may extend duration; time-limited fixes duration and may exceed resources
Resource-limited scheduling keeps resource usage within constraints, potentially extending the schedule, while time-limited scheduling preserves the end date.
Which metric on a resource loading table indicates the cumulative hours a resource is assigned across all activities?
Answer: Total resource demand
Total resource demand sums all assigned hours across every activity for a given resource.
When applying resource leveling on the critical path, what is the most likely consequence?
Answer: The project end date is extended
Leveling critical path activities has no float to absorb the shift, so the project completion date moves later.
A project has three parallel tasks each requiring 4 workers for 2 weeks. The organization has only 8 workers available. What leveling action is most appropriate?
Answer: Sequence the tasks to stay within the 8-worker limit, extending the schedule
Sequencing tasks so no more than two run in parallel keeps demand at or below 8 workers, though it extends duration.
In resource loading analysis, what does an 'S-curve' of cumulative resource hours typically represent?
Answer: Slow start, peak in mid-project, and tapering at close
Cumulative resource usage typically follows an S-curve: slow ramp-up, rapid acceleration through execution, then tapering during closeout.