The document outlines the STATIK framework for implementing Kanban, which involves understanding the system's purpose, sources of dissatisfaction, demand and capability, knowledge discovery processes, classes of service, Kanban systems design, and rollout. It emphasizes understanding multiple perspectives, balancing demand and capability, discovering needs through collaboration and validation, recognizing different expectations through classes of service, and designing systems to pursue sustained evolutionary change through Kanban values like transparency and respect.
1 of 74
More Related Content
Inside Lean Kanban (#lkuk14 keynote)
1. Inside Lean Kanban
…the humane,
start with what you do now
approach to change
Mike Burrows
@asplake
@kanbanInside
mike@djaa.com
3. Understanding FP1: Start with what you do now
Agreement
FP2: Agree to pursue evolutionary
change
Respect
FP3: Initially, respect current processes,
roles, responsibilities and job titles
45. STATIK
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
46. Reverse STATIK
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
53. 4. Classes of service
5. Kanban systems
Review:
• The visibility of work items and where
they sit
• Policies
• WIP limits and other controls on WIP
• Commitment points
• Feedback loops
6. Roll out
54. 4. Classes of service
Managing to different kinds of expectations
55. 4. Classes of service
Fixed Date
Managing to different kinds of expectations
56. 4. Classes of service
Expedited Fixed Date
Managing to different kinds of expectations
57. 4. Classes of service
Expedited Intangible Fixed Date
Managing to different kinds of expectations
58. 4. Classes of service
Standard Expedited Intangible Fixed Date
Managing to different kinds of expectations
59. 3. Knowledge discovery process
4. Classes of service
• Recognise different kinds of customer
expectation
• Organise: qualitative categories before any
quantitative ranking
• Make explicit both internally and externally
• Select (prioritise) and risk-manage items
accordingly
6. Kanban systems
62. 2. Demand & capability
3. Knowledge discovery process
• Understand what kind of knowledge is
acquired at each stage of the process and
aim to acquire it quickly
• Implement through customer validation,
customer collaboration, policies, allocations
4. Classes of service
63. 2. Demand & capability
3. Knowledge discovery process
• Keep testing your understanding; validate
relentlessly!
• Encourage the shift:
– away from taking orders & satisfying
requirements
– towards building the capability to
anticipate, explore & meet needs at the
right time
4. Classes of service
64. 2. Demand & capability
Demand
• How work arrives
• How frequently
• From whom
• Of what types
• In what sizes
• etc
Capability
• How work leaves
• Batches
• Lead time(s), delivery rate
• Predictability
• Flow efficiency
• etc
Are these in balance?
65. 2. Demand & capability
Demand
• Weekly calls with business
managers
• Ad-hoc meetings with user reps
• Mostly business-driven work;
some market-driven, regulatory
and infrastructure change
• Typically 2-10 days
development work per item
Capability
• Releases every 6 weeks
• But ~18 week lead time
• Flow efficiency percentage in
single digits
• (5 days in 18 weeks is 4%)
Outline example
66. 1. Sources of dissatisfaction
2. Demand & capability
• Attend to both sides of this equation
• Internal and external perspectives
• Expect changes at the boundaries to impact
system design, and vice-versa
3. Knowledge discovery process
68. 1. Sources of dissatisfaction
Internal
(self awareness)
External
(empathy)
Source: Markus Andrezak @markusandrezak #lascot14
69. 0. Purpose
1. Sources of dissatisfaction
• Two perspectives (at least!)
• Assumes a system scope and a boundary
– Both of these are potential sources of
dissatisfaction in their own right
• Sources are much easier to identify &
address when there is already some
transparency
2. Demand & capability
71. Reverse STATIK
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
72. Sustained, purposeful change with Kanban
0. Understand the purpose of the system
1. Understand sources of dissatisfaction
2. Analyze demand and capability
3. Model the knowledge discovery process
4. Discover classes of service
5. Design kanban systems
6. Roll out
Agreement
Respect
Balance Flow
Customer
focus
Transparency
Collaboration
Leadership