Resource Pool

R

Rod C

I have seen several posts regarding the resource pool, overallocations, links
to previous files, extending task durations, etc. And I guess this question
is directed more at JulieS and Jan De Messemaeker.
Is there a "best practices" document or user information regarding how to
avoid these pitfalls? In my particular instance (consultant advising on
project best practices - not necessarily MS Project) the Program Director
does not seem to be open to ProjectServer (although that may change) and as a
result of the issues with the resource pool mentioned above, wants to
disassociate the projects from a shared pool. (I understand the issues of
common resources, mulitiple projects, etc. but cannot get past the hurdle of
"this worked before".)
Moreover, the project managers of which there are two, must submit plan
updates to a central control administrator and not update the plans
themselves. And the resources submit paper documents into a central folder
from which the administrator updates the plans with actuals. Obviously not
best practice from a project point of view nor from an MS Project point of
view.
Btw we are using MS Project 2003, sp2. I have recommended PS but seem to be
going nowhere with that suggestion.
Other than 'giving up' which is not in my nature, do you have any
suggestions? Please help if you possibly can.
Desparate 4 Some Guidance
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top