Gantt Chart

A Gantt chart places tasks against a timeline. Each horizontal bar starts when a task begins and ends when it finishes. Bar length represents duration, and overlapping bars show tasks scheduled at the same time.

A two-week release planSample data

Loading chart…

View sample data

Read the schedule

Design runs from day 0 to day 3. Build starts on day 3 and finishes on day 9. Testing starts on day 7, so it overlaps with the last two days of build.

This example uses elapsed days from a project start. It does not exclude weekends or holidays. A working-day schedule needs a stated calendar.

Duration is not effort

A six-day task does not necessarily require six person-days of work. It may include waiting time or several people working together. A Gantt chart shows timing unless effort is supplied separately.

The same applies to progress: a bar ending next Friday does not tell you how much work is complete. Show actual progress as a separate, labeled measure if it is needed.

Add dependencies only when they are known

A dependency states that one task relies on another. Tasks drawn beside each other do not automatically have that relationship. The example shows timing only, without dependency arrows.

Use clear task names and enough detail to explain the schedule. Too many tiny tasks can hide the main deadlines. Keep planned and actual dates distinct when reporting delays.

For category totals without a time range, use a bar chart. For a metric that changes over time, use a line chart.