| | |
|---|
| | | ## Facilitation Guidelines |
|---|
| | | |
|---|
| | | * Present the slides to introduce Event Storming, what it is, why we use it and walk through the steps in how to use it |
|---|
| | | * Present the residency examples provided in slides and encourage any Labs people present to talk about their experiences of using the practice |
|---|
| | | * Present the residency examples provided in slides and encourage any Labs people present to talk about their experiences of using the practice. We have found presenting a real Event Storm (ideally with the physical board) is much more effective than presenting the slides and has resulted in much better conversation. If you have access to real artefacts, consider reducing the slides. |
|---|
| | | * Kick off the interactive exercise: |
|---|
| | | * As a class, put up the pre-baked Event Storm. The Facilitator should talk through as he/she puts up the events, commands, user, external system, etc. |
|---|
| | |  |
|---|
| | | * Table groups should then replicate the pre-baked event storm artifact and follow the instructions in the slide to extend this to cover additional functionality. Some examples have been given. You could also encourage participants to think about their own experience of to-do-list management |
|---|
| | | * Time box of 20 minutes. Facilitators should walk round the room and help with any questions and engage in conversations |
|---|
| | | * As a class, talk about aggregates and what aggregates might apply to these emerging event storms |
|---|
| | | * |
|---|
| | | * As a class, talk about aggregates and what aggregates might apply to these emerging event storms |
|---|
