Variation

A real project condition that differs from what the approved baseline predicted.

Key Points

  • It is the difference between actual project conditions and what the baseline expected.
  • Variations can be favorable or unfavorable and should be measured and recorded.
  • They often trigger analysis and may lead to corrective or preventive actions and change requests.
  • A variation is not an approved change; baselines are updated only through integrated change control.

Example

In a construction project, the baseline plan expects concrete to cure in 7 days, but due to cold weather it takes 9 days. The 2-day difference is a variation that the project manager logs, analyzes for schedule impact, and addresses through the change control process if needed.

PMP Example Question

During monitoring and controlling, the team observes the actual defect rate is 3% while the baseline target is 1%. What is this difference called?

  1. Variation
  2. Issue
  3. Change request
  4. Risk event

Correct Answer: A - Variation

Explanation: It is an actual condition that does not match the baseline expectation, which defines a variation. It may lead to an issue entry or change request, but the difference itself is a variation.

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 the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management and Technology, not on Udemy.

See What Is Included