| Activity 35 | Risk Storming |
A collaborative, visual technique for identifying risks in the architecture. Risk storming was proposed by Simon Brown in Software Architecture for Developers [Bro16].
Benefits
- Quickly identify risks in the proposed system architecture.
- Visualize the system by considering the level of risk.
- Constrain risk identification to architectural concerns.
- Provide a platform for all team members to elevate their concerns.
Activity Timing
60--90 minutes.
Participants
Small groups of 3--7 developers. Participants must be familiar with the architecture. This workshop can be self-facilitated by experienced participants.
Preparation and Materials
-
Views of the architecture. These can be created just-in-time or printed from appropriate sources. ...
Get Design It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
