LEARN. PRACTICE. GROW.A measure needs a rule and a date
In Vega’s fictional model, three packages have weights of 20, 30, and 50. The progress rule awards the full weight only when a package is accepted. If the first is accepted and the second merely coded, earned value is 20, not 50. This is an explicitly chosen teaching rule; it does not claim all projects should measure this way. Define the criterion before using it and apply it consistently. Also state data dates: Thursday costs, Monday progress, and month-old risks do not automatically represent a single Friday status. Reconcile periods or clearly flag limitations before interpreting a trend.
A current forecast does not erase the reference
Keep the authorized baseline, current forecast, and observed result distinct. Rearranging tasks within float and delegated authority may recover one day without changing approved commitments. Update the forecast and track float consumption; do not erase variance with an informal replacement baseline. In financial forecasting, check each amount’s boundary. If €42,000 is paid, €8,000 is accepted but unpaid work, and €15,000 is future work already including retirement, the total is €65,000. Adding retirement again duplicates cost. Values are invented for reasoning practice, not a bank’s estimates or universal accounting rules.
Evidence has validity conditions
A rehearsal with 600,000 records demonstrates results under that rehearsal’s conditions. Requesting another 400,000 in the same window changes the population and may change duration, contention, and reconciliation. Multiplying duration by the volume ratio is a working assumption; it does not replace evidence about the new load. Assess alternatives such as another rehearsal or staging, and obtain the decision from whoever can change scope. Apply similar care to dependent risks: if losing one lab delays two tests, do not multiply probabilities as though they were independent events. State the common event, consequences for each deliverable, and the response that may protect them together.
Transfer, acceptance, and retirement are distinct decisions
RUN may accept daily support before evidence exists to retire the old platform. In Vega, retirement requires a reconciled month-end; five stable days do not demonstrate that cycle. Keep an owner and assessment date for the pending condition, including parallel-running cost. If reorganization splits operations across two units, reconfirm who receives alerts and who decides outside business hours. At closure, also check accessible records, residual commitments, and mandatory criteria. A supplier’s personal account is not equivalent to organizational archive delivery. If you discover a completion report omitted a condition, correct it promptly and confirm decision makers received the update.
# Synthetic scenario rules; not an official exam or bank policy
weights = [20, 30, 50]
accepted = [True, False, False]
earned = sum(w for w, ok in zip(weights, accepted) if ok) # 20
forecast = 42000 + 8000 + 15000 # 65000
can_retire = daily_support_accepted and month_end_reconciledThe committee received “migration complete”, but the manager discovers reconciliation is still pending. Correct status before the benefit announcement and explain what is delivered, what remains unproven, and who decides the next step.
Common pitfalls
Counting unaccepted code as earned value; combining dates without warning; duplicating future cost; transferring evidence to another population; treating partial acceptance as waiver of pending conditions.
Related topics: Plan with real capacity · Stakeholders, mandates, and cross-team decisions · Operational exit and controlled decommissioning
Report the state supported by evidence, with conditions and dates. Completing a deliverable does not waive outstanding acceptance, transfer, or retirement criteria.
Reference: PMP Examination Content Outline July 2026 · PMP ECO July 2026; BigSavant PMP 2026.7