A critical path is not a list of the project’s “most important” tasks. It is the longest sequence of dependent activities in a schedule, and it determines the earliest possible completion time under the current constraints. If an activity on that path slips and has no available float, the finish date will usually move with it. A task outside the path may be delayed within its float without changing the final date.
Consider a kitchen renovation. Measuring, fabricating the benchtop, installing it and connecting the sink must happen in order and together take twelve days. Wall touch-ups, meanwhile, need only three days and can finish earlier. A one-day delay in painting may not affect handover, while a one-day delay in fabrication may push every later step back. Attention should therefore follow dependencies and float, rather than being spread evenly across every task.
The critical path is not the same as a bottleneck. A bottleneck describes a resource that constrains ongoing throughput; a critical path identifies the chain that sets the minimum duration of a one-off project. Nor is it permanent. If a task becomes shorter, a dependency changes or resources are reassigned, another path may become critical.
The practical point is simple: the effect of a delay depends on where it sits in the network, not only on how long it lasts. Urging every task to go faster may create more bustle without shortening the project. Find the path that controls the finish, and you know what deserves protection first.
Source: https://www.pmi.org/-/media/pmi/documents/registered/pdf/pmbok-standards/pmi-lexicon-pm-terms.pdf
Discover more from Geoffrey Chen
Subscribe to get the latest posts sent to your email.