Risk Storming is a collaborative technique for identifying significant architectural challenges and constraints, especially those that could obstruct future business outcomes. section 4.3.2
Run the technique by:
- Creating architectural diagrams first, typically C4 context and container diagrams. section 4.3.2
- Overlaying risks as sticky notes, contributed by people who know the represented architecture best. section 4.3.2
- Assessing each risk with probability and impact scores from 1 to 3, then multiplying the scores. section 4.3.2
- Treating scores of 6 or above as major red risks, scores under 3 as low green risks, and intermediate scores as amber. section 4.3.2
Holiday booking architecture
A container diagram exposes risks including business logic embedded in stored procedures, alongside a monolithic legacy database coupled to almost everything and current hotspots that may not scale with target business outcomes. section 4.3.2
Use the C4 container diagram to see how multiple architectural risks can be overlaid and assessed in context. section 4.3.2
