What Is a Gantt Chart? Tasks, Dependencies and the Critical Path
By the end of this lesson you'll be able to:
- Read a Gantt chart: bars, dependencies, milestones and slack
- Find the critical path and explain why it sets the end date
- Shorten a schedule by changing the right tasks
Quick answer: what is a Gantt chart?
A Gantt chart is a bar chart of a project schedule: each task is a bar on a timeline, the length of the bar shows how long the task takes, and arrows show which tasks depend on others. In this Kanbanchi lesson you build one, find its critical path and see how Hoover Dam finished early.
Gantt chart basics in 8 slides
One idea per slide. Use the buttons, the dots or your arrow keys. The full text of every slide is right below the player.
Lesson 6 slides
8 slides
The full lesson: how a Gantt chart works
What is a Gantt chart?
A Gantt chart is a bar chart of a project schedule: each task is a bar on a timeline, the length of the bar shows how long the task takes, and arrows show which tasks depend on others. It answers three questions at a glance: what has to be done, in what order, and when. It is named after Henry Gantt, who charted work against time around 1910 to 1915; if you are curious about the name itself, see where the name Gantt comes from.
A Gantt chart is a planning tool for the planning phase of the life cycle and a tracking tool for monitoring and controlling. It turns the task list from the project management process into a picture that everyone can read, from the team to the sponsor.
The example used in this lesson: a 14-day website project, with the critical path in red.
Bars: tasks on a timeline
Each row is a task. Where the bar starts is the start date, and its length is how long the task takes. Dates run along the top or bottom, so you can read the whole schedule from left to right. Many tools also show who owns each task and how much of it is done, for example by filling part of the bar.
Dependencies: what waits for what
A task dependency is a link between two tasks; in the most common type, finish-to-start, one task cannot start until the other has finished. On the chart they are arrows from the end of one bar to the start of the next. In the example, the site cannot be built until the pages are designed, and testing cannot start until the copy is loaded. Dependencies are what turn a list of bars into a real schedule: move one task, and every task that depends on it moves too.
Milestones: key moments
A milestone is a point in the schedule that marks a key event, such as an approval or a launch, and has no duration of its own. They show as diamonds, such as "Launch" or "Design approved". Milestones are the dates stakeholders care about, so they are a good way to report progress without walking through every task.
The critical path
The critical path method (CPM) is a scheduling technique that finds the longest chain of dependent tasks; that chain sets the shortest possible project duration, and any delay on it delays the whole project. In the example, the path runs through the brief, design, build, loading the copy and testing: 14 days. That is why the critical path is the first thing a project manager looks at when a deadline is tight: shortening any task on it shortens the project, and shortening anything else does not.
Slack: room to slip
Slack, also called float, is how long a task can slip without delaying the end of the project. Writing the copy has 6 days of slack in the example: it can start late or take longer without moving the launch. Tasks on the critical path have zero slack. Slack is useful, but it is shared: if a task uses up its slack, it joins the critical path.
How to make a Gantt chart in 5 steps
List the tasks, estimate each one, link the dependencies, add the milestones, then find the critical path.
- List the tasks. Use the work breakdown from planning: tasks of a few days each.
- Estimate each one. Ask the person who will do the work.
- Link the dependencies. For each task, ask what has to finish before it can start.
- Add the milestones. Approvals, handovers and the launch.
- Find the critical path. Most Gantt chart tools highlight it for you; protect those tasks first.
Plan vs actual
Save the approved schedule as the baseline, then draw actual progress next to it. The gap shows you where the project is drifting. A baseline is the approved version of the scope, schedule and budget that actual progress is measured against. Kanbanchi's Great Projects series draws famous projects exactly this way, as planned and actual bars, and the Kanbanchi Gantt chart tool does the same for your own project, straight from the cards on your board. When you do need to choose between a timeline and a board for day-to-day work, the Gantt vs kanban guide compares the two.
Case study: Hoover Dam, the critical path pulled forward
Hoover Dam is a project you can read straight off its Gantt chart: a few long phases in sequence, one hard interim deadline, and a planned and an actual bar that end more than two years apart. All facts below come from Kanbanchi's Great Projects page on Hoover Dam.
Great Projects case study
Hoover Dam, 1931 to 1936
Energy · Boulder City, Nevada / Black Canyon, United States
The plan: seven years and one hard interim date
Hoover Dam was authorized by the Boulder Canyon Project Act, which President Coolidge signed on Dec 21, 1928. The act appropriated $165 million for the whole project, which also covered Imperial Dam and the All-American Canal. Six Companies, Inc., a joint venture of western construction firms, submitted the lowest of three valid bids, at $48,890,955, and had seven years from Apr 20, 1931 to complete the work. The schedule had one hard interim date: the river diversion tunnels had to be finished by Oct 1, 1933, because nothing else in the canyon could start until the Colorado was out of the way.
The critical path, pulled forward
Diversion was the first link in the chain: cofferdams, excavation and concrete all depended on it. The river was diverted into the two Arizona tunnels on Nov 13, 1932, almost eleven months before the contract deadline. On a Gantt chart, that is the first bar on the critical path finishing early, and every bar after it moving left: the cofferdams, the excavation and everything after them started almost a year earlier than the contract required.
The longest bar: concrete placement
The first concrete went in on Jun 6, 1933 and the last on May 29, 1935. To stop the mass from cracking as it cured, it was poured in blocks cooled by embedded steel pipe, which allowed placement rates of 10,462 cubic yards in one day. Kanbanchi's page calls this turning concrete placement from a waiting game into a production process.
Plan vs actual at the finish
President Franklin D. Roosevelt dedicated the dam on Sep 30, 1935. All features were completed by Mar 1, 1936, when the dam was turned over to the federal government more than two years ahead of schedule. A 1939 federal survey put the expenditure at nearly $140 million. The speed had a human cost: 112 deaths were reported in connection with construction. The page also notes that its sources do not document which scheduling tools the site office used, but the job's structure, a few long sequential phases tied to one interim deadline, is exactly what a Gantt chart is designed to show.
What this shows about Gantt charts
- Find the enabling task, the first bar on the critical path, and attack it first: finishing it early moves every later task.
- A milestone with a hard date, like the diversion deadline, belongs on the chart as a diamond everyone can see.
- Drawing planned and actual bars side by side shows at a glance where a project is ahead or behind.
Source: Hoover Dam: planned vs actual cost and schedule, Kanbanchi Great Projects (with the original sources listed on that page).
Exercise: build the schedule and hit the deadline
An interactive Gantt chart. Change the task lengths and see the end date, the critical path and the slack update instantly.
Build the schedule: hit a 12-day launch
The client wants the site live on day 12, not day 14. Change the number of days for any task, as if you could add help or cut scope, and watch the chart, the end date and the critical path update. Feedback appears after every change.
Worked example
The chart starts with the plan from this lesson: 14 days, with the critical path through the brief, design, build, loading the copy and testing. If you cut "Write the copy" from 3 days to 1, nothing moves, because it has 6 days of slack. Cut "Build the site" from 5 days to 3 instead, and the launch moves from day 14 to day 12.
Write the briefStarts on day 0Day 0 to 2, critical
Design the pagesAfter: Write the briefDay 2 to 6, critical
Write the copyAfter: Write the briefDay 2 to 5, 6 days slack
Build the siteAfter: Design the pagesDay 6 to 11, critical
Load the copyAfter: Write the copy, Build the siteDay 11 to 12, critical
Test and fixAfter: Load the copyDay 12 to 14, critical
LaunchAfter: Test and fixDay 14
Knowledge check: Lesson 6
Five questions on this lesson. Get at least 4 right to complete Lesson 6 and move your course progress forward. Each answer comes with an explanation.
Key takeaways
- A Gantt chart shows tasks as bars on a timeline, with dependencies as arrows and milestones as diamonds.
- The critical path is the longest chain of dependent tasks; it sets the end date.
- Tasks with slack can slip without moving the end date, until the slack runs out.
- Save the approved schedule as a baseline and compare actual progress with it.
Try it on a real board: a Gantt chart in Kanbanchi
Kanbanchi, the task and project management app that works inside Google Workspace, turns the cards on your board into a Gantt chart:
- Create a board and add a card for each task from the exercise above.
- Give every card a start date and a due date.
- Open the Gantt chart view and link the dependencies by dragging from one bar to the next.
- Mark the launch card as a milestone.
- Move a bar and watch the dependent tasks move with it.
This step is optional. The course works without an account, and your progress does not depend on it.
Gantt chart: FAQ
What is a Gantt chart used for?
To plan and track a project schedule. It shows each task as a bar on a timeline, which tasks depend on others, the key milestones and the critical path, so you can see what has to happen when and what a delay would affect.
What are the parts of a Gantt chart?
Task bars on a timeline, dependency arrows between tasks, milestones shown as diamonds, and often the critical path highlighted, owners, and progress shown inside the bars.
What is the critical path in a Gantt chart?
The critical path is the longest chain of dependent tasks. It sets the shortest possible project duration, and any delay on it delays the whole project. Tasks off the critical path have slack.
Can I use a Gantt chart for agile projects?
Yes, at a high level. Agile teams often keep a Gantt chart for milestones, releases and dependencies on other teams, and use a board for the day-to-day work inside each cycle.