I agree -- this is critical for real world management. End-Start dependencies reflect a pure waterfall methodology. But the reality is projects are much messier, where a dependent task doesn't wait for its antecedent to complete.
So for example, task B will often start when Task A is only 75% complete. Yet there is still a dependency between these tasks such that if task A gets postponed by a week so does Task B.
This is so important that a gantt chart MUST support this to accurately reflect the project. Otherwise users have to trick the software by either eliminating explicit dependencies all
together, or entering incorrect start date for many tasks.
Multiple dependencies is also critical in order for a gantt chart to accurately reflect reality.
In my experience these are not just nice-to-have features, they are absolutely essential to any gantt chart tool.
john
supported this idea
·
I agree -- this is critical for real world management. End-Start dependencies reflect a pure waterfall methodology. But the reality is projects are much messier, where a dependent task doesn't wait for its antecedent to complete.
So for example, task B will often start when Task A is only 75% complete. Yet there is still a dependency between these tasks such that if task A gets postponed by a week so does Task B.
This is so important that a gantt chart MUST support this to accurately reflect the project. Otherwise users have to trick the software by either eliminating explicit dependencies all
together, or entering incorrect start date for many tasks.
Multiple dependencies is also critical in order for a gantt chart to accurately reflect reality.
In my experience these are not just nice-to-have features, they are absolutely essential to any gantt chart tool.