Lean conference 2014 Mike Burrows - introducing and developing Kanban systems

Introducing Kanban (using STATIK) @asplake #investni

Introducing Kanban(using STATIK)

Mike Burrows@asplake@[email protected]


Continuous improvement:• Very hard to sustain on its own• Creative knowledge work presents its own special

challenges


• “Evolutionary change for your technology business”(Anderson)

• The humane, “start with what you do now” approach to change (@KanbanInside)

• Developed pragmatically by and for people engagedin creative knowledge work

The Kanban Method


• A new name for the Kanban Method’s best-kept secret

• A repeatable (and humane) way to get started with Kanban

• A way to invigorate even the most shallow of implementations

STATIK


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


Reverse STATIK







6. Roll out


5. Kanban systems


5. Kanban systems

How well is our work represented?


5. Kanban systems

How well does it support our workflow?


5. Kanban systems

Policies?

~~~ ~~ ~~~~~ ~~ ~~ ~~~ ~~~~~~

~~~ ~~ ~~~~~ ~~ ~~ ~~~ ~~~~~~


5. Kanban systems

4

Limits on work-in-progress (WIP)?


5. Kanban systems

4



5. Kanban systems


4


5. Kanban systems

Is our capacity respected when we replenish & commit?


5. Kanban systems

Do we coordinate deliveries effectively, commit at the right time?


5. Kanban systems

Effective feedback loops?


5. Kanban systems


4. Classes of service

5. Kanban systems

Review:

• Different types of work items and where they sit

• WIP limits and other controls on WIP

• Commitment points

• Policies

• Feedback loops

6. Roll out



Managing to different kinds of expectations




Fixed Date




Expedited Fixed Date




ExpeditedStandard Fixed Date




Expedited IntangibleStandard Fixed Date



Q: Fixed Date, Expedited, Standard or Intangible?

1. Manually add space to a server that has reached 90% full

2. Roll out an automated disk space provisioning system

3. Fix the server that is keeping the trading system out of the market (and costing us $1m per hour)

4. Report to the board next Friday to explain ourselves


3. Knowledge discovery process


• Recognise different kinds of customer expectation

• Qualitative categories before any quantitative ranking

• Make explicit both internally and externally

• Select (prioritise) and risk-manage items accordingly

6. Kanban systems



What don’t we know?



What are we discovering here?



Or here?


2. Demand & capability


• Creative knowledge work demands a shift:

• away from taking orders, satisfying requirements

• towards building the capability to anticipate, explore & meet needs at the right time

• Understand what kind of knowledge is acquired at each stage of the process

• Implement through customer validation, collaboration, policies, allocations




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?



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


1. Sources of dissatisfaction


• Attend to both sides of this equation

• Outside-in as well as inside-out

• Expect changes at the boundaries to impact system design, and vice-versa




Internal

External


0. Purpose


• Outside-in as well as inside-out

• Assumes a system scope and a boundary, both potential sources of dissatisfaction in their own right

• Sources are much easier to identify when there is already some transparency



“STATIK Lite”







6. Roll out


0. Purpose

What Who W

HY


STATIK-0






6. Roll out



Sustained, purposeful change with Kanban




6. Roll out





Sustained, purposeful change with Kanban




6. Roll out




Understanding

Agreement Re

spec

t

Collaboration

Customer

focus

Transparency Balance Flow

Leadership


Resources


Autumn Conference Series

Moscow, London, Paris, Istanbul, Hamburg, Bangalore– see conf.leankanban.com

http://conf.leankanban.com/


Community Connections

Coaching Tools

Games

More Resources

See positiveincline.com/index.php/resources/

http://positiveincline.com/index.php/resources/


Thank you!

Mike Burrows@asplake@[email protected]

Documents

Lean conference 2014 Mike Burrows - introducing and developing Kanban systems