HKSM

Reserve analysis is a technique used to estimate, allocate, and manage cost and schedule reserves to address uncertainty. It sets contingency for known risks and recommends management reserve for unknowns, aligned to desired confidence levels and risk appetite.

Key Points

• Applies to both cost and schedule to protect objectives from uncertainty.
• Contingency reserve covers identified risks and is included in the baseline; management reserve covers unknowns and is outside the baseline.
• Reserve sizing is driven by risk exposure and desired confidence levels (for example, P70 or P80), often informed by quantitative analysis.
• Reserves must have clear usage rules, approval thresholds, and triggers to prevent misuse.
• Reserves are not a slush fund; they are tied to planned risk responses and conditions of use.
• Reserves are reviewed and adjusted as risks evolve and as the project progresses.

Purpose of Analysis

The purpose is to determine how much time and money to set aside so the project can absorb risk impacts without missing objectives. It aligns reserves with organizational risk tolerance and target confidence levels, improves realism of the plan, and provides governance for when and how reserves can be used.

Method Steps

• Compile risk data: identified risks, probabilities, impacts, and planned responses.
• Select a target confidence level based on stakeholder tolerance (for example, P70 cost, P80 schedule).
• Quantify exposure using techniques such as expected monetary value, range estimating, or Monte Carlo simulation.
• Differentiate reserves: size contingency for known risks and propose management reserve for unknowns.
• Allocate reserves to work packages, control accounts, or schedule buffers where risks are concentrated.
• Define triggers, drawdown rules, and approvals for reserve use, and document in the management plan.
• Update baselines and funding requirements to reflect approved contingency and management reserve.
• Monitor reserve consumption and re-forecast reserves as risks are retired or new ones emerge.

Inputs Needed

• Risk register or risk log with probabilities, impacts, and response strategies.
• Quantitative risk analysis outputs such as confidence curves, sensitivity charts, or simulation results.
• Cost estimates, schedule model, and assumptions for key activities and deliverables.
• Historical data and organizational reserve policies or guidelines.
• Stakeholder risk tolerance and funding constraints.
• Change control procedures and governance requirements for reserve use.

Outputs Produced

• Contingency reserve amounts embedded in the cost baseline and schedule buffers.
• Recommended management reserve and resulting total project budget and timeline.
• Reserve allocation by phase, control account, or activity, including buffer placement.
• Usage criteria, triggers, and approval thresholds for accessing reserves.
• Updates to baselines, funding requirements, risk register, and assumptions log.
• Reserve tracking approach and reporting cadence.

Interpretation Tips

• Confirm whether figures refer to contingency (in baseline) or management reserve (outside baseline) to avoid confusion.
• Link reserves to confidence targets: a P80 cost implies a 20 percent chance of overrun; adjust to the sponsor's tolerance.
• Prevent double counting by excluding response costs already baked into estimates from contingency calculations.
• Account for correlation among risks; independent summing can understate needed reserves.
• Release unused reserves at phase gates when associated risks are retired, improving forecast accuracy.
• Track reserve usage separately from variances to diagnose whether overruns are due to uncertainty or estimating errors.

Example

A project estimates USD 2.5M at P50. Monte Carlo shows P70 at USD 2.62M and P90 at USD 2.75M. The sponsor accepts P70, so the team sets cost contingency at USD 120k (2.62M - 2.5M) and recommends an additional USD 80k as management reserve for unknowns, yielding total funding of USD 2.7M.

Schedule analysis shows a P80 finish 12 working days beyond the deterministic plan, concentrated on two high-variability activities. The team inserts an 8-day project buffer plus two 2-day feeding buffers at those points. Triggers and approval thresholds are documented so buffer consumption is controlled and reported.

Pitfalls

• Using a flat percentage without risk analysis, leading to over- or under-reserving.
• Blurring contingency with management reserve, causing baseline and reporting issues.
• Lumping all reserves at project level with no allocation to risk hotspots, reducing effectiveness.
• Failing to define triggers and governance, resulting in uncontrolled reserve spending.
• Cutting reserves to meet a target budget without reducing risk exposure.
• Not revisiting reserves after major changes or as risks are closed.

PMP Example Question

While developing the cost baseline, the team identifies significant risk exposure. The sponsor asks to keep the baseline lean by placing all extra funds into management reserve. What should the project manager do?

1. Agree and place the entire amount in management reserve to avoid inflating the baseline.
2. Include contingency for identified risks in the cost baseline and keep a separate management reserve for unknowns.
3. Remove reserves and rely on change requests if risks occur.
4. Combine contingency and management reserve into a single pool managed by the sponsor.

Correct Answer: B — Include contingency for identified risks in the cost baseline and keep a separate management reserve for unknowns.

Explanation: Contingency belongs in the baseline to cover known risk responses, while management reserve is held outside the baseline for unforeseen work and governed separately.