1. Ian Johnson

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

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

4.  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

5. To DoDoingDone

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

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

8. To DoDoing Done Parked

9. Blocked Feature Bug

10.  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

11. My details:  Blog: http://ninjaferret.co.uk/bloghttp://ninjaferret.co.uk/blog  Twitter: @IJohnson_TNF Further Reading:  Mattais Skarin - “Kanban and Scrum – Making the most of both” : http://bit.ly/a7q3GV http://bit.ly/a7q3GV  http://www.limitedwipsociety.org/ http://www.limitedwipsociety.org/