The DevOps Void & Value Stream Mapping
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
In the above multiprocess diagram, we can see the Data team takes:<br />
• 180 minutes of operations (real value),<br />
• 5 days of waiting (wastage),<br />
• Or 2.5% Efficiency (<strong>Value</strong> Operation / [<strong>Value</strong> Operation + Wastage]).<br />
Not exactly something you want to write home about. However, not an “untypical”<br />
inefficiency, and a serious opportunity for improvement.<br />
Imagine if for each team could move from 2.5% to just 25%. <strong>The</strong> benefits would be<br />
enormous, and over the lifetime of a project we could be saving weeks, maybe<br />
months, of time which translates to early “time to market” and significant IT project<br />
cost savings.<br />
Enter <strong>Value</strong> <strong>Stream</strong> <strong>Mapping</strong><br />
Originally employed in the car manufacturing space, <strong>Value</strong> <strong>Stream</strong> <strong>Mapping</strong> (VSM)<br />
is a lean method that helps you better define a sequence of activities, identify<br />
wastage & ultimately improve your endtoend processes. A set of methods that can<br />
be applied to any type of operation, including of course IT Environments & <strong>DevOps</strong>.
Change language