Focus video player for keyboard shortcuts
Auto
  • 720p
  • 540p
  • 360p
1.00x
  • 0.50x
  • 0.75x
  • 1.00x
  • 1.25x
  • 1.50x
  • 1.75x
  • 2.00x
cc

We hope you enjoyed this lesson.

Get the Project Management Basics course for more great video tutorials.

Start free trial

Cool lesson, huh? Share it with your friends

About this lesson

Understand when and how to use a Gantt chart on a project. Learn how to create a Gantt chart.

Exercise files

Download this lesson’s related exercise files.

Gantt Chart
60.9 KB Gantt Chart - Solution
77.7 KB

Quick reference

Gantt Chart 

The Gantt Chart is a project schedule tool that shows summary and detail tasks represented by horizontal bars on a schedule timeline.

When to use 

The Gantt Chart should be used on predictive projects.  It is helpful for organizing schedule planning information because of its graphical display.  However, its best use is in schedule tracking.

Instructions

The Gantt Chart is the most commonly used project schedule chart – although it probably shouldn’t be.  It is easy to create and read.  However, its major flaw is that it is based upon the assumption that all estimates of task duration are accurate.   This assumption is often false, either because of the inherent uncertainty in the work, the vagueness of the requirements, or the unpredictable availability of resources.  However, when the estimates are accurate the Gantt chart format provides great schedule perspective for the project.  It is easy to see what tasks the project team should be working on each day, and it is easy to see if adequate progress has been made by changing the color of completed tasks.  When being used for tracking progress, I always add a “time now” line on the current date of the project to indicate how much progress should have been made.

  1. List the project phases (Gantt Charts are often created one phase at a time).
  2. Within each phase list the summary level tasks and their associated detail tasks.  The summary tasks are often associated with a major project deliverable.
  3. For each task set the estimated task duration (use the units of the Gantt Chart timeline).
  4. Link the tasks that must occur in the project in a sequential manner.
  5. Either:         
    • Starting with the project start date and the first task, go forward in time plotting all the tasks on the timeline based upon their linkages; or
    • Starting with the project end date and the last task, go backward in time plotting all the tasks on the timeline based upon their linkages.
  6. Record the placement of tasks, the start date, end date, and duration on the timeline.
  7. Insert any risk mitigation changes, such as adding buffers between high risk tasks.
  8. As the project progresses, change the color of completed task bars to show they are finished.

Hints & tips

  • The Gantt Chart is the easiest project schedule chart to read and understand.
  • Start with a summary level Gantt Chart and create detailed Gantt Charts for each phase.
  • Draw a vertical line on the timeline showing “time now” and move the line along the timeline as the project progresses.  It will show what work the project team should be doing and you can easily track whether you are ahead or behind schedule.
  • Different color bars can be used to show additional information about a task, such as critical path, behind schedule, or task is complete.
  • The Gantt Chart relies on accurate and precise estimates for each activity.  Using inaccurate estimates sets false expectations because team members try to meet the estimates, even though they quickly realize that some are wrong; and stakeholders begin to doubt the credibility of the project team when the actual durations are often different from the estimates.
  • The Gantt Chart cannot be created with variable estimates.  If you have that situation either use a Network Diagram or start with the “most likely” estimate and build in a risk buffer.
  • Gantt Chart:  “A bar chart of schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates.” PMBOK® Guide

This definition is taken from the Glossary of the Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017.

