How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Critical Path Method (CPM)

A scheduling technique that calculates the shortest possible project duration and measures the amount of float on each logical path in the schedule network.

Key Points

  • Identifies the critical path: the longest path through the network with zero total float; any delay on it delays the project finish.
  • Uses forward and backward pass to compute early/late start and finish dates and total float for activities and paths.
  • The critical path can shift during execution, and there can be multiple critical paths in some schedules.
  • Informs schedule compression choices (crashing, fast tracking) and highlights where schedule flexibility exists.

Example

A project schedule lists activities with durations and dependencies. The team draws the network diagram and runs forward and backward passes to find early/late dates. The path A-B-D-E totals 40 days with zero float, while path A-C-E totals 35 days with 5 days of float. To finish sooner, the manager considers crashing activities on A-B-D-E since only shortening the critical path reduces the overall project duration.

PMP Example Question

Which technique determines the minimum project duration and identifies where schedule float exists across network paths?

  1. Critical Path Method (CPM)
  2. Program Evaluation and Review Technique (PERT)
  3. Monte Carlo simulation
  4. Resource leveling

Correct Answer: A — Critical Path Method (CPM)

Explanation: CPM calculates early and late dates, total float, and the longest path, revealing the minimum project duration and schedule flexibility.

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