Backward Pass

A CPM technique that figures out each activity's late start and late finish by moving backward through the schedule from the project's completion date.

Key Points

  • Part of the critical path method, performed after or alongside the forward pass.
  • Starts at the project finish (or latest imposed finish) and works backward through the network.
  • For each activity: late finish (LF) is typically the minimum late start (LS) of its successors; late start (LS) = LF - duration, adjusted for leads/lags and relationship types.
  • Provides late dates used to compute float and confirm the critical path (zero total float).

Example

You have a project that must finish on day 50. Activity D (3 days) feeds two successors: E and F. From earlier calculations, LS(E) = day 30 and LS(F) = day 32. In the backward pass, D's LF = min(30, 32) = 30, and D's LS = 30 - 3 = day 27. Repeat this for all predecessors, moving backward until you reach the project's start.

PMP Example Question

Which scheduling step uses the project finish date to determine activities' late start and late finish dates?

  1. Forward pass
  2. Backward pass
  3. Resource leveling
  4. Rolling wave planning

Correct Answer: B — Backward pass

Explanation: The backward pass starts from the project completion date and calculates late dates for each activity, enabling float and critical path determination.

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


Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course