MS Project: Task has 1 predecessor, but won't start unitl 1 month after predecessor ends
Posted on 2011-09-28
I have two projects using a shared resource pool. I want the schedule for project A to have priority over project B. I used load leveling. It worked -but I did not set priorities before load leveling. In project A I have task #8 with only one predecessor -task #7. I did not specify any lag time. #8 is to start ASAP after #7. Task #7 ends in October. Project sets task #8 to begin in December. The one resource for the task is "Bob".
In project B, "Bob" is a busy guy all through November. I reset the priority of project B to 300. I also set the Nov. tasks, and the summary tasks, all to priority 300.
I reset project A, and the relevant tasks to priority 900. In A, it still won't start #8 before December -even if I manually set it to start Nov 1, it won't save and blips back to Dec for start date.
How do I get task #8 to do what I thought I told it to: Start right after the only predecessor -task #7, and bump any tasks from project B due to higher priority?