A
anovak
As I understand it, there is a difference between the plan owner and
the project manager.
That is, the plan owner has control over the entire plan whereas a
subset of tasks can be "assigned" to a particular PM who will receive
all the time reporting appovals instead of the plan owner?
If that's the case, is the plan owner the only one who can phsically
open the plan with Project Pro and add, edit, delete tasks and
assignments?
If there were 5 different sections of the plan assigned to 5 different
PMs, can they all updated the plan or can they only approve progress
as entered via time reporting?
If the plan owner is the only one who can physically change the plan
via Project Pro, is there a way for the PMs to change the plan (add
tasks, remove tasks, edit tasks, change assignments) via some type of
PWA request and approval mechanism without having to physically open
the plan with Project Pro?
The reason I ask is that for now we are using separate *.mpps that
have interproject dependencies and it has been a real bear to manage.
Seems like I have read on one of these threads a scenario like
mentioned above.
Thanks,
Andy Novak
University of North Texas
the project manager.
That is, the plan owner has control over the entire plan whereas a
subset of tasks can be "assigned" to a particular PM who will receive
all the time reporting appovals instead of the plan owner?
If that's the case, is the plan owner the only one who can phsically
open the plan with Project Pro and add, edit, delete tasks and
assignments?
If there were 5 different sections of the plan assigned to 5 different
PMs, can they all updated the plan or can they only approve progress
as entered via time reporting?
If the plan owner is the only one who can physically change the plan
via Project Pro, is there a way for the PMs to change the plan (add
tasks, remove tasks, edit tasks, change assignments) via some type of
PWA request and approval mechanism without having to physically open
the plan with Project Pro?
The reason I ask is that for now we are using separate *.mpps that
have interproject dependencies and it has been a real bear to manage.
Seems like I have read on one of these threads a scenario like
mentioned above.
Thanks,
Andy Novak
University of North Texas