0

In my project, I have (among others) tasks A and B such that there is no dependency between them, and each of them can be carried out by resource R1 or resource R2. All things being equal, it makes more sense to do A before B (especially if both are done by the same resource), but it's not strictly necessary.

Is there a way to capture this relationship between tasks and have Project honour it when levelling? I currently solve this by introducing a start-to-start dependency of B on A if they're done by the same resource. Hower, sometimes I have to re-assign tasks between resources (as new tasks crop up, resources go on unexpected leave and so on), and if I forget to remove these dependencies, they can worsen the planning considerably.

I tried setting the priority of task A higher than task B, but it doesn't seem to have an effect on their relative ordering.

Angew is no longer proud of SO
  • 366
  • 3
  • 13

1 Answers1

1

Try using priority and creating larger gaps between the priority numbers. Then use Priority, Standard in the leveling calculation. You can also quickly view tasks that were leveled because of resource overallocations in the Leveling Gantt. (Or add the leveling delay field to a task view). Flag the tasks that were delayed or if you re-assign tasks, run the leveling command again and it will remove any delay that is not necessary.

JulieS
  • 438