Sensitivity analysis

Sensitivity analysis tests how changes in a single input affect a project outcome while holding other inputs constant. It highlights which variables have the greatest influence so the team can focus risk responses and monitoring on what matters most.

Key Points

  • Varies one input at a time to see its effect on a chosen outcome (e.g., cost, schedule, NPV).
  • Helps prioritize critical assumptions and risks that drive the most change.
  • Often visualized with a tornado diagram to rank variables by impact.
  • Supports quantitative risk analysis, estimating, and scenario planning.
  • Relies on credible ranges for inputs (e.g., optimistic, most likely, pessimistic).
  • Complements but does not replace probabilistic methods like Monte Carlo.

Purpose of Analysis

To identify which uncertain inputs most influence project outcomes so that management attention, contingency, and risk responses are focused where they yield the greatest benefit.

Method Steps

  • Select the outcome metric to test (e.g., total cost, finish date, benefit value).
  • List candidate input variables and define realistic ranges or discrete scenarios for each.
  • Hold all inputs constant at their baseline and vary one input across its range.
  • Record the outcome change at each bound for that input; repeat for all inputs.
  • Rank inputs by magnitude of outcome change; create a tornado diagram if useful.
  • Translate findings into actions: refine estimates, add reserves, or plan risk responses.

Inputs Needed

  • Baseline model or estimate linking inputs to the chosen outcome.
  • List of uncertain inputs and their plausible ranges or scenarios.
  • Assumptions and constraints that define fixed versus variable factors.
  • Historical data, expert judgment, or market intelligence to set input ranges.
  • Risk register entries that describe key drivers and potential responses.
  • Tooling (e.g., spreadsheet, scheduling or cost model) to run calculations.

Outputs Produced

  • Ranked list of inputs by their impact on the outcome.
  • Impact ranges showing how the outcome changes at input bounds.
  • Tornado diagram or similar visualization (optional but common).
  • Recommendations for risk responses, contingency, and further analysis.
  • Updated assumptions and documentation of input ranges tested.

Interpretation Tips

  • Focus on high-impact drivers first; they offer the best leverage for control.
  • Check that input ranges are realistic; exaggerated ranges distort priorities.
  • Remember it is a one-factor-at-a-time view; interactions among variables are not shown.
  • Use results to refine estimates and trigger targeted risk responses.
  • Pair with scenario or probabilistic analysis when dependencies are important.

Example

A project cost model depends on labor rate, productivity, and material price. The team varies each input between optimistic and pessimistic bounds while holding the others at baseline. The tornado diagram shows productivity has the largest impact on total cost, followed by material price, then labor rate. The team decides to pilot process improvements (to stabilize productivity) and negotiates price locks with suppliers.

Pitfalls

  • Using arbitrary ranges without data or expert validation.
  • Ignoring correlations between inputs that move together in reality.
  • Overlooking non-linear effects when the model only assumes linearity.
  • Assuming results are precise; they are only as good as the model and inputs.
  • Failing to convert insights into concrete risk responses and monitoring.

PMP Example Question

A project manager wants to identify which uncertain cost driver most affects the total project budget. Which technique should they use to vary one input at a time and compare the change in total cost?

  1. Expected monetary value analysis.
  2. Sensitivity analysis.
  3. Cause-and-effect diagram.
  4. Delphi technique.

Correct Answer: B — Sensitivity analysis

Explanation: Sensitivity analysis varies one input at a time to see its effect on the outcome and rank drivers by impact. The other options serve different purposes.

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