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.

Probability Trees

A visual diagram that lays out possible events as branches, with each outcome shown on its own limb and labeled with its likelihood. These probabilities can be combined with impacts along each path to estimate the overall effect if risks occur on the project.

Key Points

  • Shows events and their alternative outcomes as branching paths.
  • Each branch is annotated with the probability of that outcome.
  • Enables calculation of expected impact (e.g., EMV) by multiplying probabilities and impacts along paths and summing results.
  • Useful for sequential or conditional risks and for comparing alternative decisions.

Example

A project faces a supplier delay risk (30% chance) that would cost $50,000. If the delay occurs, there is a 40% chance of additional rework costing $20,000. A probability tree shows: branch 1 (no delay, 70%, $0), branch 2a (delay only, 30% x 60% = 18%, $50,000), branch 2b (delay + rework, 30% x 40% = 12%, $70,000). Expected impact = (0.18 x 50,000) + (0.12 x 70,000) = $9,000 + $8,400 = $17,400.

PMP Example Question

Which risk analysis tool maps possible outcomes as branches, assigns a probability to each branch, and allows you to compute the overall expected impact?

  1. Probability trees
  2. Risk register
  3. Monte Carlo simulation
  4. RACI matrix

Correct Answer: A — Probability trees

Explanation: Probability trees depict outcomes as branches with probabilities, enabling calculation of expected impact across paths. The risk register documents risks; Monte Carlo simulates distributions; a RACI matrix defines roles.

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.

Seven 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