An Explanatory note on ³Project Crashing ³
Crashing is a process of expediting project schedule by compressing the total project duration. Itis helpful when managers want to avoid incoming bad weather season. However, the downside isthat more resources are needed to speed-up a part of a project, even if resources may bewithdrawn from one facet of the project and used to speed-up the section that is lagging behind.Moreover, that may also depend on what slack is available in a non-critical activity, thusresources can be reassigned to critical project activity. Hence, utmost care should be taken tomake sure that appropriate activities are being crashed and that diverted resources are notcausing needless risk and project scope integrity. Indeed, it is advisable to first crash activitiesearly in the project as to have a leeway to crash other activities in the later stages of the project. Nonetheless, it is imperative that all project guidelines, resources and costs are diligently beingtracked and are aligned to the aspirations of the client and senior managers.Project crashing is a method for shortening the project duration by reducing the time of one or more of the critical project activities to less than its normal activity time. The object crashing isto reduce project duration while minimizing the cost of crashing.OBJECTIVE OF CRASHINGTo reduce the scheduled completion time to reap the results of the project sooner.As project continue over time, the team consume indirect costs.There may be direct financial penalties for not completing a project on time.KEY TERMSCRASHING is reducing project time by expending additional resources.CRASH TIME is an amount of time an activity is reduced.