How To Start My Kanban – Pierre Neis

A G I L E T O U R B E I R U T 2 0 1 51 7 N O V 2 0 1 5

How To Start My KanbanHuman Relations Over Processes And Tools!

Thank You To Our Sponsors

2

GOLD

SILVER

BRONZEHOST

Thanks To Our

3

Media Partners

Eco-System Partners

Support Sponsors

Organizer

Who Am I?

Senior Lean Agile Coach Senior Scrum Coach & Trainer Agile Management Catalyst Dead, Brother & Son

C A P G E M I N I , E R D F, R U E D U C O M M E R C E . C O M , R E D M I N D , # P L AY 1 4 , O R E S , S A P U K , K I N G F I S H E R , E U R O C L E A R G R O U P, G D F S U E Z E U R O P E , A X A G R O U P, I N V I V O , C T I E , AT H O M E , A C C E N T U R E , T O U R I N G A S S U R A N C E S , C L O U D W AT T, S W I N G M O B I L I T Y, L U M E N S I O N S E C U R I T Y, W E M A N I T Y, U P W A R D C O N S U LT I N G , A G I L E 4 H R …

http://RueduCommerce.com

5P I E R R E E . N E I S | L U X E M B O U R G | B E I R U T | G E N E VA | B R U S S E L S | L O N D O N

How to Start my Kanban

Agile by Nature

H IK I F I K

K I FA KÇÀ VA?

6

People don’t have propensity to LAZINESS. People have propensity for HARD WORK. It just needs to be WORK THAT MATTERS TO THEM

Jane McGonigal, Reality is Broken

Kanban+ see the whole 1

F R O M T H E C L A S S

8Page § 97

Class Expedite

Make Expedite class visible on the board

Backlog Analysis Development Done Test

Standard

Doing Doing Doing Done Done Done

Defect

Expedite

Fixed date Expedite


9Page § 38

Kanban Rules

v  Visualize the workflow

v  Split the work into pieces, write each item on a card and put on the wall.

v  Use named columns to illustrate where each item is in the workflow. v  Limit Work In Progress (WIP) – assign explicit limits to how many

items may be in progress at each workflow state.

v  Measure the lead time (average time to complete one item, sometimes called “cycle time”), optimize the process to make lead time as small and predictable as possible.


10

Page § 74

Managing and measuring Flow

Cycle Time

Due Date Performance

Throughput

Cumulative Flow Diagram

Flow Efficiency

Issues and Blocked Work Items

Failure Load

0 50

100 150 200 250

Releas

e 1

Releas

e 2

Releas

e 3

Releas

e 4

Failure Load

Number of total defects

Escaped Defects

How Sexy Is That?11

How Motivating?12

Are You Doing That To Your Teams?

13

Really?14

I Guess You Missed Something

15

16

Agile is not just a methodology or process, it’s a mindset, a culture and working coaching and management approach supported by techniques and tools.

17

Human Relations over processes and tools

18

Let’s Make The Assumption That You Will Use This Tool To Visualise The Whole…And Get Engagement And Interaction

19

Let’s Start In A Mad Retrospective

20

W H AT M A D E S Y O U M A D D U R I N G Y O U R W O R K ?

W H AT M A K E S Y O U W H AT M A K E S Y O U H A P P Y ?

O N W H AT A R E Y O U A F R A I D ?

Ask To Individuals On What They Are Working On (No Laptop Permitted)

22

E V E RY S I N G L E TA S K S Y O U A R E W O R K I N G O N

L I S T

then ask them to consolidate all the different types of work in a common stream

24

When You Are Aligned, Then Start To Improve It

26

Kanban+ improve 2

28

B U S I N E S S A S U S U A L

D E M A N D

O U T C O M E

PR

OC

ES

S

R O O T S

F R U I T SSink&Cherrytree

29

D E M A N D

O U T C O M E

PR

OC

ES

S

This Is The Work Stream

31

Manage the Tap

In Scrum, it’s PO’s job!

D E M A N D

O U T C O M E

PR

OC

ES

S

32

Manage the Sink

In Scrum, it’s Scrum Master’s job!

