Fast Tracking Vs Crashing

hi guys today's topic is fast tracking versus crashing both of these terms are mainly related to schedule compression how we can compress a schedule by using these two techniques fast tracking and crashing let me start from fast tracking fast tracking is basically doing critical path activities in parallel that were originally planned in sequence this will often results in rework usually increased risk and requires more attention to communication let me explain this from this diagram please consider this network diagram this activity has two days duration this has ten days duration this has seven days and this has one days so if we start from here and try to calculate the critical path from here so two plus ten 12 plus seven 19 plus 120 so from here it's 20 and from here if we can calculate 2 + 5 7 + 1 8 so from here it's 8 so this one from here this is our critical path which is of 20 days or longest duration so so this is the critical path from here so if your manager came and he says that 20 days are very high days and you want to and he wants to reduce these number of days to 15 days or less than 15 days so what you have to do to achieve this objective of 15 days you need to consider an activity which can be done in parallel originally its plan to do in sequence but due to the requirement of the constraint of time you need to do it in parallel so you have to overlap the dependency here for example if you want to do this seven days activity in parallel so it can be done before finishing of this ten days activity so you have to overlook or bypass this dependency and do this seven days activity in parallel with this ten days activity so in this way the sequential activities needs to be done in parallel and overlooked the dependencies to achieve or compress the schedule after applying the fast-tracking this network diagram would become like that see if we calculate now the critical path again so two plus ten twelve plus one thirteen the seven you can see now it's parallel with the ten so two plus seven nine plus one ten and if we calculate from here to plus five seven plus one six seven plus one-eighth so now if we calculate the critical path the longest duration now it's become 13 so you can see from here that after making the seven days activity parallel the duration total duration of project become reduced and it came to thirteen so it means the in fast-tracking basically we make the activities in parallel to compress the schedule but the it it results it increased the risk factor because originally these activities were planned in to two as a sequence but due to the car requirement and time constraint you have to do it in parallel so it increased the risk and you have to consider the communication complications let me came towards crashing in thrashing basically it making cost and schedule trade-offs to determine how to obtain the greatest amount of scheduled compression for the least incremental cost while maintaining project scope it always result in increased cost please consider this diagram again it is the same diagram which we have shown in fast-tracking see if you have to crash to do crashing in this project so you have to you have to reduce the time duration of an activity so that the overall project duration becomes reduced to achieve this objective you need to put more resources by mean my meaning to put more reduces it will increase the cost automatically so crashing always results in increasing of cost for example please consider this activity of 10 days if a one day if one resource is taking ten days to achieve this task so if we put more resources here so that we need to check that can be accomplish a task unless they're less days if it's possible then we will put more resources here but it will eventually increase the cost of overall project after applying the crashing we double the resources here so that this same activity of 10 days can be achieved in 5 days now if we calculate the critical path again from here so 2 + 5 7 + 7 14 + 1 15 if we calculate from here to + 5 7 + 1 8 so you can see here now that the critical path now becomes as 15 days because we have doubled the resources here so in crashing basically we put more resources to crash or to compress the schedule of a project but it eventually increased the cost of a project to summarize fast tracking and crashing in fast tracking basically we generally overlook the dependencies so it may result in rework and increase risk it will not compromise on the scope of work but it increased rework and factor of risk in crashing we have to add more resources to compress the schedule of a project but it is expensive and increased cost thanks for your time that's all from my side I hope this topic increase your concept or knowledge about the fast tracking and crashing if you like this video please share with your friends and please and I would request to subscribe to my channel so that I can share my updates with you thanks a lot for your time

Channel: Project Management

Views: 19,920

Rating: 4.7156396 out of 5

Keywords: Fast Tracking, Crashing, parallel, critical path, cost, expensive, dependency, activity, schedule compression

Id: uJD4G9EDH8w

Length: 8min 4sec (484 seconds)

Published: Sat Mar 05 2016