The Kanban Method is a powerful way for Agile teams and organizations to visualize work, identify and eliminate bottlenecks, and achieve measurable operational improvements in throughput and quality.
This 1 or 2-day foundational workshop introduces the core concepts of Lean and just-in-time (JIT) production and prepares participants to apply Kanban to their work, including when to use Kanban alongside or instead of other Agile frameworks, like Scrum.
With hands-on group exercises and real-world case studies, participants will experience principles that underpin the Kanban method while gaining an appreciation for the key benefits and impact the Kanban Method will have on their teams and across their organizations.
From Kanban newbie to active practitioner, this workshop is role-agnostic and is geared towards anyone looking for a deeper understanding of Kanban and how to apply it to their teams, wherever their organization is on their journey, from enterprise to startup.
Kanban Workshop participants can claim seven PDUs and/or SEU’s for the 1 or 2-day class. Visit our FAQ page to learn how to claim PDUs and/or SEUs.
Kanban Training Learning Outcomes
Through a combination of immersive team-based learning, exercises, and real-world case studies, participants will be able to:
- Understand the “what” and “why” of Kanban
- Describe the Kanban Method (Principles and Practices)
- Apply core concepts of Lean (Flow, Waste, Cost of Delay, Work In Progress)
- Setup and configure a Kanban board for their team
- Utilize key Kanban metrics to manage flow and reduce time to market
- Focus on optimizing for the whole and limiting work in progress
- Increase visibility to increase collaboration and eliminate waste
Kanban vs. Scrum
Kanban and Scrum are frameworks that fall beneath the Agile umbrella. It is not a question of whether one is better or the other, it’s which framework is best for the environment. Both frameworks have their strengths and weaknesses, depending on the situation. Kanban allows teams to visualize the workflow to identify blocks, limit work in progress to establish focus, and measure lead time.
Here are some reasons why teams may decide to move to Kanban:
- No requirement to commit to customers or release schedules
- Work is “interrupt-driven”
- Ability to change priorities on the fly
Scrum allows teams to become more predictable by committing to work and swarming until it is completed.
Here are some reasons why teams might decide to move to Scrum:
- Craving more goals and focus
- More predictability
- Just starting out and need a more solid framework to create discipline
Best Environment for Kanban
The environments best suited for Kanban are those that support business teams because the framework is flexible and responsive enough to accommodate shifting priorities. Teams that are mature, disciplined, and self-organizing are also able to handle a less-disciplined framework.
Kanban vs. Scrum – How to choose is a more in-depth article with questions to help choose between the two frameworks.