Do I need special software for a Gantt chart?

No. A spreadsheet draws one adequately for a small project, and every scheduling tool draws one from a task list with dependencies. The tool matters less than whether the bars come from a breakdown structure or from a blank calendar.

How often should the chart be updated?

As often as progress is reported, weekly for most projects, and always against a kept baseline so that re-planning is visible. A chart updated without a baseline can be kept looking on track indefinitely, which is its most dangerous property.

Is a Gantt chart useful for agile teams?

Within a team, rarely; a board and a burn-down show flow and progress better. Across several teams working toward a fixed date, a chart at the level of releases and milestones is often the only view a steering group can read, and agile programmes that refuse one on principle lose the argument about the date.

Gantt Chart

Also: Gantt, bar chart schedule, timeline chart, project timeline

A Gantt chart is a schedule drawn as horizontal bars against a calendar, one bar per activity, with dependencies drawn between them and progress shown along each bar.

Our take. A Gantt chart is a communication device and is mistaken for a planning method. It shows a plan beautifully and creates one badly, because drawing bars invites people to fill the calendar rather than to decompose the work. Build the breakdown structure and the dependency network first, and let the tool draw the bars from them; a chart drawn first is a picture of hope.

The chart's virtue is that anyone can read it. Time runs left to right, each activity is a bar from its start to its end, arrows show which activities wait for which, and a shaded portion of each bar shows how far it has got. A sponsor sees at a glance what is happening this month, what is late, and what the late thing will push. No other project document communicates so much so quickly to people who will not read a plan, which is why every scheduling tool produces one and every steering meeting has one on the wall.

The chart shows well	The chart hides
When each activity starts and ends	Why it takes that long, and who estimated it
Which activities depend on which	How confident anyone is in the dependency
Progress along each bar	Whether the remaining work is the hard part
The critical path, when highlighted	The near-critical paths that will become it
What is late	What was quietly re-planned last month so that nothing looks late

The failure mode is drawing it first. A blank chart invites bars, bars invite dates, and dates arrive before anyone has asked what the work is. The result is a schedule in which the activity called build software is a twelve-week bar because twelve weeks were available, with no breakdown beneath it and no way to know in week six whether it is half done. The disciplined order is scope, then breakdown structure, then dependencies and estimates, then the chart generated from those, so that every bar is a work package somebody owns and its length is an estimate somebody made.

Agile teams use the chart less, since an iteration of fixed length and chosen scope has no long bars to draw and a burn-down or a board shows the same progress better. Programmes coordinating several teams toward a date use it again, at the level of releases and milestones rather than tasks, because it remains the only picture a steering group can read in a minute. The certifications at the entry level ask what the chart shows; the professional ones ask what a manager should conclude from a specific one.

In practice

A programme office maintains a Gantt chart of eleven hundred lines for a two-year system replacement, updated weekly by a planner who moves bars to match what people report. In the steering meeting the chart shows everything on track. In the corridor, engineers say the data migration is a year behind. Both are true: the migration bar has been re-planned every week to end just before the go-live bar, and its length has grown from four months to sixteen without a single day of visible lateness. The fix is a baseline: the original bars kept in grey behind the current ones, so that the chart shows movement as well as position. The next steering meeting is uncomfortable, and honest.

Often confused with

Critical Path: The critical path is calculated from the dependency network and can be highlighted on the chart. The chart is a drawing; the path is arithmetic, and a chart drawn without a network has no path to show.
Work Breakdown Structure (WBS): The breakdown structure is the hierarchy of work with no dates. The chart is those pieces placed on a calendar. Chart before structure produces bars nobody can estimate.
Kanban: A Kanban board shows work flowing through stages right now, with no calendar. A Gantt chart shows work planned against dates. One is about flow, the other about schedule, and teams often keep both.

Key takeaways

→The chart communicates a plan to people who will not read one; generate it from the plan rather than drawing it first.
→Keep the baseline visible so the chart shows movement, not only position.
→Every bar should be a work package with an owner and an estimate.

More courses from these shelves

A rotating selection from the course directory, drawn from the subcategories where this concept is taught rather than picked for it. Details, price and the provider link are on the course page.

FAQ

Do I need special software for a Gantt chart?: No. A spreadsheet draws one adequately for a small project, and every scheduling tool draws one from a task list with dependencies. The tool matters less than whether the bars come from a breakdown structure or from a blank calendar.
How often should the chart be updated?: As often as progress is reported, weekly for most projects, and always against a kept baseline so that re-planning is visible. A chart updated without a baseline can be kept looking on track indefinitely, which is its most dangerous property.
Is a Gantt chart useful for agile teams?: Within a team, rarely; a board and a burn-down show flow and progress better. Across several teams working toward a fixed date, a chart at the level of releases and milestones is often the only view a steering group can read, and agile programmes that refuse one on principle lose the argument about the date.

Sources

The primary text this definition rests on. Read it before you trust ours.

Project Management Institute, Practice Standard for Scheduling, Third Edition (2019)
Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide), Seventh Edition (2021)

Last reviewed 13 September 2026 · Getting Digital

Gantt Chart

In practice

Often confused with

Key takeaways

More courses from these shelves

Agile & Scrum: Interview Preparation with Questions, Answers

Hotel Management Strategic Operations

Healthcare Project Leadership 101

Operations Management: Inventory Management

The Complete Agile & Scrum Project Management Course

Strategic planning using ancient wisdom and visual mapping

FAQ

Sources