An Analysis of Project Networks as Resource Planning Tools
Usage and availability of resources are essential considerations when establishing Project Networks in Resource Planning. This analysis has focused on some of the risks of certain actions used to offset resource constraints, advantages/disadvantages for reducing project scope, and options/advantages/disadvantages for reducing project duration. If implemented correctly, careful consideration of the outlined risks will make managing a project a little less painless.
Following is an analysis of project networks as resource planning tools. The analysis will be segmented into three topical areas to include: * Risks associated with leveling resources, compressing, or crashing projects, and imposed durations or "catch-up" as the project is being implemented; * Advantages and disadvantages for reducing project scope to accelerate a project and what can be done to reduce the disadvantages * Three options for reducing project duration and advantages and disadvantages to these options Risks Associated with Leveling Resources, Compressing, or Crashing Projects, and Imposed Durations or "Catch-Up" The text (Gray and Larson, 2008) gives good definitions for the risks associated with certain actions used to offset resource constraints. The act or process of evening out “resource demand by delaying noncritical activities (using slack) to lower peak demand” (Gray and Larson, 2008) is considered leveling resources. This action ultimately increases the resource utilization, which is more than likely the desired result. Even though one may get the desired results resource-wise, leveling resources often results in pushing out the end-date of a project. In most cases, that is the extreme outcome. Another risk that bears its head when slack is reduced, is loss of flexibility which equates to an increase in critical activities. Without slack anywhere in a project network, ALL activities become...
Please join StudyMode to read the full document