Having seen it before in a sneak-peek, I must say that it has improved even more! This is a must-see talk for anybody in tech and a must-have talk for many conferences, within or outside of PHP.
5/5 Would see again, if only for being reminded of the good points Aisha makes we can still improve as community.
Interesting talk and topic. The OWASP always feels a bit enterprise-like to me, with all the acronyms and complicated naming that goes with it, but Katy did a good job making things a lot simpler.
I would've liked to see a couple more examples (perhaps about doing it wrong vs doing it the correct way) of more topics.
I did go home with an actionable item, so I'd say there's something in it for everybody.
As much as I've left the FIG alone in the past, this talk inspired me to take look at it again. Thank you for the interesting talk, well brought.
Thanks for the good overview and introduction. I feel this topics has been done many times before, but judging from all the times it's still going wrong, there's a need for it! So keep up the good work of spreading the word.
An excellent overview of the concepts, giving a clear sense of structure to something that could easily lose focus. I'll definitely be integrating it into our process.
Only suggestion would be to spend a little more time going over the rules of poker, as some were not very clear on the rules.
Other than that minor issue, highly recommended.
I am leaving this so the bar can open, thus
I am leaving this so the bar can open
I am leaving this so the bar can open.
Good talk, and very recognisable. However, it felt a bit all over the place. I guess the slow transitions between slides and the often looking at the slides didn't help. Also, it was hard to understand the in-crowd jokes watching remotely from the track 2 room.
That being said, it's a very interesting angle and a topic that more people should think about and be thankful for.
Great tutorial, very interesting subject which I hadn't heard anything about before.
Event storming still feels like quite a young methodology, and hopefully over time it will become a bit more rigorous, as it felt slightly very open to interpretation at this point.
The approach does seem a very powerful tool for eliciting requirements for a software project, and given this introduction, I would like to give it a try some time for a real project.