Finding Overallocations in the Resource Allocation View

     

The Resource Allocation view is a combination view with the Resource Usage view in the upper pane and the Leveling Gantt view in the lower pane. The reason this view is so useful is that the Usage view in the upper pane does a great job of showing exactly how many hours have been assigned to a resource during a specific time period and the Leveling Gantt view shows the task in question and also a graphical representation of how far the task can be moved out in time without delaying the project. This lets you see if you can move the entire assignment to a later time, and what effect this move would have on the project finish date.

Showing and Using the Resource Management Toolbar

graphics/one_icon.jpg Right-click any toolbar and select Resource Management.

graphics/two_icon.jpg Show the Resource Allocation view.

graphics/three_icon.jpg Move the selection in a view to the next overallocation .

graphics/08inf03.jpg

Finding Overallocations

graphics/one_icon.jpg Click the Go To Next Overallocation button to have Project select the next overallocation.

graphics/two_icon.jpg Project moves to the first overallocation.

graphics/three_icon.jpg You can see that the overallocation is caused by Brian's assignment to Task 1 and Task 2.

graphics/four_icon.jpg This line shows the slack for Task 1. This means that Task 1 can be moved out one day and not affect the project finish date.

graphics/08inf04.jpg

Resolving Overallocations

There are several ways to resolve overallocations, including delaying an assignment or task so that it starts later, moving the task or assignment to start sooner, decreasing the assignment Units value so that the resource is not overallocated, or replacing the resource with one that will not be overallocated.

Delaying an assignment or decreasing the assignment's Units value both risk pushing out the project's finish date because they both generally push out the finish date of the task. The effect of such a change should be watched closely. The safest methods from a schedule standpoint are either to move the task so it starts sooner (if possible) or to replace the resource. Neither of these methods have a direct impact on the project's finish date, and in some cases starting the task earlier can even hasten the project's finish ”which is always a good thing!



Show Me. Microsoft Office Project 2003
Show Me Microsoft Office Project 2003
ISBN: 0789730693
EAN: 2147483647
Year: 2003
Pages: 204

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net