The below figure gives the task durations for software project activities. Assume that a serious, unanticipated setback occurs and instead of taking 10 days, task T5 takes 40 days. Revise the activity network accordingly, highlighting the new critical path. Draw up new bar charts showing how the project might be reorganized. 14/7/99 15 days 15 days 8 days T9 T1 5 days 4/8/99 25/8/99 25/7/9 M6 4/7/99 T6 M3 start15 days 20 days 7 days T7 T11 T2 5/9/99 25/7/99 11/8/99 10 days 10 days M715 days M8 M2 T5 T4 T10 10 days 8/7/99 T12 M5 25 days T8 Finish 19/9/99 The below figure gives the task durations for software project activities. Assume that a serious, unanticipated setback occurs and instead of taking 10 days, task T5 takes 40 days. Revise the activity network accordingly, highlighting the new critical path. Draw up new bar charts showing how the project might be reorganized. 14/7/99 15 days 15 days 8 days T9 T1 5 days 4/8/99 25/8/99 25/7/9 M6 4/7/99 T6 M3 start15 days 20 days 7 days T7 T11 T2 5/9/99 25/7/99 11/8/99 10 days 10 days M715 days M8 M2 T5 T4 T10 10 days 8/7/99 T12 M5 25 days T8 Finish 19/9/99