Description: The ‘Event Storming’ is a collaborative workshop technique used to explore and analyze complex business processes. This approach allows participants to identify, visualize, and understand the interactions and relationships between different events within a system. By creating a visual map, teams can break down complicated situations into more manageable components, thus facilitating the identification of problems, improvement opportunities, and informed decision-making. Event Storming encourages collaboration and idea exchange, resulting in a deeper understanding of the processes at hand. This technique is particularly useful in environments where processes are dynamic and subject to constant changes, as it enables teams to quickly adapt to new circumstances and adjust their strategies accordingly.
History: The Event Storming technique was developed by Alberto Brandolini in 2013. Brandolini, an expert in software development and agile methodologies, introduced this approach as a way to tackle complexity in system and process design. Since its inception, Event Storming has gained popularity in the agile development and project management fields, being adopted by teams across various industries to enhance collaboration and understanding of business processes.
Uses: Event Storming is primarily used in software development, project management, and business process improvement. It allows teams to map workflows, identify bottlenecks, and better understand the interactions between different parts of a system. Additionally, it is useful for planning new features and identifying user requirements, as it facilitates communication between developers, designers, and stakeholders.
Examples: A practical example of Event Storming could be a workshop where a development team gathers to map the purchasing process of an online service. Through the technique, participants can identify key events such as selection, processing, and confirmation, as well as the interactions between these events and potential issues that may arise at each stage. Another example could be improving a service process, where interactions between users and support staff are mapped to identify areas for improvement.
