DDD iterative way
ksouf opened this issue · 5 comments
Hi Crew
I was thinking about iteratively using model processing.
I think is better to add when to do it also if we are in an agile context.
what do you think?
PS: I can help if you're open to it.
Hi @ksouf,
I agree that modelling should be iterative and we've put a few sign posts and warning in the documentation trying to advise people to not just model as a single process. If you have some ideas about how we can improve that messaging that would be great.
How to apply these steps iteratively/continuously as an agile process seems like a good area to focus on. Feel free to outline your ideas in here or create a draft PR.
Thanks
Isn't this issue addressed with our new overview image?
yes it is but not in the way i expected :)
Maybe you want to share your expecations / ideas?
Sure sorry for the late response.
Here what I think : for the first iteration (understand/discover). in an itrative way we should get as fast as possible to coding so we can get a feedaback as much as possible. i don't thin it's a wise idea to iterate only on understand discover.
To give an example and be more specific i was thinking on somthing that Tobias Goeschel : Domain Prototyping
https://www.youtube.com/watch?v=gDT5PKIYsT0
the thing that feels dangerous is doing it in waterfall way. I mean it 's better than it was before but we can make it even better ;)
Like i said i'm open to help if you'd like to.