Introduction to Kanban

Ian Johnson

A bit about me…

10 years as a software developer 2 years working in a scrum team 6 months working with Kanban Blog: http://ninjaferret.co.uk/blog Twitter: @IJohnson_TNF

Agenda

Origins of Kanban Building a simple Kanban board Evolving a Kanban board at work Visualising data Questions

Origins of Kanban

Do not send defective products to the next process

Take only what you need for production

Produce only what is needed for the next process

Equalize production Use Kanban as a means of fine tuning Iteratively improve

Building a Kanban board

To Do

Doing

Done

Limit Work in Progress

To Do Doing DoneMow Lawn

Clean Kitchen

Clean BathroomTalk on Kanban

Release WCF Client

Ruby Twitter Game

Learn F#

Kanban at Work: Our Process

In Progress

High Level

Design +

Estimate

Detailed Design

+ Estimate

s

Idea Analysis

Approval Design Approv

al Build Test Deployed

Kanban at Work: Our Board

To Do Doing Done

Parked

Visualisation Data

Blo

cked

Feature Bug

Summary

Limiting WIP can lead to improved performance

Visualising your process can help identify bottlenecks

Keep it simple Add complexity only when you need it

Your board belongs to your team Experiment/Continuously improve

There is no “one size fits all” solution Have fun

Questions?

My details: Blog: http://ninjaferret.co.uk/blog Twitter: @IJohnson_TNF

Further Reading: Mattais Skarin - “Kanban and Scrum

– Making the most of both” : http://bit.ly/a7q3GV

http://www.limitedwipsociety.org/