Product Operations Program ManagerBarcelona, Cataluña, Spain
I am not familiar with IT Projects. In some of my projects, a traditional Gantt chart with its beautiful waterfall lives in perfect harmony with the SCRUM board. The latter is used as a tool to ensure that deliverables are on time and to manage (small) changes in a quick and efficient manner. Saving Changes...
Drake SettsuProject Manager / BloggerHi, United States
The Gantt chart will be present. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
I'm still using Gantt chart for my projects. Saving Changes...
On "fully" agile projects within minimal external dependencies, a team might be able to shift entirely away from Gantt charts but in most cases you will either have some waterfall work packages and/or sufficient external dependencies to justify use of Gantt charts but at an appropriate level of detail and not containing redundant info relative to what is being tracked in your agile planning & work tracking tool.
For organizations involved with Agile software development there is no need for the Gantt chart.
Yet for all other organizations involved in IT projects that are outside of software development the Gantt chart is irreplaceable. Software installation, equipment rollouts, service integration, circuit upgrades, essentially everything in IT that is not software development runs on the traditional waterfall model. As long as there is waterfall, there is the Gantt chart. Saving Changes...