Float (slack) in scheduling, and how does it differ for the project finish date versus an intervening milestone?

Float (slack) in scheduling, and how does it differ for the project finish date versus an intervening milestone?

• A. Float is the amount of time a project can be extended without affecting any deliverables.
• B. Float is the amount of time an activity can be delayed without affecting the project finish date; free float refers to slack without delaying successors when not on the critical path.
• C. Float is the budget reserve for activities.
• D. Float is the total duration of the project.

Answer: (B)

Float (slack) shows how much you can delay a task without pushing the project’s finish date. There are two important flavors to understand. Total float is the amount of delay an activity can tolerate before the project finish date is affected. If an activity sits on the critical path, there is no float because delaying it will delay the project. Free float is the portion of that slack that won’t delay any successor activities. In other words, you can slide the activity within its free float without impacting downstream work. This distinction matters when an activity has downstream tasks; you might have free float to use without pushing successors. When an intervening milestone is involved, the same ideas apply: you’re looking at how much delay you can absorb without missing the milestone or delaying the final finish. Free float specifically focuses on not delaying successors, while total float relates to the overall project finish date.

Float (slack) shows how much you can delay a task without pushing the project’s finish date. There are two important flavors to understand. Total float is the amount of delay an activity can tolerate before the project finish date is affected. If an activity sits on the critical path, there is no float because delaying it will delay the project.

Free float is the portion of that slack that won’t delay any successor activities. In other words, you can slide the activity within its free float without impacting downstream work. This distinction matters when an activity has downstream tasks; you might have free float to use without pushing successors.

When an intervening milestone is involved, the same ideas apply: you’re looking at how much delay you can absorb without missing the milestone or delaying the final finish. Free float specifically focuses on not delaying successors, while total float relates to the overall project finish date.