Ian Johnson

 10 years as a software developer  2 years working in a scrum team  6 months working with Kanban  Blog: 

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

 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

To DoDoingDone

To DoDoingDone Mow Lawn Clean Kitchen Clean Bathroom Talk on Kanban Release WCF Client Ruby Twitter Game Learn F#

In Progress High Level Design + Estimate Detailed Design + Estimates IdeaAnalysisApprovalDesignApprovalBuildTestDeployed

To DoDoing Done Parked

Blocked Feature Bug

 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

My details:  Blog:  Further Reading:  Mattais Skarin - “Kanban and Scrum – Making the most of both” : 