Schedule Compression: What's the Difference between Fast Tracking and Crashing?

The video explains the concepts of crashing and fast tracking in project management, both of which are methods to expedite a project or compress a schedule. Crashing involves using additional resources to speed up project completion, while fast tracking involves performing tasks in parallel that are usually done sequentially. Both methods have associated risks and costs, such as increased expenses and potential resource burnout for crashing, and dependency risks for fast tracking. The video concludes that a combination of both methods is often used to achieve project goals efficiently.

What is the primary goal of both crashing and fast tracking in project management?

• To improve team communication

• To reduce project costs

• To expedite project completion

• To enhance project quality

Which of the following is a method used in crashing a project?

• Reducing project scope

• Hiring additional staff

• Delaying project tasks

• Eliminating project risks

What is a potential risk of fast tracking a project?

• Increased project costs

• Resource burnout

• Dependency conflicts

• Reduced project scope

In the context of fast tracking, what does performing tasks in parallel mean?

• Eliminating unnecessary tasks

• Completing tasks one after another

• Starting a new task before the previous one is finished

• Delaying tasks to save resources

Which of the following is NOT a method of expediting a project?

• Crashing

• Using COTS components

• Fast tracking

• Reducing quality