artifactDelivery & agility

Gantt Chart

A time-scaled visual schedule that represents project activities as horizontal bars and can show dates, durations, milestones, dependencies, and progress.

Download Markdown (.md)

01What it means

A Gantt chart places work on a calendar, with each bar showing an activity’s planned start, finish, and duration. Depending on the tool and audience, it may also display workstreams, milestones, dependencies, owners, baseline dates, progress, and critical activities. It is a view of the schedule, not proof that the underlying plan is complete or feasible.[1][2][3]

Activities placed on a shared calendar Bars reveal duration, overlap, sequence, and milestone timing
Period 1Period 2Period 3Period 4
DiscoverResearch
DefineDecision milestone
BuildIncremental delivery
ValidateEvidence + correction
ReleaseMilestone

Illustrative schedule only. A Gantt view represents a plan; it does not prove estimates, dependencies, resources, or feasibility are sound.

02Why it matters

The chart makes timing and coordination easier to discuss than a dense activity table. Teams can see overlapping work, important handoffs, milestones, and likely congestion, while stakeholders gain a shared view of what should happen when. Comparing current and baseline bars can also make slippage and approved changes visible.

03When to use it

Use a Gantt chart when work must be coordinated across dates, teams, suppliers, or phases. Create an executive view for major milestones and a more detailed operational view where useful. Keep distant or uncertain work at an appropriate level of detail, particularly in iterative delivery environments.

04How it works

  1. Define activities and milestones from the project scope, with clear completion criteria and responsible owners.
  2. Estimate durations, apply working calendars, and connect genuine dependencies rather than arranging bars decoratively.
  3. Schedule activities, resolve obvious resource conflicts, and identify critical or constrained work.
  4. Baseline the approved schedule and choose a reporting level suited to the audience and decisions.
  5. Update actual dates, remaining durations, forecasts, and approved changes so the chart reflects current evidence.

05A practical example

Example

A payment-platform launch chart groups security approval, integration, merchant pilot, support readiness, and rollout. Milestones mark approval and go-live decisions; dependency lines show that pilot evidence precedes rollout. When certification slips, the chart exposes the affected launch path and gives leaders a basis for considering phased release.

06Where it breaks

A visually tidy chart can hide weak estimates, missing scope, incomplete dependency logic, or overloaded resources. Large Gantt charts become unreadable, and exact-looking dates may overstate confidence. They are less useful for day-to-day flow than a team board and should not replace network analysis, risk management, or collaborative planning.

Common mistakes

  • Drawing bars first and treating their arrangement as a validated schedule.
  • Showing excessive detail or precision to audiences who need decisions, not noise.
  • Updating percent complete without revising remaining duration and forecast dates.
  • Using the chart as a fixed promise after assumptions or scope have changed.

07Sources

  1. Programme and Project PlanningNorthern Ireland Department of Finance · Government project guidanceProgramme and Project Planning
  2. Garden Communities Toolkit: Project ManagementUK Ministry of Housing, Communities and Local Government · Government delivery guidanceGarden Communities Toolkit: Project Management
  3. GAO Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · Government best-practice guideGAO Schedule Assessment Guide: Best Practices for Project Schedules
View saved topics

Start typing to search titles, definitions, categories, and frameworks.