owner can't Update external tasks if he sees only his schedule

[David.Rot]

Hello,
I am running project server with 20 projects.
Only the owner of the project can see his project and not other
projects.

there are some external links between the schedules.
When the project owner opens his project the 'link between project'
window pop up but he see 'file not found' in the differences column.

So the owner cannot update his projects according to ecternal links
(he sees only 'file not found').

There is something I can do? Do I miss something?
Does the only option is to let his see (view only) the other projects
and then he will be able to accept the changes???

Thank you very much,
David

 

[Dale Howard [MVP]]

David --

I think your organization's use of cross-project dependencies is in direct
conflict with the default security settings in Project Server (as your PM's
have alread found). I would recommend that you modify the Project Managers
group to allow your PM's to see and open one another's projects Read/Write.
To do this, open the Project Managers group for editing and select the My
Organization category. In the Permissions grid, select the "Open Project"
and "Save Project" permissions to Allow and then save the changes.

Beyond this simple change, I would also recommend that you establish a
process for each PM to follow to deal with cross-project dependencies. You
must be very strict about not allowing a PM to change another PM's project
without the other PM's permission. Making this a training and performance
issue, and then hold them accountable for their performance. Hope this
helps.

 

[David.Rot]

David --

I think your organization's use of cross-project dependencies is in direct
conflict with the default security settings in Project Server (as your PM's
have alread found). I would recommend that you modify the Project Managers
group to allow your PM's to see and open one another's projects Read/Write.
To do this, open the Project Managers group for editing and select the My
Organization category. In the Permissions grid, select the "Open Project"
and "Save Project" permissions to Allow and then save the changes.

Beyond this simple change, I would also recommend that you establish a
process for each PM to follow to deal with cross-project dependencies. You
must be very strict about not allowing a PM to change another PM's project
without the other PM's permission. Making this a training and performance
issue, and then hold them accountable for their performance. Hope this
helps.












- Show quoted text -

Dale,
First, thank you very much for your help.

I can tell you that I have used your advises in the past and you gave
me some good ides.
Regarding the issue I have submitted, the big problem is that the PM's
are vendors that can't see other projects than their own (by
contract).
I am using a VPN to allow access to external users (not in the
domain), using Juniper device (if you know that web VPN).
It's all work fine.

So what you are saying that there is no option than let them see the
related projects (that have external tasks)?
Meantime I have set a work process that I will send them the changes
(of course I can see the changes, I am the admin), ones they approve,
I will make the changes and they will see the changes inside their
schedule.

Two more questions: (If you agree to answer I would appreciate it):
1. Regarding circular tasks, what do you think is the best way to
identify them?
I have created a filter that when a successor < predecessor (in the
same task) than we have a circular task.

Do you have an idea to do this differently?
2. I have a master schedule, what do you think is the best way to
create a 'what if' scenario's on a master level. Meaning when I open
the master (with 6 projects inserted) and I change a task for a
project the project linked to that task does not changed.
I have to open each project, accept the changes and then see the
changes on the global level.
What do you think?

Again thank you very much; I assume that you helped a lot of Project
Server admin wannabe

 

[Gary L. Chefetz [MVP]]

David:

The easiest way to detect a circular relationship between two plans is
simple:

Open one plan, if the system tells you that the dates have changed due to
the other plan, accept them and save and close.
Open the second plan, if the system tells you that the dates have changed
due to changes in the first plan, bingo, you have a circular relationship.
The best way to avoid these is by using sound plan structures and using
cross linking very sparingly..

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com