|
|
|
Overview |
Reason 1 | Reason 2 | Reason 3 | Reason 4 | Reason 5 | Reason 6 |
Reason 7
|
Reason 8 |
Reason 9 | Reason 10 | Reason 11 | Reason 12 | Reason 13 | Reason 14 |
Reason 15
|
Reason 7: Limited resource forecasting capability in project plan scheduled to run multi years duration – Cause Resource over allocation
Scenario: PM is managing project plan of 1 year duration in two phases. PM wants to assign resource as committed against Phase 1 tasks, also want to show the resource as a proposed resource for Phase 2 assignments.
Project Server 2003:
Project Server 2003 lacks the capability to show the resource in a project plan as committed and as well as proposed.
In this scenario, Chia Jeff will appear as fully committed to this project until end of the project, meaning that Chia Jeff is not available for other projects. During this time, if another PM assign Chia Jeff to do work on his/her project, Chia Jeff will be appear as over allocated.
Project Server 2007:
Project Server 2007 allows PM to book the resource as Committed for the current phase and Proposed for future phases through the use of Resource Plan.
Resource Utilization is always accurate and thus over allocation of resources is avoided.
Resources are assigned to tasks only when actually needed.
| |
|
