Difference between Crashing and Fast Tracking.
I have been trying to understand the difference between Crashing and
Fast tracking. Following are my understanding and questions:
Fast tracking means that you look at activities that are normally done
in sequence and assign them instead partially in parallel. If you were
fast-tracking, you would start constructing the solution in areas where
you felt the design was pretty solid without waiting for the entire
design to be completed.
"Crashing" the schedule means to throw additional resources to the
critical path without necessarily getting the highest level of
efficiency. For instance, let’s say one person was working on a ten-day
activity on the critical path. If you were really desperate to shorten
this timeframe, you might add a second resource to this activity.
1) Both the approaches are aimed at reducing the schedule
2) Both the approaches require addition of resources to achieve the goal
3) Even though fast tracking doesn't mention the term Critical Path,
it's obvious that the Critical Path tasks need to be done in parallel
to reduce the schedule. So, both the approaches involve changes to
Critical Path activities schedule.
Given the above, both of them looks similar with no subtle difference.
But, the two different terms should have been created for a purpose,
that i might be missing here.