10 pitfalls when implementing kanban May 4, 2011 Mattias Skarin - - PowerPoint PPT Presentation

Mattias Skarin Kanban / Lean coach

www.crisp.se

10 pitfalls when implementing kanban

May 4, 2011

http://blog.crisp.se/mattiasskarin mattias.skarin@crisp.se

2

2011-05-13

Mattias Skarin 2

Me

4

#1 Purpose first

2011-05-13

Mattias Skarin 4

You cannot improve what you don’t understand

5

2011-05-13

Mattias Skarin 5

Beware of trojan horses..

6

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

Mattias Skarin 6

7

2011-05-13

Mattias Skarin 7

”To be able to complete more assignments on time, with less stress and more laughter!”

8

#2 Management by absence

2011-05-13

Mattias Skarin 8 Even we managers need WIP limits..

• 1. Visualize workflow
• 2. Limit Work in Progress

3.Measure and manage flow

• 4. Make process policies explicit

Kanban principles:

(.. living by them; or remove them..)

9

My management checklist

2011-05-13

Mattias Skarin 9

• 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?

10

#3 Not ready for the transparency

2011-05-13

Mattias Skarin 10

Backlog In work Done

People who build their case on heroic efforts might be in for a surprise..

11

#4 Loss of overview

2011-05-13

Mattias Skarin 11

Backlog Dev

• Acc. test

Deploy Done

[5] [2] [3] [5]

Concerned coach

• 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

discussing in front of the board Kanban sanity check:

I’m I using the right granularity?

12

#5 Ignoring WIP limits

2011-05-13

Mattias Skarin 12

Backlog Dev

• Acc. test

Deploy Done [3] [3]

”That looks fun, I’ll take that on..” ”..but they asked me to..” ??

13

2011-05-13

Mattias Skarin 13

Potential cure: Physical WIP Limits Potential cure: Physical WIP Limits

14

#6 All tasks must be on the board

2011-05-13

Mattias Skarin 14

Backlog Dev

• Acc. test

Deploy Done

[5] [2] [3] [5]

Potential mistakes..  Confusing tasks with demand  Treating all demand equal  Ignorant about incurring overhead

Want a coffee? Sure, write a Jira ticket and add it to the Kanban board

15

Ask: ”What demand do we want to learn about?”

2011-05-13

Mattias Skarin 15

Low value demand High value demand ”White noice”

 It’s nature  And our capability to meet it

16

Caught under a big pile of work?

2011-05-13

Mattias Skarin 16

17

Treatment #1: Hold back ”Overanalysis”

2011-05-13

Mattias Skarin 17

Analysis we don’t need right now Analysis required for next sprint

”Pile of work”

18

Treatment #2: Early screening of purpose

2011-05-13

Mattias Skarin 18

Backlog Dev

• Acc. test

Deploy Done

[5] [2] [3] [5]

Whishlist Dev

• Acc. test

Deploy Done

[5] [2] [3] [5]

User value defined

”I understand why this feature should be made”

Senior team member

19

Treatment #3: Let your bottleneck set the pace

2011-05-13

Mattias Skarin 19 In queue

2 stories / week

Flow Legacy team Front end team

Limit to 2 legacy team stories already here! 5 stories / week

20

Treatment #4: Fix failure demand upstream

2011-05-13

Mattias Skarin 20 Failure demand Value demand ”Pile of work” Value demand: Demand for service from customers Failure demand: Caused by failure to do something right for the customer

22

#7 Overbelief in value of planning

2011-05-13

Mattias Skarin Business area

Backlog Dev Done Planned work Unplanned work Backlog Dev Done

”How I behave”

Unplanned 2. Project 1.

”How I plan”

Project 2. We’re always stressed..

So , what you rather want?

[1] [1] Unplanned 1. Why are you not delivering the planned stuff??

23

#8 Not having a strategy for dealing with variance

2011-05-13

Mattias Skarin 23

Work to do ”Does it need a deadline? Define why..”

Flow

$$

24

#9 Improvement efforts gets eaten upp by events (lack of endurance)

2011-05-12

Mattias Skarin 24

External service partner Business area A External tech partner First line support Problem solving time

25

2011-05-12

Mattias Skarin

Managers door

Getting endurance in problem solving

Improvement kanban

What we as a team do What we need help with from the

• rganization?

Next [2] In work [2] Done

Example from Fredrik Lindgren, Crisp

26

#10

2011-05-12

Mattias Skarin 26

”Everybody thinks of changing the world, but noone about changing himself”

• Leo Tolstoy

27

Good news! Fixes can be applied

2011-05-12

Mattias Skarin 27

To our demand And our capability

28

Now, go practice!

2011-05-13

Mattias Skarin 28 Expand your toolkit: www.crisp.se/utbildning

29

Kanban training with David Anderson May 30 – 31, Copenhagen

2011-05-13

Mattias Skarin 29

www.trifork.com