Schedule Compression

A method to shorten the overall project timeline without changing the agreed scope.

Key Points

  • Achieved mainly through fast-tracking (overlapping work) and crashing (adding resources to critical tasks).
  • Focuses on activities on the critical path; compressing non-critical work may not affect the finish date.
  • Often increases cost and/or risk, so trade-offs must be analyzed before applying.
  • Requires re-analysis of the schedule and stakeholder agreement on impacts and assumptions.

Example

A construction project is slipping. The PM overlaps foundation curing with early framing (fast-tracking) and brings in an extra crew for framing (crashing) to pull the completion date back without changing deliverables.

PMP Example Question

A project must meet a deadline without removing any deliverables. What should the project manager do?

  1. Apply schedule compression by fast-tracking critical path activities.
  2. Reduce lower-priority requirements to save time.
  3. Level resources across all tasks to balance workload.
  4. Add extra features to increase stakeholder satisfaction.

Correct Answer: A — Schedule compression

Explanation: Schedule compression shortens the timeline without changing scope. Scope reduction changes scope, resource leveling often lengthens duration, and gold plating adds unnecessary work.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course