Skip to content

⚠️ Risk Identification & Tracking ​

Spotting risks early and managing them before they become problems.

Risk categories ​

  • Technical β€” Architecture limitations, integration issues, performance
  • Resource β€” Team availability, skill gaps, turnover
  • Timeline β€” Unrealistic deadlines, dependency delays
  • Scope β€” Creep, unclear requirements, changing priorities
  • External β€” Vendor reliability, regulatory changes, market shifts

Risk assessment matrix ​

Probability / ImpactLowMediumHigh
HighMediumHighCritical
MediumLowMediumHigh
LowLowLowMedium

Risk response strategies ​

  • Avoid β€” Change the plan to eliminate the risk
  • Mitigate β€” Reduce probability or impact
  • Transfer β€” Shift risk to a third party (insurance, outsourcing)
  • Accept β€” Acknowledge and prepare a contingency plan

Risk register template ​

RiskCategoryProbabilityImpactResponseOwnerStatus
API vendor goes downExternalMediumHighFallback providerTech LeadMonitoring

Best practices ​

  • Review risks at every sprint review or milestone
  • Assign an owner to each risk
  • Track leading indicators, not just lagging ones
  • Create contingency plans for critical risks before they happen
  • Celebrate risks that were mitigated successfully

Pergame Knowledge Base