61
Keep Calm and Use Kanban

Keep Calm and Use Kanban

Embed Size (px)

Citation preview

Keep Calm and Use Kanban

Keep Calm and Use Kanban Limit Your WIP

Aim

Visualization1

2

3

4

History of Kanban

Context Switching

Kanban in Action

codebyts

AmberCOO

TJCEO

AyhanManufacturing

Software Development

ProcessImprovement

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.

A curved line with every point equal distance from the centre

Dr. William Edwards Deming (1900 – 1993)

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

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

• Get into a circle

• 3 projects:

1. Alphabet : A…Z

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

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

Backlog Analyze Dev ReadyTest Production

doing done doing done

Analyst Developers Tester

Our Team

Product Owner

ContinuousDeployment

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

Backlog Analyze Dev ReadyTest Production

doing done doing done

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

dfwgwrgrgwrg

g

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

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

doing done doing (2) done (2)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- 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

- 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

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