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.
EvanLeybourn
STARTINGWITHVSM & KANBAN
Apracticalworkshoponvaluestreammapping&WIP
Evan Leybourn
lean / agile business leader and author
Singapore
@eleybourn
http://theagiledirector.com
CLICK TO DISCOVER M...
1. eliminate waste
2. amplify learning
3. decide as late as possible
4. deliver as fast as possible
5. empower the team
6....
valuestreammapping
defines the ‘as-is’steps & roles for each
task
valueadd(va)
time spent on outcomes for the
customer
non-valueadd(nva)
time spent between steps
identify, isolate and define the process
measure the average va and nva
calculate your process efficiency
= (va / va + nva)
what is kanban (かんばん)
workflow monitoring & visualisation
1. visualise (card wall)
2. limit wip
3. manage flow
4. make policies explicit
5. feedback loops
6. improve collaboratively
kanbanifyyourvsm
- merge 0’s
- define board policies
- calculate wip
min throughput is usually= team size
ifyourefficiencywas100%,howmany“x”couldyoudosimultaneously?
whatisyourtotalwip
total wip =
min throughput / efficiency
e.g. 7/55% ~= 13
Assuming a
software team a 7
(not pairing)
calculate%effortperstate
% effort =
state va / total va
e.g. 4 / 14.5 ~= 28%
proportionwipbystate
wip =
total wip * % effort
e.g. 13 * 28% ~= 4
proportionwipbystate
design wip = 2
develop wip = 7
test wip = 4
deploy wip = 0 = 1
inspect & adapt
kaizen(改善)
what went well?
retrospective/qualitycircle
addactionabletaskstothebacklog
what could be improved?
kaizenemphasises
teamwork, discipline & morale
1. do not send defective products to the subsequent process
2. the subsequent process comes to withdraw only what is
neede...
http://agilebusinessmanagement.o
rg
- Case Studies
- Articles
- Community
Join our Agile Journey
To learn more, check out
Directing the Agile Organisation
by Evan Leybourn
available at Amazon and all good book stores
CL...
Starting with vsm and kanban; A practical workshop on value stream mapping & WIP
Starting with vsm and kanban; A practical workshop on value stream mapping & WIP
Upcoming SlideShare
Loading in …5
×

Starting with vsm and kanban; A practical workshop on value stream mapping & WIP

2,246 views

Published on

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
* Recruitment
* 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.

Published in: Software
  • Be the first to comment

Starting with vsm and kanban; A practical workshop on value stream mapping & WIP

  1. 1. EvanLeybourn STARTINGWITHVSM & KANBAN Apracticalworkshoponvaluestreammapping&WIP
  2. 2. Evan Leybourn lean / agile business leader and author Singapore @eleybourn http://theagiledirector.com CLICK TO DISCOVER MORE
  3. 3. 1. eliminate waste 2. amplify learning 3. decide as late as possible 4. deliver as fast as possible 5. empower the team 6. build integrityin 7. see the whole
  4. 4. valuestreammapping defines the ‘as-is’steps & roles for each task
  5. 5. valueadd(va) time spent on outcomes for the customer
  6. 6. non-valueadd(nva) time spent between steps
  7. 7. identify, isolate and define the process
  8. 8. measure the average va and nva
  9. 9. calculate your process efficiency = (va / va + nva)
  10. 10. what is kanban (かんばん) workflow monitoring & visualisation
  11. 11. 1. visualise (card wall) 2. limit wip 3. manage flow 4. make policies explicit 5. feedback loops 6. improve collaboratively
  12. 12. kanbanifyyourvsm - merge 0’s - define board policies - calculate wip
  13. 13. min throughput is usually= team size ifyourefficiencywas100%,howmany“x”couldyoudosimultaneously?
  14. 14. whatisyourtotalwip total wip = min throughput / efficiency e.g. 7/55% ~= 13 Assuming a software team a 7 (not pairing)
  15. 15. calculate%effortperstate % effort = state va / total va e.g. 4 / 14.5 ~= 28%
  16. 16. proportionwipbystate wip = total wip * % effort e.g. 13 * 28% ~= 4
  17. 17. proportionwipbystate design wip = 2 develop wip = 7 test wip = 4 deploy wip = 0 = 1
  18. 18. inspect & adapt kaizen(改善)
  19. 19. what went well? retrospective/qualitycircle
  20. 20. addactionabletaskstothebacklog what could be improved?
  21. 21. kaizenemphasises teamwork, discipline & morale
  22. 22. 1. do not send defective products to the subsequent process 2. the subsequent process comes to withdraw only what is needed 3. produce only the exact quantity withdrawn by the subsequent process 4. equalise, or level, the production 5. kanban is a means to fine tuning 6. stabilize and rationalize the process
  23. 23. http://agilebusinessmanagement.o rg - Case Studies - Articles - Community Join our Agile Journey
  24. 24. To learn more, check out Directing the Agile Organisation by Evan Leybourn available at Amazon and all good book stores CLICK TO DISCOVER MORE

×