True Confessions of a PM: Rant Against the Gantt
True confessions of a PM: I don't get Gantt charts. I've blogged before about how I'm not a visual person, so I'm sure that has something to do with it. Maybe my readers can educate me about how the Gantt chart adds value, but I frankly don't see it. I can't tell you how many hours of my life I've spent resizing MS Project schedules to print in a desperate, but ultimately futile, attempt to confine a multi-year schedule to an 8 x 11 friendly format.
Until now, I've kept my opinions on Gantt charts quietly to myself. But I can now step into the light, because, on a recent engagement, a senior executive's request for a Gantt chart inspired a collective groan from the project team. Not surprisingly, the typical grumblings about why this information was being requested ensued. The project team just wanted to be left alone to do their work. But then, one of the team members piped up, "Who even needs a Gantt chart anyway?" Bingo.
I don't dispute the need to keep senior executives informed of project progress. Maybe the project team wants to be left alone to do the work, but there's no such thing as working alone when you're on a change engagement. You'll quickly be alone--with no work to do--if the project sponsors aren't aware of the project's benefits. They'll pull the plug.
While I don't dispute the need for updates, what I do dispute is the tired Gantt chart view that we churn out without thinking. When a project sponsor asks for a Gantt chart, consider what he or she really wants to see. A 45-page printout of long bars extending into oblivion? Unless your project is simple enough that this type of view can be confined to one page, I'd ditch it. Here are some good alternatives to Gantt charts that'll dish the project dirt without requiring formatting gymnastics: