L
Lars Hallin
Hi,
I am helping a project team to put their plans in 4 or 5 MSP files, and
consolidate them into one master document and all resources in one pool. One
question that has risen is what the best practice is when it comes to track
conflicts (resource or calendar) across the consolidated files once the
project has strarted.
Is there any way to let Project warn for conflicts in project A as a result
of a change in project B? Or is it better to kep track of the consequenses
of a change manually, i.e. follow up on all linked tasks "downstream"?
Greatfull for any advice
Lars
I am helping a project team to put their plans in 4 or 5 MSP files, and
consolidate them into one master document and all resources in one pool. One
question that has risen is what the best practice is when it comes to track
conflicts (resource or calendar) across the consolidated files once the
project has strarted.
Is there any way to let Project warn for conflicts in project A as a result
of a change in project B? Or is it better to kep track of the consequenses
of a change manually, i.e. follow up on all linked tasks "downstream"?
Greatfull for any advice
Lars