Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.

Published in: Technology


  1. 1. An Introduction to Kanban<br />Stephen Forte<br />Chief Strategy Officer, Telerik<br />@worksonmypc<br />
  2. 2. Bio<br />Chief Strategy Officer of Telerik<br />Certified Scrum Master<br />Active in the Community:<br />International Conference Speaker for 12+ Years<br />RD, MVP and INETA Speaker <br />Co-moderator & founder of NYC .NET Developers Group<br />Wrote a few books: SQL Server 2008 Developers Guide (MS Press)<br />MBA from the City University of New York<br />Past:<br />CTO and co-Founder of Corzen, Inc. (TXV: WAN)<br />CTO of Zagat Survey <br />
  3. 3. Agenda<br />Defining Agile and Kanban<br />Using Kanban to manage projects<br />How to implement Kanban<br />
  4. 4. Agenda<br />Defining Agile and Kanban<br />Using Kanban to manage projects<br />How to implement Kanban<br />
  5. 5. Process and tools<br />Individuals and interactions<br />Following a plan<br />Responding to change<br />Comprehensive documentation<br />Working software<br />Contract negotiation<br />Customer collaboration<br />over<br />over<br />over<br />over<br />The Agile Manifesto–a statement of values<br />Source:<br />
  6. 6. Back to the Basics<br />“Agile” is about “values” not “rules” and rigid adherence to a process<br />Agile is about embracing change<br />
  7. 7. Influential Agile Methodologies<br />XP (The Past)<br />Scrum (The Present) <br />Kanban (The Future)<br />
  8. 8. What is Kanban?<br />An agile methodology that stresses pulling individual work items to completion <br />Focuses on visualization <br />Focuses on just in time delivery of raw materials<br />Workers get what they need when they need it, no sooner (Lean)<br />Limit Work in Progress<br />
  9. 9. Where did Kanban Come From?<br />Comes from the famous Toyota Production System<br />Part of the Lean Manufacturing Movement<br />Part of Six Sigma<br />Japanese for “signal card”<br />Kaizen-promotes continuous improvement <br />
  10. 10. Kanban Cards<br />
  11. 11. Flow<br />Kanban is about flow<br />Pull system- work is pulled through the system by demand<br />Batch v flow (individual work items)<br />Where there is inventory, there is no flow<br />Flow and pull are linked:<br />Keep the entire value stream moving towards the customer at the rate the customer consumes<br />
  12. 12. Agenda<br />Defining Agile and Kanban<br />Using Kanban to manage projects<br />How to implement Kanban<br />
  13. 13. Kanban for Technology Projects<br />Define a work flow and visualize it<br />Organize a queue<br />Limit work in progress (WIP) for each queue<br />Allows you to constantly evaluate process improvements<br />Allow work to flow through the system in a controlled way (not iterative) <br />No sprints!<br />Evolutionary by design<br />Change is built into the model<br />Communication is about flow<br />
  14. 14. Core Practices of Kanban<br />Define and visualize the workflow<br />Limit Work-in-progress<br />Measure and Manage Flow<br />Make Process Policies Explicit<br />Use Models to Suggest Improvement<br />For more info:<br />
  15. 15. Kanban<br />
  16. 16. Demo<br />Kanban Board<br />
  17. 17. Agenda<br />DefiningAgile and Kanban<br />Using Kanban to manage projects<br />How to implement Kanban<br />
  18. 18. Building a Kanban Process<br />
  19. 19. Building a Kanban Process #1<br />Define a process flow <br />Identify queues (swimlanes)<br />Visualize it on a board<br />
  20. 20. Building a Kanban Process #2<br />Set your first work in progress limits<br />First time you *may* have to guess<br />
  21. 21. Building a Kanban Process #3<br />Break down each work item to about the same size<br />Or you can use separate swim lanes: small, medium, and large <br />Put items in the queue<br />Pull the first items through the system <br />Establish your cycle time<br />Define how long it takes to pull an item through the system<br />Will determine your new work in progress limits<br />Evaluate if the WIP limits are correct and readjust<br />Evaluate if the Queues are appropriate <br />
  22. 22. Building a Kanban Process #4<br />Establish a delivery cadence<br />Establish regular meetings/reviews<br />Borrow from Scrum/XP <br />
  23. 23. Building a Kanban Process #5: Kaizen<br />Constantly improve your process<br />Daily meeting facing the board to evaluate your flow<br />Continue to tweak the WIP limits and queue<br />Formalize the improvement process<br />Have regular formal change meetings<br />Remember “be agile”<br />
  24. 24. Kanban has few rules<br />No daily scrum<br />No prescription for engineering practices <br />No iterations <br />No estimation<br />Uses metrics<br />
  25. 25. Be careful!<br />The lack of rules can lead to a lack of discipline <br />But the lack of rules allows you to mix and match<br />
  26. 26. References<br />Anderson, Kanban in Action:<br />Hiranabe, Kanban Applied to Software Development: from Agile to Lean:<br />
  27. 27. Questions? <br />