Which schedule compression technique has phases or activities done in parallel that would normally have been done sequentially?

Question

Options

• ACrashing
• BFast tracking
• CLeads and lags adjustment
• DParallel task development

• A
  3% (2)
• B
  75% (46)
• C
  15% (9)
• D
  7% (4)

Explanation

Fast tracking (B) compresses the schedule by overlapping phases or activities that were originally planned to run sequentially - for example, starting construction while design is still being finalized. This introduces risk since the later activity begins before the earlier one is complete, but it saves time without adding resources.

Crashing (A) also compresses the schedule, but by adding resources (people, budget, equipment) to critical path tasks - not by parallelizing work. Leads and lags adjustment (C) is about fine-tuning dependencies (starting a successor task early = lead; delaying it = lag), which can affect schedule duration but is not a compression technique per se. Parallel task development (D) is a plausible-sounding distractor but is not a recognized PMI/PMBOK term - it's essentially describing fast tracking without using the correct name.

Memory tip: Think of fast tracking like a relay race where runners start overlapping their legs before the baton is passed - you're going faster by running in parallel, but you risk a dropped baton (rework/risk). "Fast = parallel" locks in the distinction from crashing, which is "crash = add more people/money."

No community discussion yet for this question.