Cross Project Dependencies updated when task has a % complete

[L8rdays]

I hope you can tell me what I'm doing wrong, because I can't believe it works
this way.

Actually this question applys regardless of cross project or locally linked
tasks.

Task 3 % complete = 20 Linked to start after Task 2 has finished.

If Task 2 duration changes impacting the finish date and it is tied to
another task that has something other than 0% complete, it doesn't update
that task. In this case Task 3 wouldn't show a change because task 2 slipped.

Why??? I'm assuming there is logic behind this, I need help understanding
this and training it.

Thanks

 

[Dale Howard [MVP]]

L8rdays --

When you enter progress on a task, either manually or by accepting progress
from PWA, Project Professional 2007 enters an Actual Start date on a task.
When a task has an Actual Start date, the system will not move the Start
date of that task, no matter what happens with the predecessor. Hope this
helps.

 

[L8rdays]

Hi Dale!

Thanks for the response.

Here is my delima I really could use a best practice on.

Project Scope:
Construction meets IT meets business is live.
So I have a project plan that talks to Construction date deliverables.
Then I have another project plan that talks to IT deliverables tied to the
business functional areas. I've setup the Construction project and IT
project deliverables as milestone project plans. I then need to tie the IT
plan to the business plans so they know when they can move into their
functional areas. They were trying to tie it to a line item that has a
duration and actual start / finish dates. Should I instead have them put in
a milestone task item to tie back to the IT plans. Then their milestones
will tie back to other tasks within their project plan. They then can see
the milestone be impacted by change from the IT plan and then they will have
to understand (manually) the impact to the rest of their plan.

Thanks!!