Jump to content

Gantt chart

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 193.63.27.196 (talk) at 14:21, 11 November 2009 (→Advantages and limitations). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

"Gantt" redirects here. For other uses, see Gantt (disambiguation).
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. Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements comprise the work breakdown structure of the project. Some 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.

Although now regarded as a common charting technique, Gantt charts were considered revolutionary when they were introduced. In recognition of Henry Gantt's contributions, the Henry Laurence Gantt Medal is awarded for distinguished achievement in management and in community service. This chart is used also in Information Technology to represent data that has been collected.

Historical development

The first known Gantt Chart was developed in 1896 by Karol Adamiecki, who called it a harmonogram. Adamiecki did not publish his chart until 1931, however, and then only in Polish. The chart is commonly known after Henry Gantt (1861–1919), who designed his chart around the years 1910–1915.[1][2][3]

In the 1980s, personal computers allowed for 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.

Advantages and limitations

Gantt charts have become a common technique for representing the phases and activities of a project work breakdown structure (WBS), so they can be understood by a wide audience.

A common error made by those who equate Gantt chart design with a shit project design is that they attempt to define the word cunt the project work breakdown structure at the same time that they define schedule activities. This practice makes it very difficult to follow the 100% Rule. Instead the WBS should be fully defined to follow the 100% Rule, then the project schedule can be designed. [citation needed]

Although a Gantt chart is useful and valuable for small projects that fit on a single sheet or screen, they can become quite unwieldy for projects with more than about 30 activities. Larger Gantt charts may not be suitable for most computer displays. A related criticism is that Gantt charts communicate relatively little information per unit area of display. That is, projects are often shuit and cuntish to fucking use u cunt considerably more complex than can be communicated effectively with a Gantt chart.

Gantt charts only represent part of the triple constraints (cost, time and scope) of projects, because they focus primarily on schedule management. Moreover, Gantt charts do not represent the size of a project or the relative size of work elements, therefore the magnitude of a behind-schedule condition is easily miscommunicated. If two projects are the same number of days behind schedule, the larger project has a larger impact on resource utilization, yet the Gantt does not represent this difference.

Although project management software can show schedule dependencies as lines between activities, displaying a large number of dependencies may result in a cluttered or unreadable chart.

Because the horizontal bars of a Gantt chart have a fixed height, they can misrepresent the time-phased workload (resource requirements) of a project, which may cause confusion especially in large projects. In the example shown in this article, Activities E and G appear to be the same size, but in reality they may be orders of magnitude different. A related criticism is that all activities of a Gantt chart show planned workload as constant. In practice, many activities (especially summary elements) have front-loaded or back-loaded work plans, so a Gantt chart with percent-complete shading may actually miscommunicate the true schedule performance status.

One way to overcome this limitation is to use a gantt chart that can show both actual and planned schedules of activities [4]. See the illustration to understand this.

See also

References

  1. ^ H.L. Gantt, Work, Wages and Profit, published by The Engineering Magazine, New York, 1910; republished as Work, Wages and Profits, Easton, Pennsylvania, Hive Publishing Company, 1974, ISBN 0879600489.
  2. ^ Blokdijk, Gerard (2007). Project Management 100 Success Secrets. Lulu.com. p. 76. ISBN 0980459907.
  3. ^ Peter W. G. Morris, The Management of Projects, Thomas Telford, 1994, ISBN 0727725939, Google Print, p.18
  4. ^ ‘’Chandoo.org’’. Gantt Charts – Project Management Using Excel
Wikimedia Commons has media related to Gantt charts.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Gantt_chart&oldid=325245820"