Which time constraint solution is best used when there are activities on the critical path that can be completed faster by adding resources?

Which time constraint solution is best used when there are activities on the critical path that can be completed faster by adding resources?

• A. Fast tracking
• B. Resource leveling
• C. Crashing the schedule
• D. Schedule compression

Answer: (C)

When you want to shorten the project timeline by making a specific path go faster, you apply a time-constraint technique that directly adds resources to activities on the critical path. The critical path is the sequence of tasks that determines the project’s finish date; reducing the duration of any of those tasks reduces the overall project duration. By allocating more people, equipment, or other resources to those critical activities, you can complete them sooner. This approach is a deliberate time-cost trade-off: it usually increases cost or risk, but it yields the quickest way to shorten the schedule when the bottleneck lies on the critical path. Other techniques don’t fit as well here. Fast tracking speeds up the project by overlapping tasks, but it doesn’t necessarily involve adding resources and it increases risk. Resource leveling focuses on smoothing resource usage and avoiding overallocation, which can actually extend the schedule rather than shorten it. Schedule compression is the umbrella term for methods to shorten the schedule, but the specific method that explicitly uses extra resources to drive down duration on critical-path activities is crashing.

When you want to shorten the project timeline by making a specific path go faster, you apply a time-constraint technique that directly adds resources to activities on the critical path. The critical path is the sequence of tasks that determines the project’s finish date; reducing the duration of any of those tasks reduces the overall project duration. By allocating more people, equipment, or other resources to those critical activities, you can complete them sooner. This approach is a deliberate time-cost trade-off: it usually increases cost or risk, but it yields the quickest way to shorten the schedule when the bottleneck lies on the critical path.

Other techniques don’t fit as well here. Fast tracking speeds up the project by overlapping tasks, but it doesn’t necessarily involve adding resources and it increases risk. Resource leveling focuses on smoothing resource usage and avoiding overallocation, which can actually extend the schedule rather than shorten it. Schedule compression is the umbrella term for methods to shorten the schedule, but the specific method that explicitly uses extra resources to drive down duration on critical-path activities is crashing.