Roots Conference BergenWednesday 25.05.2011

Arild Strømhylden – Ketil Jensen

Kanban Game

Outline

• A really short introduction to Kanban• Playing the getKanban game• Experience exchange / summary

About us

@stromhylden @ketilj

Show of Hands

- How many have heard about Kanban?- How many uses it or have used it?

What is Kanban?

The “Father” of TPS and Kanban

Kanban in Software Development

2004…..2006….2007….2008….2009….2010

David Anderson introduced Kanban at XIT Microsoft

Kanban introduced at Corbis for team with +50 people

Several sessions about Kanban at Agile 2008

Kan Ban – Visual Card

Visualizing the Workflow And Limiting WIP

Creates a Pull System ForJust In Time Work

Kanban is About Flow and Sustainable Pace

Classes of service

Typical Class-of-Service Definitions

• Expedite– Fix now

• Fixed Delivery Date– Significant delay incurred on

or from a specific date in near future

• Standard Class– (Near) linear cost of delay

beginning immediately

• Intangible Class– No tangible cost of delay

within reasonable lead time to delivery window

3. Tracking

Cumulative Flow Diagram

http://open.bekk.no/2009/11/03/cumulative-flow-diagrams-with-google-spreadsheets

Control chart

Let’s play the

getKanban game!

Things to Remember While Playing

•- One person keep an eye on time : < 7 mins per day

•- 3000 $ bonus to the team finishing first

•- On day 14: Play both event card 14 and 19!

•- Standard (yellow) and Intangible stories (green) should be pulled into ready queue in sequence

•- Have a problem ? Ask

•- Have fun

Game Debrief

•What stragegies did teams use?

Game Debrief

Events: - Blocker- Carlos arrival and departure- Expedite request- Fixed date stories

- Q reduction - What happened to lead time?

Decisions

- Daily- Expedite- Q replenishment

Game Debrief

•Cost of Delay:

•- What were the Cost of Delay curves for the Fixed dates?

•- What about the other stories

Cost of Delay for Classes of Service

Game Debrief

•

•Visualization:

- Was the work visualized and status of work apparent?

Go Live Often

Game Debrief

•Flow of work / Pull:

•- Did you start considering about pull from the right?

•- Was there any swarming going on? When? Was it effective?

Game Debrief

- Was planning effective?

- Were the retrospectives useful, or were issues visible enough when they arose

Little’s law

Wq is the average time in the queue for a standard jobLq is the average number of things in the queue to be processedThe denominator (Lambda) is the average processing rate for jobs in the queue

http://scalingsoftwareagility.wordpress.com/2009/12/14

Little’s law for a sub system

http://scalingsoftwareagility.wordpress.com/2009/12/14

Backlog = 100 storiesIteration length = 2 weeksVelocity = 8 stories per sprint

= 12.5 iterations or

25 weeks to get into the sprint + 2 weeks to finsish = 27 weeks

Little’s law for a system

http://scalingsoftwareagility.wordpress.com/2009/12/14

Number of projects = 50

Velocity = 10 projects per year

50 projects / 10 projects per year

= 5 years per project (in average)

Process Control Chart

David J. Anderson – Kanban Traning Class material

• Visualize the work flow as is today

• Limit Work-in-Progress

• Measure and manage flow

Getting Started

References

- David J. Anderson – Kanban Traning Class material

- Aslak Hellsøy - http://open.bekk.no/2009/11/03/cumulative-flow-diagrams-with-google-spreadsheets

- http://scalingsoftwareagility.wordpress.com/2009/12/14

- Silver Stripe Blog – http//toolsforagile/blog/archives/647

Thank you!