Hi Babynus, protion, all.
First of all, is not a bug, nor a mis-configuration or whatever, just a behavior (proving how good is this tool).
I got what happened, and I would like to share it with all.
The algorithm, day-by-day, plan each activity according to:
- Previous dependencies
- Activity Priorities
- WBS position
- Planning Mode
Let us consider ASAP. See the project PRG in demo. There are 3 activities assigned to same resource; two of them have a predecessor activity executed by another resource, while the third free of dependencies. The tool then schedules A3 and the predecessor the first day, then second day, an activity with higher priority (smaller WBS) is available; the system set A3 on-hold and execute A1. Same for next day with A2. Then re-start with A3. Below a screenshot:
If we invert the WBS position, the behavior is different:
However, there are a plethora of activities (i.e. testing) that is better not to stop once started. I solved my plan by re-prioritizing the activities, however, there is a way to tell the system that, for specific activities, once a resource is booked, the activity must be completed?
Maybe an improvement suggestion....
However, thanks for the support, this is the best PM tool I've used in my life. Congratulation!!!