example of gantt charts in software engineering[click here]

gantt charts in software engineering

What is Gantt Charts in software engineering

A Gantt Chart is a horizontal bar lines chart developed in 1917 by Henry L. Gantt. He is an american engineer and social scientist. It is often used in process management.

Gantt Chart  is useful for tracking and reporting progress, as well as for graphically show a schedule. Gantt Chart  are commonly used to report progress because they represent an easily understood picture of project status. However, Gantt Chart  are not an ideal tool for project control.

Gantt Charts provides an graphically illustrations for a schedule that helps to plan, coordinate, and track specific task in a project. Gantt charts may be simple versions that are created on graph papers, an automated versions also created using project management tools.

Project management tool integrates the Gantt charts include PRINCE, MacProject, Microsoft Project, and Microsoft Excel.

Purpose of Gantt charts is to represent a project schedule that shows the relationship of activities over the time. These are a project management tool that can be used for representing the timing of tasks required to complete a project. Because these are easily understand and construct also, they are used by most project managers for all but the most complex projects.

Reasons to Use Gantt Charts 

These charts are convenient which means it representing schedules, appointments and events graphically . Such charts helps to members of organisation to plan activities better.
Information about WHAT is happening, WHEN is happening, WHERE is happening, and WHO  will be the present,is valuable to concerned people in the organisation.
examples of gantt charts in software engineering


  • It plots activities as bars on a time scale.
  • It indicates different activities, responsibilities, Estimates or 'planned activities' start and target dates and actual start and target dates.
  • It supports scheduling activities,coordinate activities, Evaluating progress, Reallocating resources in case of problems.


  • Providing an easily understandable overview of a project for those without any technical background.
  • These are relatively easily to create and maintain
  • Able to reflect the status of each project task at any point in time.
  • Able to represent overlapping or parallel tasks.


Post a comment