Dependencies

[JennyK]

Sorry to ask what might be a really basic question.

My team is responsible for managing project dependencies between separate
projects.

What is the best way to do this in Project 2003 Enterprise? If we put
physical links between plans and one plan is updated, will this cause
confusion and automatic rescheduling in the other plan? Are there any other
ways of doing this?

Many thanks

 

[Mike Glen]

Hi Jenny,

It sounds as if your using Project Server, in which case try posting on the
server newsgroup. Please see FAQ Item: 24. Project Newsgroups. FAQs,
companion products and other useful Project information can be seen at this
web address: http://project.mvps.org/faqs.htm

Mike Glen
Project MVP

 

[Rob Schneider]

Sorry to ask what might be a really basic question.

My team is responsible for managing project dependencies between separate
projects.

What is the best way to do this in Project 2003 Enterprise? If we put
physical links between plans and one plan is updated, will this cause
confusion and automatic rescheduling in the other plan? Are there any other
ways of doing this?

Many thanks

Jenny,

As Mike indicated, this from a technology perspective best discussed in
the Server newsgroup.

That being said, same issue appears when managing dependencies using
Project Standard. Despite the fact that confusion and re-computed
schedules can indeed result from separate projects linked via
dependencies, the good news is that confusion and re-computed schedules
can result. This is because it's better to know in advance of the
affect on the overall programme before the "confusion" is caused by
actual slipped schedules.

Make sure people talk, and make sure they try to develop project plans
which minimise critical dependencies. Doing that will minimise, if not
eliminate, any technology problems with Project Enterprise.

 

[Steve House]

A dependency by definition means that when the predecessor or driving
task's schedule is changed, the successor MUST change because its
schedule is determined by that of the predecessor. If it shouldn't
change, it shouldn't be linked as predecessor/successor.