D E M A N D

O U T C O M E

PR

OC

ES

S

33

what if your organisation is

looking like this?

34

or like this?

35

How can this helping us?

36

capacity

output

input

demand m

anagement

In Agile, we use LEAN techniques to understand the demand workflow. The demand flow is a simple process: demand meets capacity and, according to the capacity, demand can be treated more or less swiftly.

Agile Demand Management

Phase 1focus on the output • delivering each time helps you to focus on what

matters and enables discussion between the stakeholders

• delivering drives fear out!

37

Phase 2focus on input • managed by a single person to insure

permanent flow • empowers PO’s position • strong stakeholder’s engagement

38

Phase 3focus on the sink, on the capacity

39

40

then limit the WIP

41

In all situations, no one sees the deposit to the bottom of the sink

deposit

42

phase 2 will trouble water

trouble water

43

Agile coaches and scrum masters focus to "toss" the container in the sink (the work and team members) during the retrospective with the aim to liquefying the deposit as soon as possible.

44

prioritise, sort

45


R O O T S

F R U I T SHow To Prioritise?

46

What’s work?There are 3 types of generally accepted work: • those that produce value (fruits) • those used to produce value (roots) • and routine (transactional) aka « business-as-

usual »

Fruits are the expected outcome of planting: CA, benefits, etc ...

"Robots" are the feed channels for the existence and growth of fruits.

Anything that is neither "fruit" nor "roots" are called Business-as-usual (BAU). The BAU is time consuming and can not be totally eliminated. But it can be controlled by treatment.


R O O T S

F R U I T S

• Lean explains that you have to optimise the flow i.e. reducing the BAU, optimise the « roots » so that each harvest produce the same « fruits ».

• Agile is more pragmatic. We consider that BAU cannot be eliminated but should be under control.

• Scrum explain that you have to focus on business value i.e. increasing fruits harvesting.

• Agile also explains that both development and production proceed in a sustainable pace.

47

Too Frequently Observed Aberrations

48

Usually performance indicators are on « BAU »: • the process is defined until the end-of-times • each input produces almost the same output

(defined process)Working hypothesis have never been validated nor experienced. They are mostly driven by annual budget Here the organisation is disconnected from reality and objective is to reinforce functional silos (keeping the organisation performance at the lowest level).

49

Important are the results (fruits) • short term thinking

Too Frequently Observed Aberrations

Then You Are Ready To Design Your Board

50

… And Improved It… Again And Again

51

Until One Day, When The Team Has Found Its Particular Work Process. Then You Can Start To Make It Fancy.

52

Some Examples58

Conclusion60

Kanban Helps To Make The Work Transparent

61

Very Last Words

62

63

P R O D U C T I V I T Y E F F I C I E N C E E F F E C T I V E NE S S

P R O D U C T I V I T Y:

Y O U D O A L O T O F W O R K , B U T I S I T T H E G O O D W O R K ?

E F F I C I E N C E :

Y O U D O Y O U R W O R K E A S I LY, B U T D I D I T R E A C H T H E

M A X I M U M I M PA C T ?

E F F E C T I V E N E S S :

Y O U D O T H E R I G H T W O R K AT T H E R I G H T T I M E . I S T H E P R O C E S S R E P E ATA B L E ?

A G I L E

64

P U R P O S E

M A S T E RY

A U T O N O M Y

Purpose = only start the work with clear purpose

Autonomy = good results come from autonomous people

Mastery = mastery through continuous improvement

Result = it’s by combining purpose/autonomy/mastery that you can create a sustainable value delivering organisation

SO

UR

CE

: «

DR

IVE »

D.

PIN

K

65

P U R P O S E

M A S T E RY

A U T O N O M Y

Outcome

SO

UR

CE

: «

DR

IVE »

D.

PIN

K

R E L AT E D N E S S

S A F E C O N TA I N E R

C O M P E T E N C E

M E A N I N G

66P I E R R E E . N E I S

P I E R R E N E I S @ U P WA R D . C O N S U LT I N G

Human

Agile by Nature

W W W. A G I L E 4 H R . N E T

mailto:[email protected]?subject=