Introduction to Kanban for Creative Agencies
159 likes50,068 views
Will Evans discusses the importance of Kanban in managing workflow and improving productivity within teams. He emphasizes five key principles of Kanban, including visualizing workflow and limiting work-in-progress to reduce stress and enhance focus. The document concludes with practical suggestions for implementing the Kanban system in organizational practices.
Introduction to Kanban for Creative Agencies
- 1. v
- 2. v Who are we? WILL EVANS Director of UX Design The Library Corporation @semanticwill Who I Am
- 3. v Let’s start with an exercise!
- 5. v You have 5 minutes • Write down everything that you are working on (or need to be working on) on a post-it • ALL CAPS • One item per post-it
- 6. v Draw Personal Kanban TO DO DOING DONE
- 7. v
- 8. v
- 9. v
- 10. v What is a Kanban? “A Card (or traditionally, a Kanban), is a symbolic token representing a unit of effort, either to be completed or in the process of being completed.” - Jabe Bloom
- 11. v A Pull System TODO DOING DONE Boundary Jabe Bloom, “The Moment of Pull” Future PastPresent
- 12. v Why Lord? Why?
- 13. v How can Kanban help? • Where are we now? • Who is working on what? • What should I be doing? • What should I not be doing? Is it hard for every person in your organization to answer these questions:
- 14. v 5 Basic Principles • Visualize your workflow • Limit your work-in-progress (WIP) • Make policies explicit • Measure your flow • Model process improvement
- 18. v Why Limit Your WIP? WIP (work-in-progress) is the proverbial “balls in the air you are juggling.” The more balls in the air, the harder it is to concentrate; attention to detail suffers; quality goes down; shit goes undone; you feel bad; work becomes overwhelming and unpleasant.
- 19. v David Anderson, “WIP Limits are for Adults, Too!”
- 22. v More Value & Throughput
- 23. v Minimize TOTAL Cycle Time
- 24. v Minimize TOTAL Cycle Time
- 25. v 10 Reasons to Limit Your WIP Jim Benson “Why Limit Your WIP: A PK Flow Series”
- 26. v Simple Kanban TO DO DOING (3) DONE Options Constraint Chris Matts & Olav Maassen, “Real Options Underlie Agile Practices”
- 27. v WIP Limits TO DO DOING (3) DONE Forces conversation
- 28. v Measure & Manage Flow Lead Time Cycle Time
- 29. v Small Batches & Cycles Reduce Risk
- 30. v Backlog To Do Doing (3) Testing (3) Done WIP Limit Explicit Policy Make Policies Explicit
- 31. v Model Process Improvement Value Stream Mapping: A graphical representation of the flow of work involved in turning an idea into a product consumed by a customer Request Approve Requirements Signoff Research Design Build Test Deploy Delay Customer Delay
- 32. v Incremental Improvement • Review bottlenecks • Pair to increase flow • Adjust WIP Limits • Suggest improvements • Measure Lead Time & Cycle Time • Perform experiments • Track results with metrics
- 34. v
- 35. v
- 36. v
- 37. v Challenges & Observations Walk the Gemba > Walking up the inference ladder Make the board work for you & your team • Start with your existing process • There is no “One True Board!” Keeping the value stream filled Pull is a mindset! Beware of “Infinite WIP” Recognize the true cost of context switching
- 38. v Further Reading Start here Then Advanced