In CPM, if a delay occurs on a non-critical activity, what is a possible consequence?

In CPM, if a delay occurs on a non-critical activity, what is a possible consequence?

• A. It cannot affect the project duration because it is non-critical.
• B. It will always reduce the project duration.
• C. It could become critical if its float is exhausted, potentially extending the project duration.
• D. It will shorten the project duration if delayed.

Answer: (C)

In CPM scheduling, every activity has float (slack) that shows how long it can be delayed without delaying the project finish. A delay on a non-critical activity uses up its float, and if that float is exhausted, the activity becomes critical, meaning any further delay will push the project completion date later. So a delay on a non-critical activity could extend the project duration if its float is consumed and it shifts into the critical path. It doesn’t automatically shorten the project, and it isn’t guaranteed to affect the duration unless the float is used up.

In CPM scheduling, every activity has float (slack) that shows how long it can be delayed without delaying the project finish. A delay on a non-critical activity uses up its float, and if that float is exhausted, the activity becomes critical, meaning any further delay will push the project completion date later. So a delay on a non-critical activity could extend the project duration if its float is consumed and it shifts into the critical path. It doesn’t automatically shorten the project, and it isn’t guaranteed to affect the duration unless the float is used up.