Login to download
  • 00:04 Hi, I'm Ray Sheen.
  • 00:05 Let's talk about schedule planning again, and
  • 00:08 this time we'll use the Gantt chart or, as its proper name, the bar chart.
  • 00:12 >> The Gantt chart is the most commonly used chart for
  • 00:15 scheduling purposes in traditional project management.
  • 00:17 It can be used for project planning, but it is best suited for
  • 00:21 tracking progress on a project.
  • 00:23 It's actually rather clunky for planning.
  • 00:26 The Project Manage of Body of Knowledge, the PMBOK Guide, defines a Gantt chart as
  • 00:31 a bar chart of schedule information, where activities are listed on the vertical
  • 00:36 axis, dates are shown on the horizontal axis, and activity durations are shown
  • 00:41 as horizontal bars placed according to start and finish dates.
  • 00:45 This is a mouthful, but it just means that we show the activities on
  • 00:49 a calendar when they're scheduled to occur.
  • 00:52 The Gantt chart can be used with either summary level information or
  • 00:56 detailed tasks.
  • 00:57 I often use the summary level information in my Gantt chart at the beginning of
  • 01:02 a project and detailed tasks are added later, one phase at a time.
  • 01:06 The Gantt chart is ideally suited for tracking progress because it creates
  • 01:11 focus on which activities should be started and finished on any given day.
  • 01:16 The best use of a Gantt chart is daily or weekly tracking of progress,
  • 01:19 provided the estimates are accurate.
  • 01:22 This is an example of a Gantt chart.
  • 01:24 You can see the summary tasks which encompass several detailed tasks.
  • 01:29 The edges of the summary task are at the earliest start time of the earliest
  • 01:34 detailed task that is being summarized, and
  • 01:36 the latest finish time of the latest detailed task that is being summarized.
  • 01:40 The detailed task bar represents the length of time planned for
  • 01:44 the detailed task.
  • 01:45 The edges of the bar show the start and finish date for that task.
  • 01:49 Now let me take you through the steps for creating a Gantt or bar chart.
  • 01:53 First, list all your project phases in order.
  • 01:56 This will be your highest level summary tasks.
  • 02:00 Next, list the summary level activities and
  • 02:03 any known detailed task within each phase.
  • 02:05 Note that we haven't yet started to put down any dates.
  • 02:08 Just list the tasks and activities that are known at this time.
  • 02:12 Your work breakdown structure is very helpful for doing this.
  • 02:15 Third, estimate the duration for each of those tasks,
  • 02:18 the estimates cannot be arranged, they must be a finite value of time.
  • 02:23 Fourth, link any of the tasks that must occur in a sequential manner.
  • 02:27 Link the end of the first task to the beginning of the second task
  • 02:32 in the sequence.
  • 02:33 Now we can finally set dates.
  • 02:35 You can either start from the beginning date and go forward in time or
  • 02:39 you can start from the end date and go backward in time.
  • 02:42 If starting from the beginning of the project, set the start date for
  • 02:46 all the tasks that can begin immediately on the start date of the project or phase.
  • 02:51 Each of these tasks will end based upon their planned duration.
  • 02:55 For the tasks that are linked,
  • 02:56 start them as soon as the predecessor task is complete.
  • 02:59 Continue until you have planned all the tasks.
  • 03:02 The latest end date for a task is when the project will end.
  • 03:06 If working from the end date backwards, set the finish date for all tasks that
  • 03:11 are at the end of the sequence, creating a final delivery of that project or phase.
  • 03:16 Set their start date by subtracting the duration from the finish date.
  • 03:20 This start date is now the end date for all the preceding tasks.
  • 03:25 Continue with all the tasks and sequences until you have planned all the tasks.
  • 03:30 The earliest start date for the phase or
  • 03:32 project is the earliest start date of any task.
  • 03:35 This step can get very ugly on a large project if doing it manually,
  • 03:39 which is why I often break things into phases.
  • 03:42 Many project management software applications will do this for
  • 03:46 you once you provide the links between tasks and the task durations.
  • 03:50 Finally, plot the calculated start and end date of the tasks on the calendar.
  • 03:54 Step seven isn't really a planning step.
  • 03:57 It's actually a tracking step.
  • 03:59 Once all the activities have been placed on the Gantt chart,
  • 04:02 the project schedule status can be easily checked.
  • 04:04 For any date, the Gantt chart will show which tasks should have been finished and
  • 04:08 what tasks should be underway and how much progress should have been made on those.
  • 04:12 All the other tasks are unstarted.
  • 04:15 Some hints and tips with Gantt charts.
  • 04:18 The Gantt chart is the easiest project schedule chart to read and understand,
  • 04:22 which is one of the reasons why it is so popular.
  • 04:25 You can use different colored bars to show additional information, such as critical
  • 04:30 path, behind schedule condition, or who was responsible for the task.
  • 04:34 But now for the huge weakness of the Gantt chart with respect to doing projects.
  • 04:38 The Gantt Chart relies on accurate and precise duration estimates for
  • 04:42 each activity.
  • 04:43 If the estimates are wrong, the entire Gantt can be wrong.
  • 04:47 This leads to problems with team members and stakeholders who make plans for
  • 04:51 other projects or business activities based upon the expectation that the Gantt
  • 04:56 chart schedule is accurate.
  • 04:58 But on almost all projects, some task estimates are uncertain.
  • 05:02 That is the nature of project work as compared to process work.
  • 05:06 Processes are usually stable,
  • 05:08 well defined work streams that can be precisely estimated.
  • 05:12 Projects often contain some unique or different tasks that are highly variable.
  • 05:17 So when working with projects that contain many variable tasks or activities,
  • 05:21 I recommend using the Network Diagram schedule chart or
  • 05:24 a Kanban chart which will be covered in other lessons.
  • 05:28 A final tip is to start with a summary level Gantt chart.
  • 05:31 It often will be accurate because of the uncertainties and
  • 05:35 detailed tasks can cancel each other out.
  • 05:37 As a phase starts, I then create the detailed Gantt chart for just that phase.
  • 05:42 Hopefully, some of the uncertainty is now resolved.
  • 05:46 >> As I said at the beginning of this lesson,
  • 05:48 the Gantt Chart is the most commonly used project scheduling tool.
  • 05:51 While often used for planning, we'll see its real power when we discuss this tool
  • 05:56 during our project tracking and control lessons.

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course