Following the session the delegates should have a basic understanding of the typical resource scheduling problems for time as well as resources constrained projects. In addition the delegate should be able to show how free slack can be used to effect resource leveling.
Project sequencing and scheduling deals poorly with resource availability and utilization ;
Project network times are not a schedule until resources have been assigned:
The implicit assumption is that resources will be available in the required amounts when needed;
Adding new projects requires making realistic judgments of resource availability and project durations;
Resources may be adequate but demand can vary – then resource leveling or smoothing is required; or
Resources may not be adequate to meet peak resource requirements , the late start date of certain activities will have to be delayed and project duration be increased – this is referred to as resource constrained scheduling.
Constraints related to the networked sequence in which project activities must occur – example, dig trenches, pour cement, then lay bricks for walls…
Activities that cannot occur in parallel or are affected by contractual or environmental conditions – ship renovation, one person allowed in confined space…
The absence, shortage, or unique interrelationship and interaction characteristics of resources that require a particular sequencing of project activities- example, normally you have 3 people to do three activities in parallel, but because you only have one person you have to schedule them in series – NB!! Resource dependency takes priority but cannot violate technical dependencies.
Projects that must be completed by an imposed date;
Require the use of leveling techniques that focus on balancing or smoothing resource demand by using positive slack (delaying noncritical activities ) to manage resource utilization over the duration of the project with the following result:
Peak resource demands are reduced;
Resource demand over the life of the project are reduced;