Variance Analysis

A method used to identify why results differ from the baseline and to measure how large those differences are.

Key Points

  • Compares actual results to baseline plans for cost, schedule, and other performance areas.
  • Quantifies the size of the deviation and investigates root causes.
  • Supports corrective and preventive actions and informs forecasts (for example, EAC in EVM).
  • Performed during monitoring and controlling, often alongside trend and earned value analysis.

Example

At the end of month 3, the project planned value is USD 300,000, earned value is USD 250,000, and actual cost is USD 280,000. Variance analysis shows SV = -50,000 and CV = -30,000. The team traces the cause to a vendor delay and overtime costs, then updates the schedule and cost forecasts and implements corrective actions.

PMP Example Question

During Control Costs, the project manager sees that actual costs are higher than planned. Which technique should be used to determine why the deviation occurred and how large it is compared to the baseline?

  1. Trend analysis
  2. Variance analysis
  3. What-if scenario analysis
  4. Reserve analysis

Correct Answer: B — analyzing differences from the plan and their causes

Explanation: Variance analysis compares actuals to the baseline to quantify the gap and identify root causes, enabling targeted corrective action.

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


Launch your Agile career!

HK School of Management and Technology helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More