Risk storming is a collaborative exercise used to determine architectural risk within a specific dimension. Common dimensions (areas of risk) include unproven technology, performance, scalability, availability (including transitive dependencies), data loss, single points of failure, and security.

While it is important to have multiple architects, as well as the development team, participate in the risk storming process, some experts argue that at some point the addition of players in this process can produce diminishing returns.

Think of a software architecture project and review the process of Risk storming. What key members of the project team do you feel are absolutely necessary to adequately identify risk via this method? What person or role do you feel doesn't need to be involved? What is the "magic number" of participants needed to successfully execute Risk storming, or, should there be no limit at all?