Lesson 119 of 159·4 min
Gantt charts and the critical path: reading schedule exposure
A Gantt chart places tasks against time so that duration, overlap and sequence are easier to see. It helps a team discuss whether the plan is plausible and which delays could affect later work. The visual presentation is useful only when the underlying tasks and relationships are accurate.
The critical path is the sequence that constrains the planned finish. Float, also called slack, is the available scheduling flexibility before a relevant finish is affected. A task can be important to the business without being on the critical path, and a short task can be critical if nothing else can proceed until it finishes.
DNA's Gantt view
DNA's Gantt page loads tasks for the selected project, active phases and dependency information. It groups operational information into a time-based view and includes critical-path and schedule-health calculations.
The reviewed calculation classifies tasks with zero or negative slack as critical and those with positive slack up to two days as near-critical. These classifications describe that calculation's output; they do not prove the plan includes every real constraint.
A verification limitation
In the supplied implementation, displayed dependency relationships and the critical-path calculation do not use the same dependency-loading route. The critical-path result therefore needs independent checking against the saved project relationships before it is used to promise a delivery date.
The practical lesson is to examine the actual sequence, dates and task completeness rather than rely only on a coloured bar or a critical label. Missing prerequisites can produce a reassuring chart with an unrealistic completion date.
Using the chart for decisions
Suppose inspection has no scheduling flexibility while a documentation task has several days available. Bringing forward inspection preparation may protect the finish more effectively than accelerating documentation. That is a planning judgement based on a verified sequence, not a rule that every critical task deserves unlimited resources.
Review the project after significant scope or date changes. A useful schedule discussion identifies the threatened outcome, the responsible person, feasible corrective action and the effect on downstream work.
Not marked. Answer every question to finish the lesson.
