Live data from Hacker News

The Art and Science of Leading Projects

teamgantt.com

21–23 of 23 posts

Re: The Art and Science of Leading Projects

#21

Earlier quoted context omitted.

What is the difference between a Gantt chart and a dependency graph?

Gantt charts typically have resource assignments and time estimates. Dependency graphs just say Bravo requires Alpha to be completed first (for example).

Dependency graphs can also be annotated with the resources required for each node or edge. Resources are estimated by summation, time is estimated by finding the critical path.

Gantt charts are a partial linearization of a dependency graph. People tend to fixate over the dates shown, allow schedule pressure to "correct" previous estimates, etc.

According to some early users of Gantt charts, they are a great tool for summarizing a plan, a terrible tool for developing and maintaining one.

Re: The Art and Science of Leading Projects

#22
post #4

Not for me, but I do like that one of the sections is: > 08 - Winning trust with communication > Learn simple keys to becoming a better communicator and how to identify your team’s different communication styles. Having experienced the pain of working somewhere where leadership tried to decree a single "right" method of communication for all developers that didn't jive with us at all, I don't take this for granted an…

People constantly confuse communication with a lot of talking and collaboration with sitting in the same room or constant meetings.

good communication happens when there's good [shared] motivation

Re: The Art and Science of Leading Projects

#23
post #7

Step 1 is not using a gantt chart to create some illusory impression of knowing exactly how complex projects will unfold.

I think problem is not creating gantt chart but impression of knowing exactly how complex projects will unfold. If you do this without creating gannt or any other chart you end up with the same result.
Post reply on HN