Notes from the AONW 2016 conference.
Here is a transcription of my awful handwriting.https://docs.google.com/document/d/1D8WecIKYNBpX9FGK7X9IdIJdtoq6taILYcvZd5o57rc/edit?usp=sharingWhat goes into the value stream? Things that deliver value Not the ENTIRE process Get more granular when there isn’t any other plan to improve Capture interactions/hand-offs between teams/groups/departmentsWhere should I focus? How do I find the bottlenecks?Queueing: How big are the queues? How long does it take to get a work item through the queue?Kaizen newspaper: What are we going to do?Value Stream Map augments process flow with touch time and cycle timeLet’s you visualize your stream to establish a shared truthKaizen: The process we wish we hadHow do you create a VSM?Whole team collaborates to identify boxesMake sure that the story (card) in the system represents user valueThis will help Engineers see the whole systemDo we have too much WIP? Not enough slack?What happens when the bottleneck is a people problem?Business process vs. Engineering OrganizationAlign the work of all people who contribute to the value streamHow do you track/compute the touch/cycle times?Inherent in Kanban systemAsk people who are doing it or have done it beforeSometimes it might be a (wide) range of valuesAssess the impact of your experiments on these timeVSM may or may not correspond to lanes on a Kanban boardKanban in software visualizes inventoryLook at WIP and variance to identify processes to improveVALUE stream vs. PROCESS flowValue stream looks at time, money, and resourcesProcess flow focuses on questions like “How?” and “Where doe the time go?”Setup and teardown timeHow do you visualize/track defects?Do a separate VSM for defects? Separate process flow?May have “emergency services”, “all hands on deck”, or “stop the presses” workflow with separate Kanban statesYou’ll need to identify root causes to find wasteBooks and other references“The Lean Paradox” (a.k.a. “This is Lean: Resolving the Efficiency Paradox” by Niklas Modig and Pär Åhlström“User Story Mapping” by Jeff Patton and Peter Economy“Product Development Flow” by Donald G ReinertsenA dense textbook with good diagramsSeems to have inspired SAFe“The Goal” by Eliyahu M. Goldratt“The Phoenix Project” by Gene Kim, Kevin Behr, and George Spafford Also, it might be worthwhile to look at various software products that help you do a VSM