Quando usar um Gantt Chart
Your tasks have real start and end dates
A Gantt chart needs two dates per row. If your plan is a list of things in rough order with no dates attached, you have a checklist, and a table will serve it better.
Overlap is the thing you want to show
The reason to draw a schedule rather than list it is to make simultaneity visible — design still running while the build starts, QA overlapping the content freeze. Bars on a shared calendar show that instantly.
You are presenting a plan to people outside the project
Clients, executives and stakeholders read a timeline far faster than a project-management tool's task list, and a published chart does not need them to have a licence for anything.
The plan spans weeks or months, not hours
Gantt charts are comfortable from about a fortnight to a couple of years. Below that the bars are too short to label, and above it a roadmap of quarters says the same thing with less noise.
You want the schedule to live in a page, not a screenshot
An embedded chart updates when the data does, so the timeline in your status page or wiki stops being a picture from three weeks ago.