A Gantt chart puts work on a calendar: one row per piece of work, one bar per span of dates, lines between bars where one piece of work waits on another. DevStride's Gantt is built on your existing workstreams, items and boards rather than a separate task list, so some classic Gantt terms map onto things you already have. This page is the dictionary. The how-to lives in Track Progress: Gantts.
| Term | In DevStride |
|---|---|
| Gantt chart | A named chart in Track Progress. It holds initiatives and milestones and points at workstreams and items that live elsewhere. Deleting a chart never deletes work. |
| Gantt group | A folder for charts in the chart picker. Charts without a group appear under Other. |
| Initiative | The top-level row on a chart. It exists only on the chart, has a name, description and color, and its dates are inferred from everything inside it. Think of it as a lane: "Q3 launch", "Platform team", "Client X". |
| Task | A workstream or item imported into an initiative. Its bar is its start and due date. Workstreams show their children when expanded. |
| Milestone | A single-date marker drawn as a diamond: a launch, a deadline, a review. Milestones belong to the chart and can be the start or end of a dependency. |
| Timeline | The right half of the chart: bars, milestone diamonds, dependency lines, the TODAY marker and, when snapped, cycle bands. |
| Table | The left half: Name, Start date, Due date, Duration, Cycle / Board, Progress and Relationships, all editable where it makes sense. |
| Term | In DevStride |
|---|---|
| Start date, Due date | The item's own dates. The chart reads and writes them; there are no Gantt-only dates. |
| Duration | Due date minus start date in calendar days. Editing it moves the due date. |
| Inferred dates | Where an item has no date, the chart draws a placeholder at a position inferred from its parent, children or today. Accept it with one click on the bar or Shift + click on the cell. |
| Rolled-up dates | Initiative dates are always the earliest start and latest due inside them. Workstream dates are their own, but the table flags when children spill outside and lets you snap to them. |
| Cycle dates | Items on cycle (time-boxed) boards can inherit their cycle's dates if the organization turns on Sync work item dates with their cycles. |
| Term | In DevStride |
|---|---|
| Predecessor / successor | Dependency / Dependent. Item B depends on item A means A blocks B. On the chart this is the orange line from A's end to B's start. There is one dependency type; finish-to-start is implied. |
| Related | A green dashed line with no scheduling meaning. Use it for "worth knowing about" connections. |
| Linked mode | The chart toggle (and organization default) that makes a due-date change push every dependent by the same number of days, down the whole chain. Unlinked mode moves only the bar you touched. See Link Mode. |
| Critical path | The chain of dependent work with no room to slip. DevStride does not compute or highlight a critical path. Trace it by hand with the Dependency Graph or by hovering bars to light up their lines. |
| Slack / float | How long a task can slip before it delays something else. Not computed; read it as the gap between a blocker's due date and the dependent's start date. |
| Snap to cycles | Overlaying one board folder's cycles (sprints, PIs) behind the bars. With a folder selected, moving a work item's bar also moves it onto that cycle's board. |
| Term | In DevStride |
|---|---|
| Progress | Bar fill and the Progress column. Options → Show Bar Progress By chooses items completed, point estimate or time estimate, or hides it. Workstreams show the rolled-up value of their children unless a manual percentage is set; Progress from Lowest-Level Work in the same menu counts every item at the bottom of the tree instead of direct children only. |
| Overdue | Due date in the past and not done. The row title turns red. |
| Resource allocation | Not a Gantt concept in DevStride. Assignees, teams and capacity live on items and boards; use the Assignee and Team filters to slice the chart. |
| Term | In DevStride |
|---|---|
| Scenario | A named set of what-if date changes recorded on a chart. While recording, moves stay in your browser and nothing is written to items. Saving stores a snapshot of every visible item's dates. |
| Baseline | A saved scenario applied as an overlay. Grey shadow bars show where each item was in the scenario, and three extra columns show the day-by-day difference. Classic Gantt tools call the original plan the baseline; in DevStride any saved scenario can play that role, including one you record without moving anything. |
See Scenario Planning.