Resource optimization techniques
“Resource Optimization Techniques” is a tool/technique for the process “Develop Schedule”.
Examples of resource optimization techniques that can be used to adjust the schedule model due to demand
and supply of resources include, but are not limited to: – Resource leveling. A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply. Resource leveling can be used when shared or critically required resources are only available at certain times, or in limited quantities, or over-allocated, such as when a resource has been assigned to two or more activities during the same time period, as shown in Figure 6-20, or to keep resource usage at a constant level. Resource leveling can often cause the original critical path to change, usually to increase.
Start Activity A Tom: 8 hrs Sue: 8 hrs Activity B Sue: 8 hrs Activity C Tom: 8 hrs Tom: 8 hrs Sue: 16 hrs Tom: 8 hrs Day 1 Day 2 Day 3 Start Activity A Tom: 8 hrs Sue: 8 hrs Activity B Sue: 8 hrs Activity C Tom: 8 hrs Tom: 8 hrs Sue: 8 hrs Sue: 8 hrs Tom: 8 hrs Day 1 Day 2 Day 3 Activities Before Resource Leveling Activities After Resource Leveling
Figure 6-20. Resource Leveling – Resource Smoothing. A technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. In resource smoothing, as opposed to resource leveling, the project?s critical path is not changed and the completion date may not be delayed. In other words, activities may only be delayed within their free and total float.
Thus resource smoothing may not be able to optimize all resources.
“Resource Optimization Techniques” is a tool/technique for the process “Control Schedule”.
Resource optimization techniques involve the scheduling of activities and the resources required by those activities while taking into consideration both the resource availability and the project time.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping