LEARN. PRACTICE. GROW.Concept and mechanism
Start by understanding the outcome the project must deliver and the conditions under which it is acceptable. In a funds migration, cost, schedule, data integrity, and outage duration may have different limits. Gather contracts, previous incidents, architecture, assumptions, and support commitments. Check each document’s origin and relevance: a probability estimated for another service may not suit the new solution. Risk appetite needs to become criteria for concrete decisions. A sponsor may accept cost variation while having little room for missing cut-off. Do not automatically carry financial tolerance across to unavailability.
Guided application
Agree probability and impact definitions before comparing ratings. If impact 4 means one day to one team and one hour to another, colors are not comparable. Also define who oversees risk, who implements each action, and who may accept exposure above the limit. An engineer may install redundancy without authority to accept business risk. Use the RBS as a source map: technology, people, contracts, and the external environment help find overlooked areas. Retain concrete events, consequences, and owners in the register. At committee, present criteria, evidence, and options. Analysis quality helps authorized people decide; it does not grant the analyst powers the organization has not assigned.
A fictional 90-minute limit at P80 requires comparing that percentile with the window, not merely mean duration.
Common pitfalls
Undefined scales; assumed authority; confused roles; checklist treated as complete coverage.
Related topics: Organize people, cadence, and resources · Identify events, assumptions, and opportunities
Before rating risk, clarify objectives, criteria, and authority.
Reference: PMI-RMP Exam Content Outline · PMI-RMP five-domain ECO, updated-2024 public document