Top Banner
Keep Calm and Use Kanban
61

Keep Calm and Use Kanban

Aug 04, 2015

Download

Business

codebyts
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Keep Calm and Use Kanban

Keep Calm and Use Kanban

Page 2: Keep Calm and Use Kanban

Keep Calm and Use Kanban Limit Your WIP

Page 3: Keep Calm and Use Kanban
Page 4: Keep Calm and Use Kanban
Page 5: Keep Calm and Use Kanban
Page 6: Keep Calm and Use Kanban

Aim

Page 7: Keep Calm and Use Kanban

Visualization1

2

3

4

History of Kanban

Context Switching

Kanban in Action

Page 8: Keep Calm and Use Kanban

codebyts

AmberCOO

TJCEO

AyhanManufacturing

Software Development

ProcessImprovement

Page 9: Keep Calm and Use Kanban
Page 10: Keep Calm and Use Kanban

While you are travelling down this road there is a chance that one or more rocks of varying size may fall from the slopes on one or both sides of you. You should be aware of this before you travel this way so that you are cautious of this particular type of hazard.

Page 11: Keep Calm and Use Kanban
Page 12: Keep Calm and Use Kanban

A curved line with every point equal distance from the centre

Page 13: Keep Calm and Use Kanban
Page 14: Keep Calm and Use Kanban
Page 15: Keep Calm and Use Kanban
Page 16: Keep Calm and Use Kanban
Page 17: Keep Calm and Use Kanban
Page 18: Keep Calm and Use Kanban
Page 19: Keep Calm and Use Kanban
Page 20: Keep Calm and Use Kanban
Page 21: Keep Calm and Use Kanban
Page 22: Keep Calm and Use Kanban
Page 23: Keep Calm and Use Kanban
Page 24: Keep Calm and Use Kanban

Dr. William Edwards Deming (1900 – 1993)

Page 25: Keep Calm and Use Kanban
Page 26: Keep Calm and Use Kanban
Page 27: Keep Calm and Use Kanban
Page 28: Keep Calm and Use Kanban
Page 29: Keep Calm and Use Kanban

With the timer ready1. Write each letter or number on separate

lines.

letters and numbers would beABCDEFGHIJ3 6 9 12 15 18 21 24 27 305 10 15 20 25 30 35 40 45 50

Page 30: Keep Calm and Use Kanban

With the timer ready1. Write each word on separate lines.

2. Write each letter on separate lines, switching from letter to letter or number to number.

In this case, first A, then 3, then 5, then B and so on…

letters and numbers would beABCDEFGHIJ3 6 9 12 15 18 21 24 27 305 10 15 20 25 30 35 40 45 50

Page 31: Keep Calm and Use Kanban

• Get into a circle

• 3 projects:

1. Alphabet : A…Z

2. 3x: 3, 6, 9, 12…

3. 5x: 5, 10, 15, 20…

Page 32: Keep Calm and Use Kanban
Page 33: Keep Calm and Use Kanban
Page 34: Keep Calm and Use Kanban

Backlog Analyze Dev ReadyTest Production

doing done doing done

Page 35: Keep Calm and Use Kanban

Analyst Developers Tester

Our Team

Product Owner

ContinuousDeployment

Page 36: Keep Calm and Use Kanban

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 37: Keep Calm and Use Kanban

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 38: Keep Calm and Use Kanban

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 39: Keep Calm and Use Kanban

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 40: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

Page 41: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 42: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 43: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 44: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

gdfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

gdfwgwrgrgwrg

g

Page 45: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

gdfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

gdfwgwrgrgwrg

g

Page 46: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

gdfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 47: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 48: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

URGENT

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 49: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

URGENT

Expedited

Page 50: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

URGENT

Page 51: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

URGENT

Page 52: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

URGENT

dfwgwrgrgwrgg

Page 53: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 54: Keep Calm and Use Kanban

Backlog Analyze (2) Dev (4) ReadyTest (2) Production

doing done doing (2) done (2)

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Feature BUG Maint. Change Request

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Your wait time from here is24 days

Page 55: Keep Calm and Use Kanban

- 24 stories completed in 3 weeks- 8 stories per week

Page 56: Keep Calm and Use Kanban

- 24 stories completed in 3 weeks- 8 stories per week

- 160 stories in backlog- 160 / 8 = 20 weeks to complete (+/-)

Page 57: Keep Calm and Use Kanban

- 24 stories completed in 3 weeks- 8 stories per week

- 160 stories in backlog- 160 / 8 = 20 weeks to complete (+/-)

- 3 weeks is 15 working days- I have 5 developers, that is 75 developer days

Page 58: Keep Calm and Use Kanban

- 24 stories completed in 3 weeks- 8 stories per week

- 160 stories in backlog- 160 / 8 = 20 weeks to complete (+/-)

- 3 weeks is 15 working days- I have 5 developers, that is 75 developer days

- 75 / 24 = 3.125 avg. developer days per story- This is the load factor in XP

Page 59: Keep Calm and Use Kanban
Page 60: Keep Calm and Use Kanban

Features Planning Development MarketingLegal Releaseddoing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Page 61: Keep Calm and Use Kanban