Critical Path Method

Correct Answer: Path B due to its higher probability of achieving planned duration

In CPM analysis, when considering paths with different probabilities of completion, we need to evaluate both duration and risk factors. Path B is the critical path because: 1. It has a 90% probability of achieving its planned duration, making it more reliable 2. The difference in duration is only 1 day (21 vs 20 days) 3. The higher reliability significantly reduces the risk of project delays Why other options are incorrect: - While Path A is shorter by one day, its lower success rate (70%) makes it more risky and less reliable for project planning - Having durations within one day of each other doesn't automatically make both paths critical; we must consider probability factors - Resource specialization is not a primary factor in determining the critical path; the focus should be on duration and probability of completion In project management, a more reliable path with slightly longer duration is often preferred over a shorter but riskier path, as it provides better predictability and risk management.

Correct Answer: Increase by 4 days

In project management, the critical path is the sequence of tasks that determines the minimum duration of the project. Any delay in a task on the critical path will directly impact the overall project duration. Since the question states that the task experiencing the delay is on the critical path, and the delay is 4 days, the project duration will increase by exactly 4 days. This is because tasks on the critical path have zero float, meaning any delay in these tasks will automatically extend the project completion date. Other tasks not on the critical path may have some flexibility (float) and their delays might not affect the overall project duration, but this is not the case for critical path tasks.

Correct Answer: Compare the crash cost per day for each critical task and prioritize tasks with lowest crash cost per day

The best approach for schedule compression in CPM is to compare crash costs per day for critical path activities and select those with the lowest crash cost per day. This method ensures cost-effective schedule compression while maintaining network logic. This approach is optimal because: 1. It focuses on critical path activities, which actually impact project completion 2. It prioritizes cost-efficiency by selecting activities with lowest crash cost per day 3. It maintains the project's network logic and relationships The other options are incorrect because: - Crashing parallel paths simultaneously is unnecessary and wasteful when not all paths are critical - Crashing activities with high total slack is ineffective since these activities do not impact the project completion date - Crashing tasks based solely on duration fails to consider cost implications and may result in unnecessary expenses