If they are, is it simple to use them with theses methods? Have you some use cases to present?
Tell me more
×
Project Management Stack Exchange is a question and answer site for
project managers. It's 100% free, no registration required.
|
|
|
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. |
|||||
|
|
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. |
|||
|
|
|
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! |
||||
|
|
