Loading
Because order lives in someone's head. The plan is a list, the sequence is understood by two people, and when a task slips nobody can say what else just moved.
A dependency records that one task cannot start or finish until another does — the order the work genuinely needs.
Dependencies are blocks and blocked-by links between tasks. The plan derives dates from them, so a change propagates instead of being manually chased through the schedule.
An integration task slips a week. Everything downstream shifts on the Gantt immediately, the delivery date moves, and the people who are now overcommitted show in capacity — before the status call.
They will not tell you the plan is realistic. A dependency chain says what must follow what; whether the estimates on it are honest is a different question.
The Gantt draws bars from them, capacity re-sums when they move, the roadmap reflects the new delivery date, and blocked work leaves personal queues.
Yes, and the effect shows in both plans.
Recorded as a preference rather than a block, so it advises without moving dates.
Yes, on creation, rather than at plan time.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.