Scaling kanban with domain storytelling

Scaling Kanban with
Domain Storytelling
Why scaling is hard?
altug@agilekanban.istanbul
Altuğ Bilgin Altıntaş
altug@agilekanban.istanbu
l

Founder, Agile Kanban Istanbul
Alumni, Koç.Net, Risk , Hakia, Toyota Motor Europe
Lean thinker, since 2010
Accredited Kanban Trainer, since 2013

Problem
How to apply kanban to all
around organization,
especially to the
upstream?

In order to scale the
kanban, ﬁrst we have
to understand the
domain.

Domain Storytelling is a tool to
discover
the domain with our domain experts.

Why is it
useful?● To learn a new domain language.
● To record domain stories told by domain experts using a
pictographic language.
● Domain experts can see immediately if you understand
their story correctly.

The
pictographic
languageThe language of
writing by means of
drawings that
represents or
expresses an idea.

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.

Textual annotations are
useful to document
assumptions, variations and
exceptions.

To add a speciﬁc
meaning to a pictogram
we name it with a term
from the domain
language.

The pictographic
language
Waiter SAPHRM
module
Architecture
Team
Delivery
note
Actor
s
Work
object
s
Ticket
discount
Daily menu
(choices) Refund Receipt

The pictographic
language
asks for
Activitie
s
Annotation
s
(1) Assuming it’s a sunny day and the
photovoltaic plates are receiving energy.
(2) The supplier was not paid after 30 days.
returns
requests

Often a
whiteboard
and some
sticky
notes are
all you
need.

Solution
1. Understand the domain (Domain StoryTelling)
2. Find the value streams
3. Transform the value streams into Kanban System with
the help of STATIK

Ready
(5)
Calculate
Monthly
Installment
(5)
Calculate
Risk
(2)
Vote
Risk
(5)
Turn Over
the car
(∞)
Waiting for
(20)
Calculate
resale value
and
backpay
(5)
Pay
backpay
(10)
Prepare for
resale
Done
Num #
cars -
outside :
345
Discarde
daltug@agilekanban.istanbul
Coordination Level Kanban

Ready
(5)
Fill out the
form
(5)
Create
customer
proﬁle
(2)
Create risk
assessment
(5)
Calculate
risk resale
value
(20)
Decide
(5)
Done
Approved
Rejected
Operation Level Kanban
Risk Team gives RiskService
RiskTeam

Features
Kanban Board
(5)
Committed
Work
Doin
g
Don
e
Idea
s
(5)
Analyze
(5)
Dev
Read
y
(6)
Development
(10)
Test
Read
y
(5)
Testing
(10)
Deplo
y
Ready
(5)
Deploy
On
Cloud
Don
e
Development and
Test
Bugs
Kaizen

altug@agilekanban.istanbul From : Practical Kanban - klaus leopold
Project Level Kanban

Find the value
streams.

altug@agilekanban.istanbul From : Practical Kanban - klaus leopold
Problem:

Find the
actors.

Find the the
relations.

What is
service?? :
?
Service
Providers
Service
Consumers

? : ? → Scaling Kanban Method
1 : 1 → One Team gives One Service
1 : N → One Team gives Multiple Services
N : 1 → Multiple Teams give One Service
N : N → Multiple Teams give Multiple
Service

1 : 1
One Team gives One
Service.

(∞)
Backlog
(5)
In Progress
(6)
Test
Don
e
CommitmentPoint
Expedite Line
Customers are
getting Operation
Service
1:1 - Operational Level Kanban
Operation Team gives Operation Service
OperationTeam

1:1 - One Team = One Service
1
2
3

(∞)
Backlog
(5)
In Progress
(6)
Test
Don
e
1 2
3
1:1 - One Team = OneService

1 : N
One Team gives More Than One
Service.

1:N - One Team = Multiple Services
1
2
3 4 7
6
8
5

1
2
3 4 7
6
8
5

anbul
1
2
3 4 7
6
8
5
altug@agilekanban.ist

N : 1
Multiple Teams give One
Service.

The customer wants to lease a car so he contacted the sales person.
The salesperson calculates the monthly installment for the contract
and sends it to the customer for signature.
After that salesperson passes the contract to the risk manager, she
starts to wait for the response from the risk department. At this point
risk manager calculates and vote the risk for that contract. If
everything goes well, the salesperson turns over the car to the
customer.
After the leasing period customer returns the car to the salesperson,
the salesperson calculates the resale value and pays payback value
to the customer. Last step is the salesperson prepared for resale.
Leasing a Car Company

Apply Kanban highest level
possible.

Before try to identify the
value streams (workflows),
first understand the domain.

1
9
3
12
10
8
13
2
11
4
7
6
5
N:1 - Multiple Teams = OneService
nbul
14
altug@agilekanban.ista

Read
y
(5)
Calculate
Monthly
Installment
(5)
Calculate
Risk
(2)
Vote
Risk
(5)
TurnOver
the car
(20)
Calculate
resale value
andbackpay
(5)
Pay
backpay
(10)
Prepare for
resale
(∞)
Waitingfor
Done
Num # cars
- outside:
345
1
9
3
12
10
2
11
4
7
6
5
13
14
8

Ready
(5)
Calculate
Monthly
Installment
(5)
Calculate
Risk
(2)
Vote
Risk
(5)
Turn Over
the car
(∞)
Waiting for
(20)
Calculate
resale value
and
backpay
(5)
Pay
backpay
(10)
Prepare for
resale
Done
Num #
cars -
outside :
345
Coordination Level Kanban
RiskTeam SalesTeam Repair & CleanTeam

