✳flâneur — a map of the web's best reading

Risk-storming

riskstorming.com · 2,031 words · saved by 1 readers

Draw one or more diagrams to show what you're planning to build or change, ideally at different levels of abstraction (e.g. using the C4 model). Gather people in front of the diagrams, and ask them to identify what they personally perceive to be risky. Write a summary of each risk on a separate sticky note, colour coded to represent low, medium, and high priority risks. Timebox this exercise (e.g. 10 minutes), and do it in silence. Ask everybody to place their sticky notes onto the diagrams, sticking them in close proximity to the area where the risk has been identified. Review and summarise the output, especially focussing on risks that only one person identified, or risks where multiple people disgree on the priority. There is risk inherent with building any piece of software; whether you're building a completely new greenfield project, or adding a new feature to an existing codebase. A risk is a possibility that something bad can happen, there being different types of risks, each wi

Risk-storming Risk-storming A visual and collaborative risk identification technique Step 1: Draw some software architecture diagrams Draw one or more diagrams to show what you're planning to build or change, ideally at different levels of abstraction (e.g. using the C4 model ). Step 2: Identify the risks individually Gather people in front of the diagrams, and ask them to identify what they personally perceive to be risky. Write a summary of each risk on a separate sticky note, colour coded to represent low, medium, and high priority risks. Timebox this exercise (e.g. 10 minutes), and do it i

Explore this link on the map →

related reading