Gantt Chart: Definition, Example & How to Make One [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on September 18, 2026
9 min read
A project schedule can be a wall of dates and dependencies that no one outside the planning meeting can read — or it can be a single chart anyone understands in ten seconds. The Gantt chart is how you get the second one: a row of bars that shows, at a glance, what is being worked on, when, and whether it is on time. It has been the default picture of a project plan for over a century, and it still is. This guide explains the Gantt chart in full — what it is, a clear example, its key elements, how to make one, how to read it, and its benefits and limits.
What is a Gantt chart?
A Gantt chart is a horizontal bar chart that displays a project's schedule against a timeline. Each task is a row, and each row has a bar whose position and length show when the task starts, how long it takes, and when it finishes. Read top to bottom, the chart is the whole project; read left to right, it is the passage of time.
It is named after Henry Gantt, who popularized it around 1910–1915 (the Polish engineer Karol Adamiecki had drawn a similar chart, the harmonogram, a decade earlier). More than a century on, it remains the single most recognizable way to show a plan, because it answers the two questions everyone has about a project — what is happening and when — in one glance. Every modern scheduling tool, from a spreadsheet to dedicated software, can produce one.
Elements of a Gantt chart
A complete Gantt chart is more than bars on a timeline — a handful of elements work together to turn it into a working schedule. These are the parts a well-built Gantt chart shows:
| Element | What it shows |
|---|---|
| Task list | The activities to be done, listed down the left side |
| Timeline | The time axis across the top, in days, weeks, or months |
| Task bars | A bar per task, positioned and sized by its start, duration, and end |
| Dependencies | Links showing which tasks must finish before others can start |
| Milestones | Key checkpoints or events, usually drawn as diamonds |
| Progress | How much of each task is complete, often shaded inside the bar |
| Owners / resources | Who is responsible for each task |
Not every chart shows all of these — a quick plan may be just bars and a timeline — but the more of them are present, the more the Gantt chart works as a live scheduling tool rather than a static picture.
Ready to take the next step in project management?
200,000+ Professionals Taught by Our Instructors
Gantt chart example
Here is a simple Gantt chart for a small software project, with five tasks across an eight-week timeline. The staggered bars show the sequence — design cannot start until requirements are underway, testing waits on development — and the diamond marks the launch milestone:
In this example, requirements are complete (the fully shaded bar), design is about 60% done (the partly shaded bar), and development and testing are still ahead. Anyone can see in a moment that the project is in its design phase, that development is the longest task, and that everything points toward a launch in week eight.
How to make a Gantt chart
Building a Gantt chart is mostly about getting the schedule right first; plotting it is the easy part. The steps:
- List the tasks. Break the work down into the activities the project needs — ideally from the work breakdown structure — and list them down the left.
- Estimate durations. Give each task a start and a duration, so it has a length on the timeline.
- Set the dependencies. Decide which tasks must finish before others can start, so the bars fall into the right sequence.
- Add milestones. Mark the key checkpoints — approvals, phase ends, the go-live date — as milestones.
- Plot and assign. Draw each task as a bar on the timeline, assign an owner, and — once work begins — shade in progress as tasks advance.
You can build one in a spreadsheet, but dedicated project or scheduling software does the heavy lifting: it recalculates the bars automatically when a date or dependency changes, which is what keeps the chart accurate as the project moves.
How to read a Gantt chart
Reading a Gantt chart is a matter of scanning in two directions. Down the rows tells you what the project involves; across the timeline tells you when each piece happens and how the pieces overlap.
A few things to look for:
- Sequence and overlap: bars that follow one another are sequential; bars that share the same weeks run in parallel.
- Dependencies: the links between bars show what is waiting on what — and where a slip will cascade.
- Progress against today: compare the shaded portion of each bar to the current date; a task less complete than it should be is falling behind.
- Milestones: the diamonds are the dates stakeholders care about most, so check whether the work leading to each is on schedule.
Apply that to the example above and the chart reads itself. Requirements and Design overlap in week 2, so they run partly in parallel; Development cannot start until Design ends in week 4, which makes that link the one to watch; and everything funnels toward the Launch diamond in week 8. If Design slips a week, the cascade is visible before it happens: Development, Testing, and the launch date all shift right together — which is precisely the conversation a Gantt chart lets you have while there is still time to act.
Benefits and limitations
Gantt charts are popular for good reasons, but they are not the right tool for every job. The trade-offs:
| Benefits | Limitations |
|---|---|
| Makes a complex schedule easy to see at a glance | Gets crowded and unwieldy on large projects |
| Shows timing, overlap, and dependencies together | Dependency lines get hard to follow as tasks multiply |
| Tracks progress against the plan in real time | Does not show schedule float or slack well |
| Communicates the plan clearly to any audience | Needs updating and re-baselining when the plan changes |
The practical takeaway: a Gantt chart is the best all-round view for planning, communicating, and tracking a schedule, but on a large or highly interdependent project it works best alongside a network diagram.
Do agile projects use Gantt charts?
Less than predictive projects do, and for a structural reason: a Gantt chart presumes you know the tasks and dates far enough ahead to draw them, which is exactly what agile declines to promise. Inside a sprint, teams track a board and a burndown, not bars on a calendar. Where Gantt charts do earn a place in agile organizations is one level up — release plans, cross-team dependencies, and fixed external dates (a trade show, a regulatory deadline) sit comfortably on a timeline even when the work inside each sprint stays adaptive. In hybrid projects it is common to see both at once: a Gantt chart for the predictive backbone, a board for the agile stream.
Who invented the Gantt chart?
The chart is named for Henry Gantt, the American engineer and management consultant who popularized it in the 1910s — but the idea is slightly older. Around 1896 the Polish engineer Karol Adamiecki devised the harmonogram, a near-identical bar view of work against time, publishing in Polish and Russian, which is why the English-speaking world learned the format from Gantt instead. Gantt's version spread through American industry and wartime shipbuilding, and it went on to schedule projects as large as the Hoover Dam and the US interstate highway system.
What kept it alive for a century is also what once made it painful: a hand-drawn wall chart had to be redrawn every time the plan changed, so early Gantt charts rewarded stable plans. Scheduling software removed that cost — bars, links, and progress now update in seconds — and turned the Gantt chart from a drafting exercise into the default working view of nearly every scheduling tool.
Gantt charts in project management
In project management, the Gantt chart is the everyday working view of the project schedule — the format teams plan in, report from, and track against, and one of the most widely used tools in the Association for Project Management's toolkit. In formal terms it is a bar chart, one of several ways to present a schedule, and it sits alongside a few relatives worth knowing. A milestone chart strips the schedule down to milestones only, for executive reporting; a network diagram or PERT chart shows the dependencies and critical path as a flow of connected activities rather than bars on a calendar.
For exam candidates, that placement is the thing to remember: the Gantt chart is the bar-chart presentation of the schedule, best for tracking and communicating, while the network diagram is where the scheduling logic and critical path live. Our PMP Complete Study Guide — the most complete on the market — covers how these schedule views fit together, so you know which one a given situation calls for.
Ready to take the next step in project management?
200,000+ Professionals Taught by Our Instructors
Frequently asked questions
What is a Gantt chart?
A Gantt chart is a horizontal bar chart that shows a project's schedule against a timeline. Each task is a row with a bar whose position and length represent its start date, duration, and end date. Together the bars give a single, at-a-glance picture of what work happens when across the life of the project.
What are the elements of a Gantt chart?
The key elements are the task list down the left, the timeline across the top, a task bar for each activity, dependencies linking tasks that must happen in order, milestones marking key checkpoints, progress showing how much of each task is complete, and the owner or resource assigned to each task. Simpler charts may show only some of these.
What is an example of a Gantt chart?
A simple example is a software project with tasks such as requirements, design, development, and testing laid out as bars across an eight-week timeline, plus a launch milestone. The bars are staggered to show sequence — design starts after requirements, testing after development — and shading inside each bar shows how far along it is.
How do you make a Gantt chart?
List the project's tasks, estimate a start and duration for each, set the dependencies that determine their order, add milestones for key checkpoints, then plot each task as a bar on a timeline and assign owners. Most people use spreadsheet or project management software, which redraws the bars automatically when dates or dependencies change.
What are the benefits and limitations of a Gantt chart?
The benefits are that it makes a schedule easy to see, shows timing and dependencies together, tracks progress in real time, and communicates the plan to any audience. The limitations are that it becomes crowded on large projects, dependency lines get hard to follow, it does not display float well, and it needs updating whenever the plan changes.
Is there a free Gantt chart template?
Yes. Spreadsheet programs such as Excel and Google Sheets offer free Gantt chart templates, and many project management tools include one at no cost. A template gives you the task list, timeline, and bar formatting already set up, so you only need to enter your own tasks, dates, and dependencies.
Are Gantt charts on the PMP exam?
Yes, though lightly. The PMP exam expects you to know a Gantt chart is a bar-chart presentation of the schedule, useful for tracking and communicating progress, and to distinguish it from a milestone chart (milestones only) and a network diagram (which shows dependencies and the critical path). It is more a vocabulary and comparison point than a heavily tested calculation.
Project Milestones: Definition, Examples & Chart [2026]
Project milestones explained: what they are, examples by phase, milestone vs. task vs. deliverable, the milestone chart, and how they are tested on the PMP.
Precedence Diagramming Method (PDM): The 4 Types [2026]
The precedence diagramming method (PDM) builds a project network from four dependency types: finish-to-start, start-to-start, finish-to-finish, start-to-finish.
Project Network Diagram: Types & How to Draw One [2026]
A project network diagram maps activities and their dependencies to reveal the critical path. What it is, activity-on-node vs arrow, and how to build one.
