Architecture Risk Analysis
1 min read
Risk Matrix
Dimensions:
- Impact (Low=1, Medium=2, High=3)
- Likelihood (Low=1, Medium=2, High=3)
Score = Impact × Likelihood
Risk Levels:
- 1-2: Low (green)
- 3-4: Medium (yellow)
- 6-9: High (red)
| Impact/Likelihood | Low (1) | Medium (2) | High (3) |
|---|---|---|---|
| Low (1) | 1 (green) | 2 (green) | 3 (yellow) |
| Medium (2) | 2 (green) | 4 (yellow) | 6 (red) |
| High (3) | 3 (yellow) | 6 (red) | 9 (red) |
Risk Assessments
Use architecture characteristics as criteria. Create matrix of characteristics vs context (services, domains, areas).
| Benefits: Considers criteria and context | Prioritizes effort | Filters noise | Tracks risk direction (△ ▽ ○) |
Risk Storming
Collaborative exercise to determine risk within specific dimension.
Participants: Architects + senior developers + tech leads
Phase 1: Identification (Individual):
- Facilitator sends diagram, criteria, logistics
- Participants analyze independently using risk matrix
- Write risk on colored sticky notes (green/yellow/red)
Best Practice: Single criterion or context per session
Phase 2: Consensus (Collaborative):
- Post large architecture diagram
- Place sticky notes on diagram
- Analyze and reach consensus
- Consolidate notes
- Unproven/unknown tech = highest risk (9)
Phase 3: Mitigation (Collaborative):
- Identify ways to reduce/eliminate risks
- Involve business stakeholders (cost vs risk authority)
- Present options with cost implications
- Make trade-off decisions
Bonus: Apply to user-story risk in iterations
Found this guide helpful? Share it with your team:
Share on LinkedIn