Resource Loading

[Robert]

In our environment, we have many engineers that will work on multiple
projects. Often the originally assigned resource gets moved to another
project and someone else take their place. A suggestion was made to add all
engineers to all projects as available resources. (Currently, assignments of
resources to a Project are done by the Program Management Office) Can any one
think of a draw back to this approach?

 

[Scott m Wagner - EPM Consulting Services]

Robert,

The drawback would be in performance. If you have many projects and many
Systems Engineers there could be a large impact on performance. This may or
may not be avoidable depending on the requirements of the business.

I have been able to use generic resources to great advantage.
zz_Systems Engineer1, zz_Systems Engineer2, zz_Systems Engineer3, for
example. These generic resources can then be replaced by actual resources
during the project. It really depends on the business needs.


Hope that helps,
Scott

 

[Reid McTaggart]

Why not just loosen up permissions so that PMs are permitted to add engineers
to their project teams? You can do this with a Category. The PMO can retain
control of other resources.