Task hierarchy and dependencies
Separate parent-child structure from work that blocks other work.
Two different relationships
A parent groups child tasks; a dependency specifies what must happen before other work can proceed. A task can be both a parent and have work of its own. Check both relationships in the imported data rather than assuming that a shared parent creates a dependency.
External waits and completed blockers
For an external wait, specify the task or reason and its deadline. Check that the deadline is compatible with the planning horizon. A completed blocker must not consume working capacity again. If source data is incomplete, clarify its status or dependency before starting.
Priority does not remove dependencies
A dependent task may have a higher priority than its blocker. That does not allow it to start before a required dependency is satisfied. Read both the priority and the dependency schedule when checking a result.
Related articles
- Review task data before calculating
Resolve missing work estimates and external deadlines; review other warnings.
- Read a calculation result
Check placement, capacity and unplaced work before adopting the plan.