Resource Leveling: A technique used when resource limits are strictly constrained. It involves adjusting the project schedule by delaying tasks until resources become available, which often results in an extension of the project's original finish date.
Resource Smoothing: A method applied when the project end date is fixed and cannot be delayed. It involves adjusting activities within their available float (slack) to ensure that resource demand does not fluctuate wildly, though it may not resolve all over-allocations.
Heuristic Scheduling: The use of 'rules of thumb' to prioritize resource allocation, such as assigning resources first to the task with the least amount of float or the task that is on the critical path.
| Feature | Resource Leveling | Resource Smoothing |
|---|---|---|
| Primary Constraint | Resource Availability | Project Completion Date |
| Schedule Impact | Often extends the project duration | Does not change the finish date |
| Critical Path | Can change the critical path | Does not change the critical path |
| Goal | Resolve over-allocation | Minimize peaks and valleys in usage |
Identify the Bottleneck: In exam scenarios, always look for the 'Critical Resource' that appears in multiple parallel tasks. If this resource is over-allocated, the project duration will likely increase regardless of the theoretical critical path.
Check the Float: Before applying leveling, calculate the total float for each task. Leveling should ideally use up float on non-critical tasks first to minimize the impact on the overall project timeline.
Resource-Constrained Critical Path: Be aware that resource limitations can create a new critical path, sometimes called the 'Critical Chain,' which accounts for both task dependencies and resource availability.
Student Syndrome: The tendency for people to start working on a task only at the last possible moment before a deadline. This leads to wasted 'safety time' and increases the risk of project delays if any issues arise during the final push.
Parkinson's Law: The concept that 'work expands so as to fill the time available for its completion.' If a resource is allocated more time than necessary, they may work slower or add unnecessary complexity rather than finishing early.
Ignoring Lead/Lag Times: Failing to account for the time it takes to procure materials or the 'ramp-up' time required for a new team member to become productive can lead to unrealistic schedules.
Critical Chain Method: An extension of resource management that focuses on resource dependencies rather than just task dependencies. It incorporates 'buffers' to manage uncertainty and protect the project finish date.
Earned Value Management (EVM): Resource management data is a primary input for EVM. By tracking actual resource usage against the planned baseline, managers can calculate cost and schedule variances to predict final project outcomes.
