In previous chapters, we learned how important it is to understand the actual problem. We also went deeper into the concept of Ubiquitous Language and explained that it is not only a glossary of terms but also the system's behavior described in words.
It remains unclear how to start the knowledge crunching and how to intensify our communication with domain experts to understand the problem space better and get a proper overview of what are we going to build.
Very often, we see that developers get to know the domain in the form of requirements. We have already been through this topic, and by now you should realize that requirements have their flaws. So, you want to improve your knowledge by talking directly to domain experts and organizing a workshop or meeting with them. Some people come, and you have a conversation for two or three hours; a lot of things get...
