Domain storytelling by example
Overview
About this stream
One of the things that many architects learn early when they switch from a developer role is that there is a shift in the scope of work they do and the understanding they need to build to be effective. This shift is moving away from the technology they know and worked with towards understanding their business. That is a difficult shift, because as engineers we’re wired and conditioned to provide solutions rather than deep dive into problems. “Don’t come to me with problems! Bring me solutions!” - a phrase often said by managers, which is supposed to boost ownership, mostly discourages critical thinking and finding the root cause of the actual problem.
One of the things that many architects learn early when they switch from a developer role is that there is a shift in the scope of work they do and the understanding they need to build to be effective. This shift is moving away from the technology they know and worked with towards understanding their business. That is a difficult shift, because as engineers we’re wired and conditioned to provide solutions rather than deep dive into problems. “Don’t come to me with problems! Bring me solutions!” - a phrase often said by managers, which is supposed to boost ownership, mostly discourages critical thinking and finding the root cause of the actual problem.
To equip you with tools, we’re continuing the journey into collaborative modelling as a means of understanding problem domains! In this session, we will dive deep into Domain Storytelling, a powerful technique that can give us insights into how people work together and help us transform domain knowledge into business software!
Telling stories is the most basic form of human communication. To tell a story, we invited Woody Zuill, a Lean and Agile Guide, to serve as our Subject Matter Expert. And as we dive into collaborative modelling based on the story, we’re being guided by two experts to help us capture the details and ask questions: Dr. Annegret Junker, Chief Software Architect @ codecentric AG, and Fabrizio Lazzaretti, Managing Consultant @ Wavestone!
If you wish to learn how to dive into understanding the problem domain, join us live!
People
Speakers
Woody ZuillLean and Agile Guide
Dr. Annegret JunkerChief Software Architect at codecentric
Fabrizio LazzarettiManaging Consultant at Wavestone
Karol SkrzymowskiHost / Integration Architect
Watch and read
Transcript
1773 transcript lines
- Karol
Good morning, good afternoon, and good evening, everybody.
- Karol
Welcome to another episode of Loosely Coupled by BridgingTheGap.eu.com.
- Karol
My name is Karol Skrzymowski, and I'll be your host tonight, and I hope everybody has something nice to drink.
- Karol
I have my trusty set of coffee to help me go through the evening.
- Karol
And today, we're changing the format a little bit, so we're not going to have the usual conversation, but we're doing collaborative modelling again.
- Karol
And as we did that in November with Annagret Junker, we're continuing, only not spreading with the tools so far as we did last time.
- Karol
And we're now focussing today only on the main storytelling as a method to capture requirements, capture the business logic, what the process is, et cetera, et cetera.
- Karol
And to walk us through this, we have, of course, Annagret Junker, joined by Fabrizio, and I'm going to butcher the name again, I'm always having the problem with that, Lazaretti, I hope I didn't, yeah, okay, that seems to be correct.