Float or Slack

5 minutes 5 Questions

Float, also known as slack, measures the amount of time that you can delay a task without causing a delay to other tasks or the project. Zero float tasks are on the critical path, while non-zero floats are off the critical path. This concept provides flexibility within the project schedule, allowing project managers to prioritize and reallocate resources if necessary and serves as a buffer against possible project delays.

Guide on Float or Slack in Critical Path Method

The term Float or Slack is commonly used in Project Management and especially in the Critical Path Method.

What is Float or Slack?
In the context of the Critical Path Method, float or slack is the amount of time that you can delay a task without a delay in the project. More slack time means the project schedule is more flexible.

Why is it important?
It's important to understand float or slack because it gives you flexibility in managing resources and risks. It allows project managers to make informed decisions on where flexibilities exist and where priorities lie. If a task has a float or slack of zero, it means it is on the critical path and any delay will affect the project's timeline.

How does it work?
The total float or slack time for a task is calculated by subtracting the early start date from the late start date (or the early finish date from the late finish date).

Exam Tips: Answering Questions on Float or Slack

1. Understand the concept of float or slack and its role in project scheduling.

2. Learn how to calculate float or slack time. Remember that it can be computed by subtracting early start date from late start date or early finish date from late finish date.

3. Always read the questions carefully. Look out for words indicating that a task is critical (i.e., has a zero slack) or non-critical.

4. Understand that tasks with more float or slack allow for more flexibility, while tasks with less or zero float or slack are more risk-prone and need to be managed carefully.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

You're managing a software project with an available float of 10 days. However, coding a new feature for the client is taking longer than expected and will use up 12 days of float. What will be the impact on the project's deadline?

The project will be completed on time The project will be completed 2 days early The project will be canceled The project will be delay by 2 days

Correct Answer: The project will be delay by 2 days

In project management, float (or slack) is the amount of time a task can be delayed before it affects the project's completion date. In this scenario, the available float is 10 days, but the new feature requires 12 days. This means the project will exceed its float by 2 days (12 - 10 = 2). When a project exceeds its available float, it directly impacts the project's deadline, causing a delay equal to the amount of exceeded float. Therefore, the project will be delayed by 2 days beyond its original deadline.

Question 2

An equipment failure has caused a delay in your project, resulting in a schedule variance of -4 days. However, your float is seven days. What's the possible status of your project?

The project cannot be completed Still on Schedule Behind schedule Ahead of schedule

Correct Answer: Still on Schedule

The correct answer is 'Still on schedule'. This is because even though there is a schedule variance of -4 days, there is still a float, or slack time, of seven days. Float time is essentially buffer time within the project schedule and in this case, the delay hasn't exhausted the float. Therefore, in this case, the project is still technically on schedule. 'Behind schedule' is incorrect because we're still within our float period. 'Ahead of schedule' isn't right because we're not ahead, we've just not consumed all our float yet. 'The project cannot be completed' is incorrect as the delay hasn't led to a situation preventing completion, as the float still provides leeway.

Question 3

You have a free float of 10 days in a software development project, but the client requests a feature that will take 9 days to complete. If you adjust the schedule for this feature, how does it affect your project's free float?

Remains 10 days Reduces to 1 day Increases to 19 days Increases to 11 days

Correct Answer: Reduces to 1 day

The correct answer is 'Reduces to 1 day'. A free float in project management refers to the amount of time that you can delay a task without pushing back the project end date or delaying the subsequent task. If you have a free float of 10 days and the client requests a feature that takes 9 days to complete, the free float would be reduced to 1 day. This is because you utilized 9 out of 10 days of your existing free float for the new feature. Therefore, the remaining free float after adjusting the schedule for this feature is 1 day. The answer 'Remains 10 days' is incorrect because it disregards the added feature that consumes free float. The answers 'Increases to 11 days' and 'Increases to 19 days' are also incorrect because adding a new feature that takes time to complete does not increase free float, it consumes it.

Go Premium