ECE 480 Gantt Charts Revisited

ECE 480
Gantt Charts Revisited
Keys to Successful Gantt Charts
USE the default, finish-to-start, constraints
obtained by specifying predecessors,
unless you KNOW you need to do
something else!!!
 DON’T put REPORTING tasks in the
dependency chain, unless they are REALLY
in the chain
– If boss stops work unless approves report…
– If delaying report submission delays the
completion of the project!
Keys, cont.
Don’t block your critical path by making the last
task scheduled be independent of other tasks –
you get NOTHING. Last task determines end of
critical path, which works backwards from there.
 TEST your critical path – EVERY task that must
be accomplished to avoid delaying successful
project completion should appear in a
dependency chain that leads to final demo of
your project. That’s NOT interim reports and
presentations! You can ALWAYS report
progress: e.g., “There was none.” That’s a
progress report.
Keys, cont.
Use “Tracking Gantt” mode to see critical
path and task completion/partial
 Track (record) completion of tasks
regularly, show your facilitator
 Make sure your (operating) plan shows
completion by the due date (last Thursday
of semester, or earlier)