Even more than other methodologies ("frameworks", whatever), Kanban requires deep understanding in order to bring about real change and measurable results. Too many teams struggle, even after they understand the "rules" of Kanban—failing to recognize visible problems on their own boards, or not knowing how to replace old bad habits with better ones. I see the same struggle, in microcosm, when I train teams using the open-source getKanban Version 2.0. Even though the game urges teams to limit work in progress (WIP)—the linchpin of Lean and Kanban—I found that my players inevitably wanted to raise it. Over numerous classes and diverse groups of players, I tried hints, then rants, about how limiting WIP reduces cycle time. But there was a problem: play teams who took my advice and lowered their WIP weren't seeing better outcomes. In this session, I'll show you the adjustments I've made to getKanban Version 2.0 to guide players to their "a-ha" moment—a deep, personal experience they feel and remember. Now, instead of just the basics of how a Kanban board works, my students understand how to detect and solve problems that impede their flow. I see the difference when they leave the game and go back to work. For players and coaches who are already familiar with the basics of Kanban, my new open-source hacks to Version 2.0 will help you go deeper and illuminate Lean principles for your clients and teams—and yourselves!—so you can achieve real results faster.

1. hacking getKanban v2.0
@bsktcase #getKanban

2. Cheryl Hammond
@bsktcase
CTO, Peak Medical Technologies
hacking
getKanban v2.0
illuminating lean to create real change
#getKanban

3. agreements and asks
@bsktcase #Agile2016 #getKanban
Tweet your feedback and questions during and after and whenever
http://sched.co/6ec4
Submit your feedback please please please
http://github.com/bsktcase/getKanbanVersion2
Download the kit and play!

4. law of two feet
@bsktcase #getKanban

5. agenda
Intro, logistics, agreements
Case study
Core hacks
Breakouts
Close
@bsktcase #getKanban

6. http://en.wikipedia.org/wiki/Bolonka
ваня
миша

7. me
Cheryl Hammond
~20 years’ experience in software
development, exec leadership, and
organizational transformation
Passionate about agile, lean, and
making software delivery humane;
not afraid to look silly doing it
Fourth-generation Seattleite
College (university) recruiter; traveler;
bolonka lover; genealogist; feminist
@bsktcase #getKanban

8. let’s get started!
@bsktcase #getKanban

9. let’s play*!
@bsktcase #getKanban

11. our favorite lean principles
variability
failure
economics
batch sizing
wip
queues (ToC)
@bsktcase #getKanban

12. at scale@bsktcase #getKanban

13. challenges
learning objectives
time constraints
scale
gamers :)
@bsktcase #getKanban

14. case study
@bsktcase #getKanban

15. hints@bsktcase #getKanban

16. more hints
@bsktcase #getKanban

17. the “experts” play
@bsktcase #getKanban

18. the “experts” fail
@bsktcase #getKanban

19. let’s hack!
@bsktcase #getKanban

20. evil subscribers rule
@bsktcase #getKanban

21. evil Carlos rule
Intended
Block players using resource allocation
to solve the bottleneck in Test, so they
have to find other solutions
In my experience
Players become even more convinced
that resource allocation would solve the
bottleneck in Test if only it were allowed
Also, actual Carlos 
Not evil at all! @bsktcase #getKanban

22. you can’t play a player
Order of the backlog is unchangeable
I’m the Product Owner
Stories must remain on board once played
This works better if you have time to play through the entire backlog
Decisions in daily standup phase only
Could go either way on this, actually
@bsktcase #getKanban

23. let’s self-organize!
@bsktcase #getKanban

24. find your tribe
Free play group
Borrow some game kits, experiment, see what you can figure out
Guided play group
Borrow some game kits, work through some specific questions/challenges
Lean principles group
Hear more about the Lean principles we teach with this game, especially queues

25. lean principles
@bsktcase #getKanban

26. prioritization
@bsktcase #getKanban

27. competing priorities
How do you decide relative value?
Stories are measured very differently, and some are immeasurable!
What choices are informed by priority?
Whether to add a yellow, purple, or green card in the Ready column
Which stories to move to the top of their column during the “daily standup”
Of course, every story you move up, pushes other stories down
Where to allocate resources (dice) each day
@bsktcase #getKanban

28. queues
@bsktcase #getKanban

29. queue patrol
Where do you see queues on your board?
How do you address queues?
How hard is it to get rid of a queue once it’s formed?
How expensive is it?
Have you spotted the one worthless queue?
@bsktcase #getKanban

30. cycle time
@bsktcase #getKanban

31. your dice don’t earn subscribers
What’s your average cycle time now?
How much did that start to suck when you got those low-subscribers stories?
What’s your best cycle time?
How did you get it?
Why isn’t every story as fast as your fastest story?
@bsktcase #getKanban

32. beyond the classroom
@bsktcase #getKanban

33. wrap-up
@bsktcase #getKanban

34. agreements and asks
@bsktcase #Agile2016 #getKanban
Tweet your feedback and questions during and after and whenever
http://sched.co/6ec4
Submit your feedback please please please
http://github.com/bsktcase/getKanbanVersion2
Download the kit and play!

35. Cheryl Hammond
@bsktcase
CTO, Peak Medical Technologies
thank you!
#getKanban

36. now go play!
@bsktcase #getKanban