Management Reserve

A portion of the project budget or schedule kept outside the performance measurement baseline (PMB) under management control, set aside to address unexpected work that still falls within the approved project scope.

Key Points

  • Held outside the PMB and not part of performance measurement until it is authorized for use.
  • Intended for unforeseen, in-scope work (unknown-unknowns), not for approved scope changes.
  • Typically released by senior management or the sponsor; using it usually requires a formal change to the PMB.
  • Different from contingency reserve, which is inside the baseline and linked to identified risks.

Example

Midway through a capital project, new regulatory testing is unexpectedly required but is still within the project's scope. The sponsor authorizes use of management reserve to cover the extra tests and associated schedule impact, and the PMB is updated to reflect the approved change.

PMP Example Question

Which statement best describes management reserve?

  1. Funds within the cost baseline set aside for identified risks with planned responses.
  2. Money or time kept outside the PMB, controlled by management, for unforeseen but in-scope work.
  3. Budget allocated for customer-requested scope changes.
  4. Extra padding added by team members to individual activity estimates.

Correct Answer: B — Money or time kept outside the PMB for unforeseen, in-scope work

Explanation: Management reserve is outside the PMB and used for unknown-unknowns within scope; contingency (A) is inside the baseline, while C and D are not correct uses.

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


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now