Project Management Stack Exchange is a question and answer site for project managers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If they are, is it simple to use them with theses methods? Have you some use cases to present?

share|improve this question
up vote 20 down vote accepted

Yes and no (I bet you love this answer)

Agile programming methodology usually deals with pretty short periods of time (e.g. a two-week sprint), during which there is also a large amount of flexibility on what tasks should be performed in what order. So on the scale of single team, I say no - gantt is not useful.

However, on the scale of larger project involving several teams working concurrently it starts showing it's usability. On this scale you deal with more long term planning, you need to manage several teams (and in fact, some of them might be working agile, while others might be using different methodologies). So on this 'strategic' sort of level it can be useful.

share|improve this answer
I agree with Mchl. I find Gantt charts only useful for the higher level planning and not the detailed planning which agile handles beautifully in my opinion. – NomadAlien Feb 8 '11 at 10:55
I agree, but I still find a good Kanban board more useful at that level. If Gantt charts have any place in the world though, it is at the enterprise, x-team level. – Andrew Clear Sep 27 '13 at 16:27
I agree. Not only is the Gantt useful for high level planning, I use them to gain budgetary approval for additional developers and resources. Its much easier to justify those things with a high level Gantt chart in-hand – Jama22 Mar 7 '14 at 15:24

Yes - provided you are talking about Feature Gantt charts and not resource Gantt charts. Feature Gantt charts, get you and your organization focused on the work and not on the workers. Because most of the world knows how to read a gantt chart, it can be very helpful in communicating widely about your progress and priority.

In comparison, burn-down and cumulative flow charts require an education for most folks. Now the burn-down and cumulative flow charts are much more helpful for steering your agile teams and work in process.

share|improve this answer

Not at all!

The mindset (based on predictive process control, theory X) for which Gantt are invented as a tool are totally incompatible with the agile mindset (empiric process control, theory Y).

Read this post by Jeff Sutherland (co-inventor Scrum) why Gantt chart were banned in the first Scrum sprints!

share|improve this answer

If a projects has a beginner and an end then it could be represented in a Gantt chart.

Also, a Gantt could represents task measured in hours.

Don't forget that AGILE methodology could be adopted in the design/implementing/supporting level, however it is not common to see other section of the business adopting it. For example, a Agile Team can show to the Business/Finance Team, a Burn Down chart.

share|improve this answer

Gantt charts are not compatible with Scrum because in scrum dependencies of task are not fixed i.e it keeps on changing which in result can increase the complexity of gantt chart. So, I suggest not to use gantt charts in scrum - Avinav

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.