Crashing

Correct Answer: A linear cost increase per unit time reduction

In project crashing, there is typically a linear relationship between cost increase and time reduction for each activity being crashed. When analyzing the cost-time relationship in project crashing: - Each unit of time reduction requires a proportional increase in cost - The crash cost per unit time remains constant for each activity until it reaches its maximum crash point - This creates a linear cost slope for each activity The other options are incorrect because: - The cost does not decrease exponentially with resource addition; it actually increases - The cost ratio is not fixed but varies based on which activities are being crashed - There is no logarithmic cost reduction; adding resources to critical activities increases costs linearly

Correct Answer: Activities with the lowest crash cost per unit time on the critical path

When crashing a project schedule, the primary goal is to reduce project duration in the most cost-effective way possible. The best approach is to focus on activities that are on the critical path, as these activities determine the overall project duration. Among these critical path activities, we should select those with the lowest crash cost per unit time to minimize the additional costs while achieving the desired schedule reduction. Other options are incorrect because: - Having high resource availability and maximum float time means these activities are not on the critical path, so crashing them would not reduce overall project duration - Short duration and minimal resource requirements are not relevant criteria for crashing decisions if the activities are not on the critical path - Schedule variance alone is not a valid criterion for selecting crash candidates, as activities must be on the critical path to affect the project completion date

Correct Answer: It involves adding resources to reduce activity duration at increased cost

Crashing is a schedule compression technique that specifically involves adding additional resources to activities to reduce their duration, though at an increased cost. Key characteristics of crashing: - Adds resources to critical path activities - Reduces activity duration - Increases project costs - Maintains original scope - Focuses on cost-time trade-offs The other options are incorrect because: - Fast tracking is about performing activities in parallel, which increases risk but is a different compression technique - Reducing project scope is not a schedule compression technique - it's a different type of change that alters project deliverables - Resource optimization through leveling/smoothing typically extends the schedule rather than compressing it Crashing is unique because it maintains the project's logical relationships and scope while trading additional cost for faster completion time.