tag:blogger.com,1999:blog-5470633149042251450.post8924029563622358262..comments2016-02-07T21:00:17.640-08:00Comments on AONW 2016: Value stream mapping for software projectsTroy Freverhttp://www.blogger.com/profile/16147170060861836615noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5470633149042251450.post-3646983579213433702016-02-04T19:09:53.239-08:002016-02-04T19:09:53.239-08:00Here is a transcription of my awful handwriting.
...Here is a transcription of my awful handwriting.<br /><br />https://docs.google.com/document/d/1D8WecIKYNBpX9FGK7X9IdIJdtoq6taILYcvZd5o57rc/edit?usp=sharing<br /><br />What goes into the value stream?<br /> Things that deliver value<br /> Not the ENTIRE process<br /> Get more granular when there isn’t any other plan to improve<br /> Capture interactions/hand-offs between teams/groups/departments<br /><br />Where should I focus? How do I find the bottlenecks?<br />Queueing: How big are the queues? How long does it take to get a work item through the queue?<br />Kaizen newspaper: What are we going to do?<br /><br />Value Stream Map augments process flow with touch time and cycle time<br />Let’s you visualize your stream to establish a shared truth<br />Kaizen: The process we wish we had<br /><br />How do you create a VSM?<br />Whole team collaborates to identify boxes<br />Make sure that the story (card) in the system represents user value<br />This will help Engineers see the whole system<br /><br />Do we have too much WIP? Not enough slack?<br /><br />What happens when the bottleneck is a people problem?<br />Business process vs. Engineering Organization<br />Align the work of all people who contribute to the value stream<br /><br />How do you track/compute the touch/cycle times?<br />Inherent in Kanban system<br />Ask people who are doing it or have done it before<br />Sometimes it might be a (wide) range of values<br />Assess the impact of your experiments on these time<br /><br />VSM may or may not correspond to lanes on a Kanban board<br />Kanban in software visualizes inventory<br />Look at WIP and variance to identify processes to improve<br /><br />VALUE stream vs. PROCESS flow<br />Value stream looks at time, money, and resources<br />Process flow focuses on questions like “How?” and “Where doe the time go?”<br /><br />Setup and teardown time<br /><br />How do you visualize/track defects?<br />Do a separate VSM for defects? Separate process flow?<br />May have “emergency services”, “all hands on deck”, or “stop the presses” workflow with separate Kanban states<br />You’ll need to identify root causes to find waste<br /><br />Books and other references<br />“The Lean Paradox” (a.k.a. “This is Lean: Resolving the Efficiency Paradox” by Niklas Modig and Pär Åhlström<br />“User Story Mapping” by Jeff Patton and Peter Economy<br />“Product Development Flow” by Donald G Reinertsen<br />A dense textbook with good diagrams<br />Seems to have inspired SAFe<br />“The Goal” by Eliyahu M. Goldratt<br />“The Phoenix Project” by Gene Kim, Kevin Behr, and George Spafford <br />Also, it might be worthwhile to look at various software products that help you do a VSM<br />Davidhttps://www.blogger.com/profile/14339690785383077372noreply@blogger.com