Managing Risk in Primavera Risk Analysis Rel. 8.6 Ed 1 — Lesson 4: Mitigation Planning, Contingency, Reporting, Governance, and Update Cycle

Technical Scope

• mitigation actions, response costs, residual risk, and ownership
• schedule contingency, cost contingency, management reserve, and appetite
• risk reports, executive narratives, confidence curves, and recommendations
• periodic updates, actuals, lessons learned, model governance, and risk runbook

Instructor Demonstration

Demonstrate mitigation actions, response costs, residual risk, and ownership within a capital project schedule analyzed for uncertainty and discrete risks to establish confidence dates, cost contingencies, mitigation priorities, and governance decisions, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering schedule contingency, cost contingency, management reserve, and appetite and risk reports, executive narratives, confidence curves, and recommendations, then test a failure, exception, or business-control scenario involving periodic updates, actuals, lessons learned, model governance, and risk runbook.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Mitigation Planning, Contingency, Reporting, Governance, and Update Cycle result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in mitigation actions, response costs, residual risk, and ownership, schedule contingency, cost contingency, management reserve, and appetite, risk reports, executive narratives, confidence curves, and recommendations, or periodic updates, actuals, lessons learned, model governance, and risk runbook without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Mitigation Planning, Contingency, Reporting, Governance, and Update Cycle and defend the result with documented evidence.