1. Which if any of the resources are over allocated?
Design, Development and Documentation.
2. Assume that the project is time constrained and try to resolve any over allocation problems by leveling within slack. What happens? The design and documentation over allocated problem is solved. However, Development is still over allocated. (See Gantt chart 3.1) 3. What is the impact of leveling within slack on the sensitivity of the network? Include a Gantt chart with the schedule table after leveling within slack. The sensitivity of the network is increased. The slacks are reduced which lead to a loss of flexibility. The probability of activities delaying the project is increased because the reduction of slack creates more critical activities and critical paths. As in the Gantt chart 3.1, there are more critical activities (marked on red). 4. Assume the project is resource constrained and resolve any over allocation problems by leveling outside of slack. What happens? What are the managerial implications? Resource constrained means that the project has limited resource but the time is flexible. Using leveling outside of slack, the over allocation problems are resolved. However, the length of the project is 675 days, which is greatly increased by 145 days, and the new end date is now 8/17/2012. The managerial implication may be the delay of the next project that uses the same resource. The critical path is changed, the cost may be increased. For example, task 4.2 must wait until the task 2.3 is finished due to the resource constrain, and the idle resource may cause money. 5. What options are available at this point in time? Include a Gantt chart with the schedule table after leveling. One option is fast-tracking. The manager can try to rearrange the logic of the network so the critical activities can be done in parallel rather than sequentially. Another option is that the manager can figure out whether there is a way to...