Scaling Kanban with Domain Storytelling
If you search what is the STATIK approach in Kanban on the web, most probably you will see David Anderson’s article on top of search results. In the article, David teaches about STATIK (Systems Thinking Approach to Introducing Kanban). STATIK approach consists of 8 steps and each step is based on the previous one. Let’s summarize the steps.
Step 0: Identify Services (← I will focus on here)
For each service…
- Step 1: Understand what makes the service fit for purpose for the customer
- Step 2: Understand sources of dissatisfaction with the current system
- Step 3: Analyze demand
- Step 4: Analyze capability
- Step 5: Model workflow
- Step 6: Discover classes of service
- Step 7: Design the kanban system
- Step 8: Socialize the design and negotiate the implementation
In this post, I will talk about STEP 0. STEP Zero is a very important part of introducing the Kanban method. Kanban Method is also is very effective at the non-IT business or we can name it upstream. Non-IT businesses for example banking or insurance domains are very complex. The question is how are we going to introduce Kanban into those complex domains. In that situation applying Kanban become an art. Most of the examples in Kanban are based on the IT Software process which doesn’t make very sense to non-IT people.
We know that if we want to introduce Kanban Method, we have to apply STATIK. And In order to apply the STATIK approach, we have to start from STEP-0 which is Identify Services. And while identifying the services I found a very effective way that I will share it with you.
STEP — 0 — Identifying the Services
How do you identify the services? It is not an easy job especially if you work with complex domains like bank or insurance. In that stage, I would like to introduce the Domain Storytelling concept.
Domain Storytelling is a collaborative modeling technique that highlights how people work together. Its primary purpose is to transform domain knowledge into pictographic language.
Domain Stories are told from an actor’s perspective. Actors may be a person, a group, or a software system. Hence, we use different pictograms.
Actors create, work with, and exchange work objects and information about work objects such as documents and messages. The pictograms represent the work object’s medium.
The actor’s activities are depicted as arrows.
Identifying Value Stream Networks
Let’s start with an example: Leasing Company. It is a Non-IT business. How do we introduce the Kanban method in a Leasing Company? Assume that you are a consultant in a leasing company and you want to start that agility transformation. Step — 0 says: identify the services and in order to identify services first, we need to understand and see value networks. Here is the happy path story of the customer
You can read the rest of the article from medium : https://medium.com/@altuga/scaling-kanban-with-domain-storytelling-461eab0e4960