A chart is cheap to make and cheap to delete, so the decision is less "should I create one" than "what should one chart cover". A good chart has one audience and one question: when does this program land, what is the platform team committed to this half, what does Client X see. Work can be on several charts at once, so you do not have to choose a single home for it.
For the full first-run walkthrough with screenshots, see Setting Up Gantt Charts.
You need CREATE_GANTT. Editing or deleting a chart afterwards needs MANAGE_OWN_GANTTS for charts you created, or MANAGE_ALL_GANTTS for anyone's. Everyone with ACCESS_GANTT can open and read every chart. If + Create is missing or an entry in it is greyed out, hover for the permission key to ask for.
Groups are folders in the chart picker. Create them from + Create then Gantt Group: the Manage Gantt Groups dialog lists existing groups and lets you add, rename or delete them. Any member with MANAGE_OWN_GANTTS or MANAGE_ALL_GANTTS can manage groups; they are shared across the organization. Charts with no group sit under Other.
Group by audience or portfolio rather than by date: "Engineering", "Marketing", "Client programs". Date-based groups fill up with dead charts.
Above the table, next to the chart name:
An empty chart needs at least one initiative before anything can be imported. Continue with Add to Gantt.
Gantt Charts Basics
The vocabulary of Gantt planning and what each term maps to in a DevStride Gantt: initiatives, milestones, bars, dependencies, Linked mode, cycles, progress, scenarios and baselines.
Add to Gantt
Every way to put work on a Gantt chart: initiatives, milestones, importing existing workstreams and items, creating new work from a row, and the Gantt bulk action from the Items Table or Map.