Dependency arrows and the critical path
Arrows connect a task to whatever it depends on, drawn from the same blocking relationship the board already tracked but never drew. Turn on the critical path and the longest chain in each group is highlighted, which is the set of tasks where a day lost is a day lost off the end date, as distinct from the ones with slack. Most of the argument about what to work on next is really an argument about which of those two a task is in, and it is much shorter when everyone is looking at the same picture.
Milestone roll-ups
A milestone sits on its target date as a marker with its own row, and it rolls up the state of every component linked to it, comparing where each one is against the stage the milestone needs it to reach. A hot fire that needs six parts machined and has two still queued reads at a glance, instead of being reconstructed from five task pages open side by side. Tasks that do not target a milestone are not hidden: they collect in a trailing group, so nothing falls off the view because it was never filed properly.
Dragging a bar reschedules the task
Drag a bar to move a task, drag its edge to resize it, or drag from its handle onto another task to mark one as blocking the other. Existing arrows can be redrawn or deleted the same way. Every edit applies immediately against what is on screen and rolls itself back if the save is rejected, so the view never sits showing a change that did not happen. A drag that lands back where it started writes nothing at all.
Moving a blocker moves its dependents
With ripple on, pushing a task later pushes whatever was waiting on it, far enough to stay clear and no further, and dependents that already had room do not move. This is the part a static chart cannot do: the reason to draw the dependency at all is that it should behave like one, and a chart that lets you move a blocker and leaves the chain sitting behind it is quietly lying about the plan. Ripple can be turned off when you want to move exactly one thing.
Zoom levels and the cross-project view
Switch between a week, a month and a quarter depending on whether you are checking tomorrow or the whole build cycle before a launch window. Overdue work is marked, and an open task with no date is drawn as a stub at today rather than dropped from the view. Across projects the same timeline groups by project instead of by milestone, so a lead can see every build at once without opening each one.