How to keep project managers from blowing away interprojectdependencies

[anovak]

If you are a program manager who is basically overseeing several sub-
projects that others are managing, say using a master project, and you
personally go in and identify/set the inter-project dependencies, is
there a way to "lock" those so that the project managers cannot remove
them?

Thanks
Andy Novak
UNT

 

[Dale Howard [MVP]]

Andy --

Anyone who can open the project Read/Write can remove or change the
dependencies. So, no, you cannot "lock" the cross-project dependencies.
Therefore, this is definitely a training and performance issue. Hope this
helps.

 

[andy.novak]

Andy --

Anyone who can open the project Read/Write can remove or change the
dependencies.  So, no, you cannot "lock" the cross-project dependencies..
Therefore, this is definitely a training and performance issue.  Hope this
helps.

Dale, that's what I figured but I certainly appreciate the response.
Are you guys going to be at the Project Conference in the Fall?

 

[Dale Howard [MVP]]

Andy --

Yes, I trust we will be at the Project Conference in force. Feel free to
stop by and say, "Hi!" Thanks for asking.

Andy --

Anyone who can open the project Read/Write can remove or change the
dependencies. So, no, you cannot "lock" the cross-project dependencies.
Therefore, this is definitely a training and performance issue. Hope this
helps.

Dale, that's what I figured but I certainly appreciate the response.
Are you guys going to be at the Project Conference in the Fall?