Sensitivity Analysis

A technique used to identify which specific risks or uncertain factors most strongly influence project results by examining how changes in model inputs are associated with changes in the outputs of a quantitative risk model.

Key Points

  • Shows how variation in one input affects the model's output while other inputs are held constant or controlled.
  • Often presented with a tornado diagram that ranks inputs by their impact on the outcome.
  • Helps prioritize risk responses by highlighting the uncertainties that drive the most outcome variability.
  • Requires a quantitative risk model with defined inputs, ranges, and a clear output metric (e.g., cost, duration).

Example

A team models total project cost with uncertain inputs such as labor productivity, material prices, and rework rates. They vary each input across its range to see how total cost changes. The tornado diagram shows labor productivity as the largest driver, so the team focuses on training and buffer strategies to reduce that risk.

PMP Example Question

After completing a quantitative cost risk model, the team wants to determine which uncertain inputs have the greatest effect on the total cost. They create a tornado diagram ranking labor productivity, material price, and rework rate by impact. Which technique are they using?

  1. Sensitivity analysis
  2. Monte Carlo simulation
  3. Expected monetary value analysis
  4. Decision tree analysis

Correct Answer: A — Sensitivity analysis

Explanation: Sensitivity analysis ranks input variables by their effect on model outputs, commonly shown with a tornado diagram. Monte Carlo produces output distributions, while EMV and decision trees evaluate choices under uncertainty.

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


Become an AI-First Agile Leader!

HK School of Management and Technology helps you apply AI to Agile work with practical, prompt-based workflows for real-world Scrum challenges. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More