Starting with value stream mapping and kanban - training slides (cc-by-sa)

Evan Leybourn

STARTING WITH VSM & KANBANA practical workshop on value stream mapping & WIP

Starting with Value Stream Mapping and Kanban by Evan Leybourn is licensed under a Creative Commons Attribution-ShareAlike 3.0 Australia License <http://creativecommons.org/licenses/by-sa/3.0/au/>

Evan Leybournlean / agile business leader and authorSingapore@eleybournhttp://theagiledirector.com

CLICK TO DISCOVER MORE

To what degree is the outcome knowable in advance?

To what degree can you coordinate and control all the players?

To what degree is the outcome dependent on intangible elements?

wate

rfall

ag

ile

Waterfall (Incrementing)

Agile (Iterating)Images with thanks from Jeff Patton: http://www.agileproductdesign.com/

individuals and interactionsover processes and tools

working software over comprehensive documentation

customer collaboration over contract negotiation

responding to change over following a plan

1. eliminate waste2. amplify learning3. decide as late as possible4. deliver as fast as possible5. empower the team6. build integrity in7. see the whole

mura: unevennessmuri: overburdenmuda: wasteunderstanding waste

the 7 wastes

transportinventorymotionwaitingoverproductionover processingdefects

agile business intelligence

part 2: flow

Backlog Build Test Done

Backlog

Analysis

Build Test Stage Doc’Releas

eDone

value stream mapping

defines the ‘as-is’ steps & roles for each task

value add (va)

time spent on outcomes for the customer

non-value add (nva)

time spent between steps

1. gather preliminary information2. product quantity routing analysis3. group customers and materials4. sort product families by sequence5. choose one value stream to start

6. create an operations flow chart7. walk the shop floor8. collect the data9. construct the vsm10. summarize the data to get the big picture

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 wip3. manage flow4. make policies explicit5. feedback loops6. improve collaboratively

kanbanify your vsm

- merge 0’s- define board policies- calculate wip

work in progress

limit concurrent work and promote workflow

min throughput is usually = team sizeif your efficiency was 100%, how many “x” could you do simultaneously?

what is your total wip

total wip = min throughput / efficiencye.g. 7/55% ~= 13

Assuming a software team a 7 (not

pairing)

calculate % effort per state

% effort = state va / total va e.g. 4 / 14.5 ~= 28%

proportion wip by state

wip = total wip * % efforte.g. 13 * 28% ~= 4

proportion wip by state

design wip = 2develop wip = 7test wip = 4deploy wip = 0 = 1

“pull” all ready tasks to wip limitpull

class of service

expeditefixed deliveryintangible class

tasks with upstream dependenciesblocked

identify & resolve bottlenecks

through low wip limits and strict process flow

production levelling

constant rate of flow through all states

cycle time

average time to complete a task from start

lead time

average time to complete a task from request

progress monitoring

cumulative flow diagramstatistical run chartburndown/up chart

plot delivered functionality against durationeffort visualisation

cumulative flow diagram

bottleneck

poor flow

large wip

long lead time

plateau

plot cycle time against averageduration visualisation

cycle time run charts

process trend

process shift

extreme process variation

effort visualisation

plot delivered functionality against velocity

velocity

how much work can be delivered per iteration

burnup chart

burndown chart

discovery

scope creep

plateau

too many features

tracking epics

inspect and adapt

kaizen ( 改善 )

what went well?retrospective / quality circle

add actionable tasks to the backlog

what could be improved?

kaizen emphasises

teamwork, discipline & morale

1. do not send defective products to the subsequent process2. the subsequent process comes to withdraw only what is needed3. produce only the exact quantity withdrawn by the subsequent process4. equalise, or level, the production5. kanban is a means to fine tuning6. stabilize and rationalize the process

http://agilebusinessmanagement.org

- Case Studies- Articles- Community

Join our Agile Journey

To learn more, check out

Directing the Agile Organisationby Evan Leybourn

available at Amazon and all good book stores

CLICK TO DISCOVER MORE