10 pitfalls when implementing kanban May 4, 2011 Mattias Skarin Kanban / Lean coach www.crisp.se http://blog.crisp.se/mattiasskarin mattias.skarin@crisp.se
Me 2011-05-13 2 2 Mattias Skarin
#1 Purpose first You cannot improve what you don’t understand 2011-05-13 4 4 Mattias Skarin
Beware of trojan horses.. 2011-05-13 5 5 Mattias Skarin
Some purposes from real teams ”Enable higher degree of self organisation..” ”Growing team member skill sets” ”Know when we can deliver..” ”Get focus. (On completing, not starting)” 2011-05-13 6 6 Mattias Skarin
”To be able to complete more assignments on time, with less stress and more laughter !” 2011-05-13 7 7 Mattias Skarin
#2 Management by absence Even we managers need WIP limits.. Kanban principles: 1. Visualize workflow 2. Limit Work in Progress 3.Measure and manage flow 4. Make process policies explicit (.. living by them; or remove them..) 2011-05-13 8 8 Mattias Skarin
My management checklist Can I see the most valuable things to work on? Are we keeping WIP limits? Are policies transparent, and in use? Is there any blocking problems that should be dealt with? For learning over time: Are we measuring flow? 2011-05-13 9 9 Mattias Skarin
#3 Not ready for the transparency In Backlog Done work People who build their case on heroic efforts might be in for a surprise.. 2011-05-13 10 10 Mattias Skarin
#4 Loss of overview Backlog Dev Acc. test Deploy Done Kanban sanity check: [5] [2] [3] [5] • I can see the most valuable thing to work on right now • I can see if we are keeping our WIP limits • Team members are I’m I using the right granularity? discussing in front of the board Concerned 2011-05-13 coach 11 11 Mattias Skarin
#5 Ignoring WIP limits Backlog Dev Acc. test Deploy Done [3] [3] ”That looks fun, I’ll take that on..” ”..but they asked me to..” ?? 2011-05-13 12 12 Mattias Skarin
Potential cure: Physical WIP Limits Potential cure: Physical WIP Limits 2011-05-13 13 13 Mattias Skarin
#6 All tasks must be on the board Want a coffee? Backlog Dev Acc. test Deploy Done [5] [2] [3] [5] Sure, write a Jira ticket and add it to the Potential mistakes.. Kanban board Confusing tasks with demand Treating all demand equal Ignorant about incurring overhead 2011-05-13 14 14 Mattias Skarin
Ask: ”What demand do we want to learn about?” It’s nature And our capability to meet it High value demand Low value demand ”White noice” 2011-05-13 15 15 Mattias Skarin
Caught under a big pile of work? 2011-05-13 16 16 Mattias Skarin
Treatment #1: Hold back ”Overanalysis” Analysis Analysis we required for don’t need next sprint right now ”Pile of work” 2011-05-13 17 17 Mattias Skarin
Treatment #2: Early screening of purpose Senior team member User Whishlist Dev Acc. test Deploy Done value [5] Backlog Dev [2] Acc. test [3] Deploy [5] Done defined [5] [2] [3] [5] ”I understand why this feature should be made” 2011-05-13 18 18 Mattias Skarin
Treatment #3: Let your bottleneck set the pace In queue Front end team 5 stories / week 2 stories / week Limit to 2 legacy team stories already here! Flow Legacy team 2011-05-13 19 19 Mattias Skarin
Treatment #4: Fix failure demand upstream Value demand Failure demand ”Pile of work” Value demand: Demand for service from customers Failure demand: Caused by failure to do something right for the customer 2011-05-13 20 20 Mattias Skarin
#7 Overbelief in value of planning ”How I plan” Backlog Backlog Dev Dev Done Done 1. Project 2. Unplanned Planned [1] work ”How I behave” Business Unplanned [1] area 1. Unplanned work 2. Project Why are you not delivering the planned stuff?? So , what you rather We’re always want? stressed.. 2011-05-13 22 Mattias Skarin
#8 Not having a strategy for dealing with variance $$ Work to do Flow ”Does it need a deadline? Define why..” 2011-05-13 23 23 Mattias Skarin
#9 Improvement efforts gets eaten upp by events (lack of endurance) External tech partner External service partner Problem solving time Business area A First line support 2011-05-12 24 24 Mattias Skarin
Getting endurance in problem solving Managers door Improvement kanban Next In work Done [2] [2] What we as a team do What we need help with from the organization? Example from Fredrik Lindgren, Crisp 2011-05-12 25 Mattias Skarin
#10 ”Everybody thinks of changing the world, but noone about changing himself” - Leo Tolstoy 2011-05-12 26 26 Mattias Skarin
Good news! Fixes can be applied To our demand And our capability 2011-05-12 27 27 Mattias Skarin
Now, go practice! Expand your toolkit: www.crisp.se/utbildning 2011-05-13 28 28 Mattias Skarin
Kanban training with David Anderson May 30 – 31, Copenhagen www.trifork.com 2011-05-13 29 29 Mattias Skarin
Recommend
More recommend