Risk Team gives Risk
Service
Sales Team gives Sales
Service
Repair & Clean Team gives
repair and Clean Service
RiskTeam
Repair & CleanTeam
SalesTeam

altug@agilekanban.istan bul
1
9
3
12
10
8
13
2
11
4
7
6
5
14
N:1 - Multiple Teams = OneService

Risk Team gives RiskService
RiskTeam
1
3
4
5
7
6
2

Ready
(5)
Fill out the
form
(5)
Create
customer
proﬁle
(2)
Create risk
assessment
(5)
Calculate
risk resale
value
(20)
Decide
(5)
Don
e
Approve
d
Rejected
1
3
4
5
7
6
2

Ready
(5)
Fill out the
form
(5)
Create
customer
proﬁle
(2)
Create risk
assessment
(5)
Calculate
risk resale
value
(20)
Decide
(5)
Done
Approved
Rejected
Operation Level Kanban
Risk Team gives RiskServiceRiskTeam

N : N
Multiple Teams give Multiple
Services.

Let’s assume that you are head of software
development and support department. Our customers
are HR, Finance and marketing departments.
As a software development and support department,
we are working on a project with Finance department.
Also we are developing CR for HR and Marketing
departments. Of course bugs are our reality and all
bugs should be fix by of software development and
support department.
Software Department

Let’s assume that you are head of software development and
support department. Our customers are HR, Finance and
marketing departments.
As a software development and support department, we are working
on a project with Finance department. Also we are developing CR for
HR and Marketing departments. Of course bugs are our reality and
all bugs should be ﬁxed by of software development and support
department.
Software Department

3
2
1
4
5
6
7
9
8
N:N - Multiple Teams = MultipleServices

3
2
1
4
5
6
7
9
8
Features
(5)
Committed
Work
Doing Done
Ideas
(5)
Analyze
(5)
Dev
Read
y
(6)
Development
(10)
Test
Read
y
(5)
Testing
(10)
Deploy Ready
(5)
Deploy On Cloud
DoneDevelopment and Test
Bugs
Kaizen

Ideas
Development and Test
(5)
Committed
Work
Deploy
On
Cloud
Doing Done
(5)
Analyze
(10)
Dev
Ready
(6) (10)
Test
Ready
(5)
Testing
(10)
Deploy
Ready
(5)
Bugs
Features
Kaizen
Done
Coordination Level Kanban Board

Features
(5)
Committed
Work
Doin
g
Don
e
Idea
s
(5)
Analyze
(5)
Dev
Read
y
(6)
Development
(10)
Test
Read
y
(5)
Testing
(10)
Deplo
y
Ready
(5)
Deploy
On
Cloud
Don
e
Development and
TestKaizen
Coordination Level Kanban Board
Analyst Team Architecture Team Development and TestTeam
HR
Department
Bugs
DeploymentTeam
Finance
Department
Marketing
Department

Analyst Team give Analyst
Service
Architecture Team give
Architecture Service
Development and Test
Team give Dev andTest
Services
Analyst Team
Development and
Test Team
Architecture Team
Deployment Team give
Devops ServiceDeploymentTeam

N : N
Shared
Services

Value Streams
and Shared
Services
1
2
3
4
5
6
7
8
9
11
12
13
14
15
16
17
10

Value Streams
and Shared
Services
1
2
3
4
5
6
7
8
9
11
12
13
14
15
16
17
3
2
1
10

ltug@agilekanban.istanbula
Value Streams
and Shared
Services

Architecture
Team
Analyst Team Developmentand
Test Team
Deployment
Team
Shared
Services
Shared
Services
(∞)
Backlog
(5)
In Progress
(6)
Test
Done
Expedite Line
Ideas
(5)
Committed
Work
(5)
Analyze
(5)
Dev
Ready
(6)
Development
(10)
Test
Ready
(5)
Testing
(10)
Deploy Ready
(5)
Deploy
On Cloud
Features
Doing Done
Bugs
Kaizen
Development and Test Done
Features
(5)
Committed
Work
Doing Done
Ideas
(5)
Analyze
(5)
Dev
Ready
(6)
Development
(10)
Test
Ready
(5)
Testing
(10)
Deploy Ready
(5)
Deploy
On Cloud
DoneDevelopment and Test
Bugs
Kaizen

Architecture
Team
Analyst Team Developmentand
Test Team
Deployment
Team
Shared
Services
Shared
Services
(∞)
Backlog
(5)
In Progress
(6)
Test
Done
Expedite Line
Featur
es
(5)
Committ
ed Work
Doi
n g
Do
ne
Ideas
(5)
Analyze
(5)
Dev
Rea
d y
(6)
Developme
nt
(10)
Test
Rea
dy
(5)
Testi
ng
(10)
Deploy
Ready
(5)
Deploy
On
Clou
d
DoneDevelopment and
Test
Bugs
Kaizen

N : ?
Upstream
Kanban

Upstream Kanban
1
3
4
5
6
7
8
9
2

1
2
3
4
5
6
7
8
9
Upstream Kanban

kanban.istanbulaltug@agile
Finance
Department
Marketing
Department
Business
Team
Analyst
Team
Architecture
Team
Development
Team
TestTeam Devops
Team

Thank You.
Any Questions?
altug@agilekanban.istanbu
l

Scaling kanban with domain storytelling

Recommended

Recommended

More Related Content

Similar to Scaling kanban with domain storytelling

Similar to Scaling kanban with domain storytelling (20)

More from Agile Club

More from Agile Club (15)

Recently uploaded

Recently uploaded (13)

Scaling kanban with domain storytelling