External Dependencies

[Costelu]

Hi,
Dale Howard explained (11-05-2004) how to create cross-project dependencies.
When you open either project A of PM1 or project B of PM2, you will see a
gray "ghost task" in each project showing the dependency with a task in
another project. When the predecessor project B for instance is slipping
it would be nice that the ghost tasks are synchronized. When projects belong
to Project Managers within the organization and they have both different
RBS-values then this synchronization is not fully guaranteed. When PM1 opens
his project plan A the "Links between Projects" dialog box will not show the
correct information in the "differences" field. How can this be realized
(without assigning the PM1 into project B of PM2)? Any idea. Thanks.Luc

 

[Gary L. Chefetz \(MVP\)]

Costelu:

I have to ask how you went about establishing the links to begin with? If
your security around the projects is so tight that one PM cannot open an
project owned by another PM, who created the cross project links? At some
point, someone needed access to both plans to create the dependencies.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts

-

 

[Costelu]

Thanks Gary for your response.

Hereby some additional info.



PM1 of project A and PM2 of project B belong to a Project Managers group and
a My Projects category (also Open , Save, Assign Resource permissions) and a
security rule for the projects "they manage" and "are a team member". The
cross-project dependencies were executed by a Project Office member who
belongs to a My Organization category with access to all Current and Future
Projects and Resources, and has Open , Save, Assign Resource permissions.



To create cross-project dependencies between project A and project B, we
used the following method:

1. Open a new blank project2. Click Insert - Project3. Select project B
and click Insert4. Click Insert - Project5. Select project A and click
Insert Completing the first five steps creates a master project or
consolidatedproject. Continue with the following steps to link the tasks:
6. Roll out project B's subtasks7. Roll out project A's subtasks8. Select
the predecessor task in Project A, press and hold the Controlkey, then
select the successor task in project B9. Release the Control key and click
the Link Tasks button on the Standardtoolbar10. Close the master project
without saving it11. When prompted to save the subprojects, click the Yes
to All button When you open either project A or B, you will see a gray
"ghost task" ineach project showing the dependency with a task in another
project. (See Dale Howard 11may2004) When predecessor task in Project A
takes for example more time, this change should be visible in Project B. But
when PM1 opens project A he gets "File not found" in the Differences field
in the "Links between projects" dialog box. The reason I presume is the lack
of rights of PM1 on Project B.When PM2 adds PM1 as a resource in his project
B everything is running smoothly,and synchronization is possible (indicates
another end date in the "Links between projects"). The disadvantage is that
PM1 can change project B.Is there another solution without adding categories
to the security setup and preserve the security on both projects A and B

 

[Gary L. Chefetz \(MVP\)]

Costelu:

Given your approach, the Project Office person must periodically open the
plans to update the cross-project links. You can't expose some information
in a project without giving someone access to all of it.

To work around this you've got to give PM1 and PM2 the ability to at least
open each other's projects. In 2003, you can grant the open permission
without granting the save permission. So, you could create a category that
contains the PM1 plan with Open Project permission only and add PM2 to the
category and vice versa. Another option (really ugly and I don't recommend
it) is to link them through a third plan that both PMs have access to.

Otherwise, you've painted yourself into the proverbial corner.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts

-