- June 28, 2020
- Posted by: Houssam Hawwa
- Category: Blog
Gantt chart is a type of bar planning that shows the project schedule. Gantt charts show the starting and ending dates of the sub- elements and summarize the project’s elements. The sub-components and component summary compose the project work system analysis. Some of Gantt’s independent schemes (example: network precedence) also show the relationships between activities. Gantt charts can show the current state of the schedule using shadows by percentage of completion of work and longitudinal line representing the day.
Although, it is considered a common graphic technique today, Gantt charts were considered revolutionary when they were introduced. In recognition of the contributions of Henry Gant, the Henry Lawrence Ghent Medal is awarded for outstanding achievement in the field of administration and community service. This chart is also used in information technology to represent the collected data.
The historical development
The first known Gantt chart was drawn up in 1896 by Carol Ademike, who described it as a time map. Ademike did not publish his chart until 1931, however, and only then in a language that was not very popular in the West. The chart, for example, now bears the name/ Henry Gant/ (1861-1919), who designed the chart for him between 1910-1915 and popularly spread in the West.
In the 1980s, computers facilitated the creation and editing of detailed Gantt maps. These office applications were primarily intended for project managers and project organizers. In the late 1990s and early 2000s, Gantt charts became a common feature of web applications, including cooperative group programs.
Advantages and limitations
Gantt charts became a general technique for representing phases, activities and analyzing of project work systems, as they became understood by a wide audience.
Those who compare Gantt charts with project designs fall into a common mistake of trying to define project work systems at the same time as they define schedule activities. This practice makes it very difficult to follow the rule 100%. Instead, project work systems should be set to track 100% of the rule, then design the project schedule.
Although the Gantt chart is useful and valuable for small projects within the limits of a single sheet or screen, it can become completely impractical with projects that exceed thirty activities. Larger Gantt charts may not be suitable because most computers display them. A related criticism was that the communication of Gantt charts of information was relatively small when viewing each region separately. And that projects are often too complex to be transferred effectively with the Gantt chart.
Gantt charts represent only a portion of three dimensions of projects, mainly because they focus on schedule management. Moreover, Gantt charts do not represent the project size or the relative size of the work elements, and therefore it is easy to miscalculate the importance of a state beyond the schedule. If two projects with the same number of days are behind schedule, the larger project has more influence on resource use, but Gantt charts do not represent this difference. Although project management software can show schedule dependencies as dividing lines between activities, displaying a large number of dependencies may produce a disorganized or unreadable graph.
Because the horizontal lines of Gantt chart have a fixed height, it can misrepresent the workload for the project’s time frame (resource requirements). All the activities of Gantt chart show the amount of work planned as a fixed quantity. In fact, many activities (especially the summarized elements) have focused action plans at the beginning or at the end, and so the Gantt charts with the percentage shaded method may be a bad connection to the real performance state of the table.