The document discusses Kanban, a Lean methodology based on visualizing workflows. It describes Kanban concepts like limiting work-in-progress and measuring lead times. The document then outlines several experiments using a Kanban game with roles like squares maker and triangles maker. Finally, it provides overviews of key Kanban techniques including cumulative flow diagrams and visualizing workflows.

1. Kanban Workshop

2. Kanban
Kanban is Japanese for ‘visual signal’ or ‘card’. Is about improving communication
through visual management
Based on Lean Thinking (Toyota Production System)
Lean is about maximizing the value deliver to the client while reducing waste.
We get as a result:
Reduce Costs
Improve Efficiency
Improve Productivity

3. Kanban Game
Task:
Roles: Squares Maker, Triangles Maker, QA
Step 1: Step 2:

4. Kanban Game: Experiment I
Roles: Squares Maker, Triangles Maker, QA
Experiment: Complete batches of size 10, before passing to next step

5. Kanban Game: Experiment II
Roles: Squares Maker, Triangles Maker, QA
Experiment: No batches, deliver as soon as possible (push system)

6. Kanban Game: Experiment III
Roles: Squares Maker, Triangles Maker, QA
Experiment: Stop push system, use pull system

7. Kanban Game: Experiment IV
Roles: Squares Maker, Triangles Maker, QA
Experiment: Reflect and see what you can improve. Use same rules.

8. Kanban Game: Experiment V
Roles: Your Choice
Experiment: Reflect and see what you can improve. No rules.

9. Kanban in a nutshell
1. Vizuale the workflow
2. Limit WIP (work in progress)
3. Measure the lead time (average time to complete one item, sometimes called
“cycle time”)

10. Cumulative Flow Diagram

11. One day in Kanban Land (1/11)

12. One day in Kanban Land (2/11)

13. One day in Kanban Land (3/11)

14. One day in Kanban Land (4/11)

15. One day in Kanban Land (5/11)

16. One day in Kanban Land (6/11)

17. One day in Kanban Land (7/11)

18. One day in Kanban Land (8/11)

19. One day in Kanban Land (9/11)

20. One day in Kanban Land (10/11)

21. One day in Kanban Land (11/11)

22. Don’t Stay in the Shu Box!

23. Scrum Essence is at Ri Level
Deliver (or Demo) Every Sprint
Self-organized cross-functional teams
Inspect and Adapt
Chief Impediment Remover (aka Scrum Master, optional)
Product Owner

24. Agile Methods are just tools

25. AGILE IS NOT A RECIPE

26. Thanks!
Diego Alonso Gil Aguilar, @diegogil1989
Software Engineer at Avantica Technologies
CSM, CSD and survivor of Alistair Cockburn’s
Agile Advanced Class
Join your local agile community:
Agile Perú: http://bit.ly/agileperu
Agile Costa Rica: http://bit.ly/agilecostarica

27. For Further Reference
Kanban and Scrum: Making the Most of Both - Henrik Kniberg and Mattias
Skarin https://www.infoq.com/minibooks/kanban-scrum-minibook
Lean from the Trenches: Managing Large-Scale Projects with Kanban - Henrik
Kniberg https://www.crisp.se/file-uploads/Lean-from-the-trenches.pdf