1 / 11

Introduction to Kanban

Ian Johnson. Introduction to Kanban. 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

lita
Download Presentation

Introduction to Kanban

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ian Johnson Introduction to Kanban

  2. 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

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

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

  5. Building a Kanban board

  6. Limit Work in Progress Mow Lawn Clean Kitchen Talk on Kanban Clean Bathroom Release WCF Client Ruby Twitter Game Learn F#

  7. Kanban at Work: Our Process InProgress High Level Design + Estimate Detailed Design + Estimates

  8. Kanban at Work: Our Board To Do Doing Done Parked

  9. Visualisation Data Feature Bug Blocked

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

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

More Related