Gantt Chart

What is a Gantt Chart?

A Gantt chart is a horizontal bar chart that shows a project schedule, with each task's start, duration and end plotted against time, along with dependencies, milestones and progress.

Updated November 2026 · 3 min read


A Gantt chart is a bar chart that shows a project's schedule. Tasks are listed down the left side and time runs across the top, and each task appears as a horizontal bar whose position and length show when it starts and how long it takes. Most Gantt charts also show dependencies between tasks, milestones and progress to date, so a single picture shows what has to happen, in what order, by when and whether the project is on track.

The chart is named after Henry Gantt, an American engineer and management consultant who developed and promoted it in the 1910s to plan and track work in factories and, during the First World War, in military supply and shipbuilding programs. A similar chart, the harmonogram, was devised by the Polish engineer Karol Adamiecki in 1896, but he did not publish it widely until 1931, by which time Gantt's version was well known. Gantt charts were drawn by hand for decades. Software such as Microsoft Project, first released in 1984, made them the default view of project schedules, and they are now built into most project and portfolio management tools.

Elements of a Gantt Chart

  • Tasks: the work items, often grouped into phases or a work breakdown structure.
  • Bars: each task's start date, end date and duration.
  • Dependencies: arrows linking tasks that rely on each other.
  • Milestones: key events with no duration, such as a design approval or launch date, usually shown as diamonds.
  • Progress: shading inside each bar showing how much is complete.
  • A today line: a vertical line showing the current date, so tasks behind schedule stand out.
  • Baseline: the original plan, shown alongside the current schedule to reveal slippage.
  • Owners or resources assigned to each task.

Types of Dependency

TypeMeaningExample
Finish-to-startB cannot start until A finishes. By far the most common.Testing starts after development finishes
Start-to-startB cannot start until A startsWriting documentation starts once development starts
Finish-to-finishB cannot finish until A finishesFinal editing cannot finish until writing finishes
Start-to-finishB cannot finish until A starts. Rare.The old system stays running until the new one goes live

Gantt Charts and the Critical Path

When dependencies and durations are defined, the chart reveals the critical path: the longest chain of dependent tasks, which sets the earliest possible finish date. Any delay to a critical task delays the whole project. Tasks off the critical path have float, or slack, meaning they can slip by some amount without affecting the end date. Most Gantt tools calculate and highlight the critical path automatically, using the critical path method.

An Example

Consider a hypothetical company relaunching its website, with these tasks:

TaskDurationDepends onDays
A. Requirements5 daysNone1 to 5
B. Design10 daysA6 to 15
C. Content writing15 daysA6 to 20
D. Build20 daysB16 to 35
E. Testing5 daysC and D36 to 40
Launch (milestone)0 daysEDay 40

The critical path is A, B, D, E: 5 + 10 + 20 + 5 = 40 days. Content writing finishes on day 20 but testing cannot start until day 36, so content has 15 days of float. On the chart, the project manager can see at a glance that a week's delay in design moves the launch, while a week's delay in content does not. If the launch must come sooner, the only places to save time are on the critical path, for example by starting the build on parts of the design as they are approved.

Strengths and Limitations

  • Strengths: easy to read, good for communicating timelines to stakeholders, makes dependencies and the critical path visible, and well suited to projects with fixed scope and sequential work, such as construction, events, migrations and regulatory programs.
  • Limitations: detailed charts become hard to maintain and read, they imply more certainty than most estimates deserve, they show schedule but not effort or cost, and they fit poorly with iterative work where scope changes every sprint.

Agile teams usually plan with backlogs and boards, but many organizations still use a high-level Gantt view across teams to coordinate dependencies, milestones and releases. In portfolio management, Gantt-style timelines show how projects overlap and where they compete for the same people.

Common Pitfalls

  • Too much detail, with hundreds of tiny tasks that no one updates.
  • A plan that is never updated, so the chart shows the original intention rather than reality.
  • Missing dependencies, which hide the real critical path.
  • Ignoring resources, so the chart assumes people can work on several critical tasks at once.
  • False precision in long-range plans, with exact dates for work months away.

Gantt charts are closely related to the PERT chart, which emphasizes dependencies and uncertainty in durations. They support dependency management, resource planning and rolling wave planning, and are standard in PPM software.