Gantt chart

From Wikipedia, the free encyclopedia
  (Redirected from Gantt)
Jump to navigation Jump to search

A Gantt chart showing three kinds of schedule dependencies (in red) and percent complete indications.

A Gantt chart is a type of bar chart that illustrates a project schedule, named after its inventor, Henry Gantt (1861–1919), who designed such a chart around the years 1910–1915.[1][2] Modern Gantt charts also show the dependency relationships between activities and current schedule status.

Definition[edit]

A Gantt chart is a type of bar chart[3][4] that illustrates a project schedule.[citation needed] This chart lists the tasks to be performed on the vertical axis, and time intervals on the horizontal axis.[3][5] The width of the horizontal bars in the graph shows the duration of each activity.[5][6] Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements constitute the work breakdown structure of the project. Modern Gantt charts also show the dependency (i.e., precedence network) relationships between activities. Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical "TODAY" line as shown here.

Gantt charts are sometimes equated with bar charts.[6][7]

Gantt charts are usually created initially using an early start time approach, where each task is scheduled to start immediately when its prerequisites are complete. This method maximizes the float time available for all tasks.[3]

Historical development[edit]

Although now regarded as a common charting technique, Gantt charts were considered revolutionary when first introduced.[8] The first known tool of this type was developed in 1896 by Karol Adamiecki, who called it a harmonogram.[9] Adamiecki did not publish his chart until 1931, however, and only in Polish, which limited both its adoption and recognition of his authorship.

In 1912, Hermann Schürch (de) published what would be considered Gantt charts while discussing a construction project. It appears that Schürch's charts were not notable but rather routine in Germany at the time they were published.[10][11][12] The prior development leading to Schürch's work is unknown.[13] Unlike later Gantt charts, Schürch's charts did not display interdependencies, leaving them to be inferred by the reader. These were also static representations of a planned schedule.[14]

The chart is named after Henry Gantt (1861–1919), who designed his chart around the years 1910–1915.[1][2]

One of the first major applications of Gantt charts was by the United States during World War I, at the instigation of General William Crozier.[15]

The earliest Gantt charts were drawn on paper and therefore had to be redrawn entirely in order to adjust to schedule changes. For many years, project managers used pieces of paper or blocks for Gantt chart bars so they could be adjusted as needed.[16] In the 1980s, personal computers allowed widespread creation of complex and elaborate Gantt charts. The first desktop applications were intended mainly for project managers and project schedulers. With the advent of the Internet and increased collaboration over networks at the end of the 1990s, Gantt charts became a common feature of web-based applications, including collaborative groupware.[citation needed] By 2012, almost all Gantt charts were made by software which can easily adjust to schedule changes.[16]

In 1999, Gantt charts were identified as "one of the most widely used management tools for project scheduling and control".[3]

Example[edit]

In the following table there are seven tasks, labeled a through g. Some tasks can be done concurrently (a and b) while others cannot be done until their predecessor task is complete (c and d cannot begin until a is complete). Additionally, each task has three time estimates: the optimistic time estimate (O), the most likely or normal time estimate (M), and the pessimistic time estimate (P). The expected time (TE) is estimated using the beta probability distribution for the time estimates, using the formula (O + 4M + P) ÷ 6.

Activity Predecessor Time estimates Expected time (TE)
Opt. (O) Normal (M) Pess. (P)
a 2 4 6 4.00
b 3 5 9 5.33
c a 4 5 7 5.17
d a 4 6 10 6.33
e b, c 4 5 7 5.17
f d 3 4 8 4.50
g e 3 5 8 5.17

Once this step is complete, one can draw a Gantt chart or a network diagram.

A Gantt chart created using Microsoft Project (MSP). Note (1) the critical path is in red, (2) the slack is the black lines connected to non-critical activities, (3) since Saturday and Sunday are not work days and are thus excluded from the schedule, some bars on the Gantt chart are longer if they cut through a weekend.

Progress Gantt charts[edit]

In a progress Gantt chart, tasks are shaded in proportion to the degree of their completion: a task that is 60% complete would be 60% shaded, starting from the left. A vertical line is drawn at the time index when the progress Gantt chart is created, and this line can then be compared with shaded tasks. If everything is on schedule, all task portions left of the line will be shaded, and all task portions right of the line will not be shaded. This provides a visual representation of how the project and its tasks are ahead or behind schedule.[17]

Linked Gantt charts[edit]

Linked Gantt charts contain lines indicating the dependencies between tasks. However, linked Gantt charts quickly become cluttered in all but the simplest cases. Critical path network diagrams are superior to visually communicate the relationships between tasks.[18] However, Gantt charts are often preferred over network diagrams because Gantt charts are easily interpreted without training, whereas critical path diagrams require training to interpret.[7] Gantt chart software typically provides mechanisms to link task dependencies, although this data may or may not be visually represented.[3] Gantt charts and network diagrams are often used for the same project, both being generated from the same data by a software application.[3]

See also[edit]

Citations[edit]

  1. ^ a b Gantt 1910.
  2. ^ a b Morris 1997, p. 7.
  3. ^ a b c d e f Klein 1999, p. 49.
  4. ^ Richman 2002, pp. 97, 117, 276.
  5. ^ a b Richman 2002, pp. 117, 276.
  6. ^ a b Selig 2008, p. 235.
  7. ^ a b Flouris & Lock 2012, p. 236, Chapter 12.
  8. ^ Wilson 2003.
  9. ^ Marsh 1974, p. 32.
  10. ^ Weaver 2012a, pp. 5–6.
  11. ^ Weaver 2012b, pp. 4–6.
  12. ^ Weaver 2017, pp. 6–7.
  13. ^ Weaver 2017, p. 7.
  14. ^ Weaver 2017, p. 6.
  15. ^ Clark 1922.
  16. ^ a b Flouris & Lock 2012, p. 281, Chapter 14.
  17. ^ Klein 1999, pp. 56–57.
  18. ^ Flouris & Lock 2012, p. 239, Chapter 12.

References[edit]

Further reading[edit]

External links[edit]