In one of my previous posts on Domain Storytelling I discussed introducing Impact Mapping as a workshop headliner to enable smoother workshop facilitation. This time we take a look on how to use both Domain Storytelling and Impact Mapping to sustainably manage your product backlog on a daily basis. Teams…

The quality of a boundary in a system can be defined by the quantity of logical dependencies between the parts of the system on each side of a boundary. It is by no means coincidental use of adjective logical along with the noun boundary. I am referring to 4+1 View…

Working on legacy systems comes often with a challenge of trying to figure out the underlying reasoning behind a piece of observable behavior. Perhaps coded years ago, those legacy system features are not easily linked with business needs that were present at a time. For the development teams that go…

The notion of quality in software is likely a matter of debate and opinion rather than having a strict definition we can relate to. One of the more distinguished attempts to put some perspective on the topic was presented by Gojko Adzic in his blog post on “Redefining Software Quality”…

Building on my last post about Domain Storytelling this time I will dive a bit deeper in the technique from the perspective of a facilitator. After facilitating a few of the Domain Storytelling workshops it was becoming obvious that when complex business rules were being presented the single facilitator was…

Two years ago at Domain-Driven Design Europe 2018 conference Domain Storytelling was introduced to a wider audience by Stefan Hofer and Henning Schwentner. …

After 20 years in the software industry one grows accustomed to certain terms and eventually takes them for granted. You might already have suggested terms like “modularization” or “architecture” as primary examples. Everyone involved in the value chain of software delivery will probably have some idea of the definition of…