So you’ve heard about this Kanban thing and want to know where to start, or maybe you’ve been using it for a while and you want to know where to go. In this hands-on workshop, we'll start at the very beginning and teach you how to build a Value Stream Map and use that to define your initial Kanban and WIP limits.
If these terms don’t make sense to you, then you need to come to this workshop.
Want to learn more;
* Learn how to create your VSM; the commonly overlooked practice of modeling the functional steps in your business processes - anything from IT to finance
* Learn how VSM and Kanban can support other Agile practices (such as Scrum or XP) and core values
* Track the flow of work through your VSM on your Kanban wall
* Learn how to use your VSM, team size and process efficiency to calculate your initial WIP.
* Learn how to embed a culture of Kaizen
=== CONTEXT ===
This is intended to be a practical workshop on Kanban. If possible the room should be set up in rounds of no more than 10 people, but I can work this in a lecture theater in a pinch. The workshop will be split into 4 primary topics.
=== 1. INTRODUCTION TO VSM AND KANBAN ===
This will be a introduction to the topic. A little history and how it made the jump from manufacturing to agile software development. I will show what a VSM looks like and demonstrate how teams can create them. I'll also demonstrate how to calculate the value added (VA) time, non-value added (NVA) time and efficiency.
=== 2. BUILD A VSM ===
Each table will model a the VSM of a given business process using large sheets of paper. The topic to model will be at the tables discretion. Some tables will create VSMs of their organisational processes. Where tables do not have or want to model their own, I will provide a number of common scenario's for them to model. These include;
* Defect management
* IT Portfolio management
* Iteration (sprint) management
=== 3. TURN THE VSM INTO A KANBAN BOARD WITH APPROPRIATE WIP LIMITS ===
Following that, each table will then turn their VSM into a Kanban board and, using simple mathematics, calculate the initial WIP limits. This will be based on;
* Calculating the process efficiency (based on the VA and NVA time)
* Calculate your total WIP based on your team size (and agile practices such as pair programming)
* Estimate your multitask capacity from your process efficiency
* Proportion your WIP based on the above
=== 4. KAIZEN ===
Everything above is just the beginning. You are modelling the "now" state. We'll look at how to use metrics (cycle time, lead time, statistical run charts, cumulative flow, etc) and agile retrospectives to embed a culture of continuous improvement to your processes through continuous refinement of VSM states, Kanban and WIP limits.