Scenario Hunting is Design First Test Method

Scenario Hunting Process

Scenario Hunting comprises a series of small steps to translate visual design artifacts (like Event Storming sticky notes) into high-quality pieces of software. During implementation, developers’ focus is on the role the scenario under test plays in the system from a bigger picture perspective.

5 Minute Demo

Install the Test Framework

Simply click here to install the open source Miro addon.

Build Faster

Minimize the time you spend switching between coding and modeling. Automate less important but costly jobs. It Improves both modeling and development speed.

Focus on Model

Focus on what deserves your attention (the model). Derive code from the model. Deal with code on the sidelines.

Coding is Modeling

Minimize the gap between coding and modeling. Use the right environment, and the right people, at the right time, for the right job. Manage your resources.

Task Switching

Deal with modeling and coding as a single task to minimize the task switching penalty. It keeps you healthier and improves your development speed.

Product Quality

Improve shared understanding while separating business concerns from technical concerns by time, environment, and potentially people.

Shorten Feedback Loops

Minimize the time you spend integrating new scenarios with code, refactor and acquire deeper insight. Then share and update the model. Avoid falling into technical rabbit holes.


Share important model adjustments during implementation with anyone whenever needed. Short feedback loops help you to keep the visual model up to date.

Complement Mob

Scenario Hunting can be used with Mob Programming. Some of driver’s job can be automated.

Event Storming to Scenario Hunting