Decision Tree Analysis

A visual and quantitative approach for mapping a series of decisions and chance events, assigning probabilities, and calculating expected results to compare options when outcomes are uncertain.

Key Points

  • Represents decision nodes (squares) and chance nodes (circles) with branches showing possible paths.
  • Uses probabilities and outcomes to compute expected value (e.g., EMV) for each alternative.
  • Supports selecting among options when results are uncertain, such as choosing risk responses or vendors.
  • Assumes mutually exclusive paths and can include costs, benefits, and utility to reflect stakeholder preferences.

Example

A PM must choose how to deliver a module. Build in-house costs $300k with a 40% chance of a $120k delay penalty (EMV = 300k + 0.4 x 120k = $348k). Buy a COTS license for $260k and integrate: Vendor A (60%) integration cost $90k, Vendor B (40%) integration cost $200k, so expected integration = 0.6 x 90k + 0.4 x 200k = $134k; total expected cost = $260k + $134k = $394k. The decision tree favors building in-house ($348k) over buying ($394k).

PMP Example Question

A project manager needs to compare several mutually exclusive risk responses that involve sequential decisions and uncertain outcomes. She wants to assign probabilities and calculate expected monetary value to justify her choice. Which tool should she use?

  1. Monte Carlo simulation
  2. Decision tree analysis
  3. Pareto chart
  4. Sensitivity analysis

Correct Answer: B — Decision tree analysis

Explanation: Decision tree analysis maps decision and chance nodes and computes expected values for each path. Monte Carlo simulates many scenarios but does not depict branching choices; Pareto charts rank causes; sensitivity analysis shows which variables drive results.

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


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now