Free Slack is the amount of time an activity can be delayed without delaying the early start of any immediately

following activities. For example in exercise 4 if we see in the activity H, there are two paths that have to complete before H can begin. The above path takes 2 + 2 = 4 days before H can begin and the next path takes 3 + 3= 6 days before H can begin. However, the longer path controls when the activity H can begin. Since the top path takes 4 days and the other path before H takes 6 days the first path has 2 days of Free Slack time before H can begin. Also For the activity K, there are two paths that have to complete before K can begin. The top path takes 10 days before K can begin and the next path takes 14 days before K can begin. However, the longer path controls when the activity K can begin. Since the top path takes 10 days and the other path before K takes 14 days the first path has 4 days of Free Slack time before K can begin. Since H can finish at day 10 in the project then, we say that H has 4 days of Free Slack. This means that H can be delayed 4 days without affecting (or changing) the early start date of K. Similarly we can calculate free slack for other activities. Total slack is the amount of time a task can slip without affecting the project's finishing date. When the total slack is negative, the duration for a task is too long for its successor to begin on the date required by its constraint. Before activity H could start there are two paths. One of them is the part of critical path which wouldn't have any total slack. The other one is A-B-E. A doesn't have any total slack as any delay in A causes delay in the planned project finish date. Whereas the total slack for B is 2 days. This means that you can delay the start of B by 2 days and it will not affect the end date of the project. The total slack for E is also 2 days, since E could be delayed and this delay will not affect the end date of the project. Similarly we can calculate total slack for other activities.