A Gantt chart is only as good as the dates underneath it. Because DevStride's chart reads and writes the real items, the way to keep it honest is to keep the items honest. These tips are the ones that make the biggest difference in practice.
Give start and due dates to the rows people make commitments about, usually workstreams and milestones, and let the detail below them float. The chart flags any workstream whose children spill outside its dates; Shift + click the date cell to snap it to the earliest or furthest child. Do not hand-date every story unless the team plans at that grain.
Undated items get a placeholder bar at an inferred position and a Date missing cell. That is fine while planning and misleading in a review. Click the bar once to accept the inferred dates, set real ones, or remove the item from the chart.
A Dependency line means the dependent cannot start until the blocker finishes, and Linked mode will move it accordingly. If two things are merely connected, use Related: it draws a dashed line and never moves a date. The chart refuses ancestor/descendant links and loops; if you are fighting those rules, the hierarchy probably already expresses the relationship.
Linked mode shifts every dependent by the same number of days a due date moved. That is exactly right when you are replanning a slip and exactly wrong when you are tidying a single bar. Pick the mode before you start dragging (Shift + M), and use the Scenario Information list or the Dependency Graph to check the chain before a big move. See Link Mode.
Any question that starts with what if belongs in a scenario. Recording keeps your moves in the browser; saving gives you a named snapshot to compare against. Record a plan of record scenario before each planning round so you have a baseline to measure drift from.
Snap to cycles shows another team's sprints or program increments behind your bars, which is the fastest way to see whether a dependency lands in the right sprint. Remember that while a folder is selected, moving a work item's bar also moves it onto that cycle's board. Look first; drag only when you mean to reassign.
Options → Show Bar Progress By offers items completed, point estimate and time estimate. Teams that size work in points should show points, otherwise a 1-point chore and a 13-point epic fill the bar equally. Workstreams roll up their children; when epics stay open for a long time, turn on Progress from Lowest-Level Work so a module's bar reflects the stories finished inside it rather than the epics; set Track Progress Manually on a workstream only when the children genuinely do not represent the work.
Resist making a chart per audience. Build one chart per program, then give each audience a saved view with its own filters, zoom, expanded rows and, if useful, a baseline scenario. Views carry a shareable link and update as the chart does. See Viewing Gantt Charts.
Launches, contract dates and reviews are points, not spans. Add them as milestones, link the work that must finish before them, and the chart will show you the moment a slip crosses one.
Use Gantt groups to organize charts, filters to hide the other team's rows, and the level buttons to collapse to the summary before a meeting. A chart nobody can read at quarter zoom is two charts.
Scenario Planning
Record what-if date changes on a Gantt chart without touching real items, save them as a named scenario, and overlay any saved scenario as a baseline to see exactly which dates moved and by how many days.
Link Mode
How Link Mode shifts dependent items when a due date moves, what triggers the cascade, where the Gantt toggle overrides the organization default, and what happens when it is off.