Microsoft Project provides many options for resolving overallocation at the Project, Task, Resource and Assignment levels of the Microsoft Project Data Model. In this Milestone Minute we will focus on the impact the assignment level of the data model had on resolving overallocation in the previous Milestone Minute. In upcoming Milestone Minutes we will continue to resolve overallocation through additional data model strategies. Also, at the end of this Milestone Minute is the answer to the question asked in the Resource Overallocation – Part 9 Milestone Minute.
In the previous Milestone Minute, a split appeared in the Gantt chart on Task B, and duration extended to 6 days on Tasks B and C after the leveling process as shown in the following illustration:
The reason for these changes is based on a default assignment level leveling option named Leveling can adjust individual assignments on a task. To access this option, from the Resource tab, Level group, click Leveling Options as shown in the following illustration:
In the Resolving overallocations section, Leveling can adjust individual assignments on a task is selected by default as shown in the following illustration:
With this assignment level option selected, Microsoft Project resolved overallocation for Wendy by moving her individual assignments on Tasks B and C, leaving Bradley’s assignments as is. For Bradley Beck, the only assignment impacted of his was on Task D as all assignments were rescheduled on Task D.
Applies To: All Current Versions of Microsoft Project.
In the previous Milestone Minute, Resource Overallocation – Part 9, we asked “why did Microsoft Project resolve the overallocation the way it did with the Standard order applied?”
The answer: with the Standard Order applied, the first pass at leveling defaulted to predecessor which means Wendy’s assignment on Task C moved first. Then, the second pass at leveling, defaulting to predecessor again, moved Wendy’s assignment on Task B as at that moment the overallocation was between Task B and Task C. Once the second move was made all overallocation for Wendy was resolved. This is the same as in a previous Milestone Minute!
Additional information: with the Standard Order applied, the following factors are considered in the leveling process: Predecessor, Amount of Total Slack, Start Date, Priority, and Constraints.