Baseline

An officially approved snapshot of a work product that may be altered only through formal change control and serves as the benchmark for comparing plan versus actual results.

Key Points

  • Represents the approved, frozen reference version of the plan or deliverable.
  • Any change to it requires a documented change request and formal approval.
  • Used to measure variances and track performance against what was planned.
  • Common types include scope, schedule, and cost baselines, which together support performance measurement.

Example

The project schedule is approved and set as the schedule baseline on May 1. Two weeks later, a task slips by 5 days. The team reports a 5-day schedule variance against the baseline. To reflect an approved scope change that shifts dates, the PM submits a change request; only after approval is the schedule baseline updated.

PMP Example Question

During execution, an approved scope change causes the critical path to slip by 10 days. What should the project manager do to keep performance measurement accurate?

  1. Update the schedule and baseline immediately to match actuals.
  2. Submit a change request to update the schedule baseline through integrated change control.
  3. Re-baseline the entire project only after project closure.
  4. Do nothing; baselines should never be changed.

Correct Answer: B — Submit a formal change request to update the baseline

Explanation: Baselines can be modified only through formal change control after approval; this keeps comparisons of planned versus actual results valid.

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 career!

HK School of Management offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More