A list of open tasks does not by itself show whether a person can do them in the expected time frame. Workload and saturation allow you to read the plan through the relationship between load and availability.
EDU and project workload
- Open Workload from the project or EDU and check the given context. The two views aggregate work with different perspectives.
- Set the period and available filters, then check the people or units included in the list. Compare data expressed in the same units.
- For a critical line, open the intended detail and identify which activities or associations contribute to the value.
- Compare load with availability, absences and assignments. A high value is a signal to be analyzed and does not in itself demonstrate an application error.
Resource saturation in the Gantt
- From your project, open Resource Phasing or the Predicted Saturation view. Check the resource and range displayed before reading the grid.
- Examine the distribution over dates and compare people. Colors and quantities must be read together with the calendar and configured availability.
- For a peak, trace the assigned activities and overlaps. Also check for any commitments on other accessible projects.
- Consider a different assignment or authorized rescheduling, then compare the result again. Don’t artificially increase availability to make the problem go away.
Putting this into practice
When a spike emerges, identify the activities that generate it before redeploying them. After a change, re-read the load to verify that the problem hasn’t just moved.
Learn more about Orchestris.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.