<style> .reveal .slides { text-align: left; } h1, h2, h3, h4, h5, h6 { text-transform: none !important; } li, p{ font-size: 20px; } .blue{ color: #42affa; } .pink{ color: #e94989; } .green{ color: #3ebeb0; } .font18{ font-size: 18px; } .inline{ display: inline; } .tleft{ text-align: left; } .tright{ text-align: right; } .image{ border: 0px; box-shadow: none;} </style> ### The DevOps Handbook Ch6 #### Understanding the Work in Our <p class="blue inline">Value Stream</p>,</br> Making it <p class="pink inline">Visible</p>, </br>and <p class="green inline">Expanding</p> it Across the Organization <p style="text-align:right; font-size:24px;">- Presenter: Dotto</p> --- <img src="https://i.imgur.com/U1n1StG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: center; float: left; padding-left: 45%;"> </br></br></br> <blockquote style="width:90%; font-size: 38px; padding: 20px;"> The most efficient way to start improving any value stream is to <span class="pink">conduct a workshop with all major stakeholders</span> and <span class="pink">perform a value stream mapping exercise</span> -- a process designed to help capture all the steps required to create value. <p class="tright" style="display: grid;font-size: 30px;">-- Courtney Kissler and the team <a href="https://shop.nordstrom.com/" style="display: contents;">Nordstorm</a></p> </blockquote> --- ### <img src="https://i.imgur.com/U1n1StG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left;">Identifying The Teams</br> Supporting Our Value Stream ---- - Members(2/7): - <img src="https://i.imgur.com/7hjFG57.png" style="border: 0px; box-shadow: none; float: right;"> **Product owner**: the <span class="blue">internal voice of the business</span> that defines the next set of functionality in the service<!-- .element: class="fragment" data-fragment-index="1" --> </br> - <img src="https://i.imgur.com/f86Ih7T.png" style="border: 0px; box-shadow: none; float: right;"> **Development**: developing application functionality in the service<!-- .element: class="fragment" data-fragment-index="2" --> ---- - Members(4/7): - <img src="https://i.imgur.com/JJ85oYh.png" style="border: 0px; box-shadow: none; float: right; height: 100px"> **QA**: ensuring that <span class="blue">feedback loops exist</span> to ensure the service functions as desired<!-- .element: class="fragment" data-fragment-index="1" --> </br> - <img src="https://i.imgur.com/XiB3Yc0.png" style="border: 0px; box-shadow: none; float: right; height: 100px"> **Operations**: maintaining the production environment and helping ensure that required service levels are met<!-- .element: class="fragment" data-fragment-index="2" --> ---- - Members(6/7): - <img src="https://i.imgur.com/kcZDYRF.png" style="border: 0px; box-shadow: none; float: right; height: 100px;"> **Infosec**: securing systems and data<!-- .element: class="fragment" data-fragment-index="1" --> </br></br> - <img src="https://i.imgur.com/uh9L5RJ.png" style="border: 0px; box-shadow: none; float: right; height: 100px;"> **Release managers**: managing and coordinating the production deployment and release processes<!-- .element: class="fragment" data-fragment-index="2" --> ---- - Members(7/7): - <img src="https://i.imgur.com/iuYW1OD.png" style="border: 0px; box-shadow: none; float: right;height: 120px;"> **Technology executives or value stream manager**: in Lean literature, someone who is responsible for <blockquote style="width:90%; font-size: 38px; padding: 20px;"> “ensuring that the value stream meets or exceeds the customer [and organizational] requirements for the overall value stream, from start to finish” </blockquote> --- ### <img src="https://i.imgur.com/U1n1StG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left;">Create A Value Stream Map To See The Work ----  ---- #### Steps 1. List high-level process blocks (5~15 blocks) 2. Each process block should include: * lead time * process time * %C/A <blockquote style="width:90%; font-size: 20px; padding: 20px;"> %C/A = % of the time that downstream customer can perform task without "CAC" <li> Correct information or material</li> <li> Add missing information</li> <li> Clarify information provided</li> </blockquote> ---- #### Focus on <span style="font-size: 28px"> 1. <img src="https://i.imgur.com/uh9L5RJ.png" style="border: 0px; box-shadow: none; float: right; background-color:red; height:80px;"><span class="pink">low %C/A rates</span> on the request form submitted by department managers due to the absence of employee numbers <!-- .element: class="fragment" data-fragment-index="1" --></span> </br></br> <span style="font-size: 28px"> 2. <img src="https://i.imgur.com/f86Ih7T.png" style="border: 0px; box-shadow: none; float: right; background-color:red; height:80px"><span class="pink">long lead times or low %C/A rates</span> when delivering correctly configured test environments to Development teams <!-- .element: class="fragment" data-fragment-index="2" --></span> </br></br> <span style="font-size: 28px"> 3. <img src="https://i.imgur.com/JJ85oYh.png" style="border: 0px; box-shadow: none; float: right; background-color:red; height:80px"><span class="pink">long lead times</span> required to execute and pass regression testing <!-- .element: class="fragment" data-fragment-index="3" --></span> --- ### <img src="https://i.imgur.com/U1n1StG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left;">Creating A Dedicated Transformation Team ---- #### Challenges - The initiatives are inevitably in conflict with ongoing business operations ---- #### Goal - Achieving a <span class="pink">clearly defined</span>, <span class="green">measurable</span>, <span class="blue">system-level</span> result <blockquote style="width:90%; font-size: 28px; padding: 20px;"> e.g. reduce the deployment lead time from “code committed into version control to successfully running in production” by 50% </blockquote><!-- .element: class="fragment" data-fragment-index="1" --> ---- #### Build up a dedicated team <span style="font-size: 28px"> <ul> <li> Assign members to be solely allocated to the DevOps transformation efforts</li> </ul> </span> <span style="font-size: 28px"> <ul> <li> Select team members who are </li> <ul> <li>have skills across a wide variety of domains.</li> <li>have longstanding and mutually respectful relationships with the rest of the organization.</li> </ul> </ul> </span></br><!-- .element: class="fragment" data-fragment-index="1" --> ---- #### Build up a dedicated team <span style="font-size: 28px"> <li>Create a separate <span class="blue">physical space</span> for the dedicated team</li><!-- .element: class="fragment" data-fragment-index="1" --> <li>Maximize <span class="blue">communication flow</span> within the team</li><!-- .element: class="fragment" data-fragment-index="2" --> <li>Create some <span class="blue">isolation</span> from the rest of the organization</li><!-- .element: class="fragment" data-fragment-index="3" --> <li>Free the transformation team from many of the rules and policies that restrict the rest of the organization and create new processes.</li><!-- .element: class="fragment" data-fragment-index="4" --> </span> ---- #### Agree On A Shared Goal <img src="https://i.imgur.com/0zi7E0P.jpg" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 20%; width: 600px"> ---- #### Keep Our Improvement Planning Horizons Short <img src="https://i.imgur.com/h52016j.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 20%; width: 600px"> ---- #### Reserve 20% Of Cycles For Non-functional Requirements And Reducing Technical Debt ---- <img src="https://i.imgur.com/xgJF7tO.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 20%; width: 600px"> ---- <img src="https://i.imgur.com/GiXOURF.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 10%; width: 800px"> ---- <img src="https://i.imgur.com/VGYylEX.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 10%; width: 800px"> ---- #### Invest 20% of cycle on * refactoring * automation work and architecture * non-functional requirements * maintainability, manageability, scalability, reliability, testability, deployability, and security --- ### <img src="https://i.imgur.com/U1n1StG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left;">Case Study: </br> #### Operation InVersion at LinkedIn ---- <img src="https://i.imgur.com/SAHf3z5.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 25%; height: 600px"> ---- <img src="https://i.imgur.com/e66I668.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 10%; width: 1000px"> ---- <blockquote style="width:90%; font-size: 28px; padding: 20px;"> It's difficult to trobleshoot and recover LEO, and difficult to release new code.... </blockquote> <img src="https://i.imgur.com/odN7vas.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 20%; width: 500px"><!-- .element: class="fragment" data-fragment-index="1" --> ---- ##### Service based <img src="https://i.imgur.com/bfSR6SG.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 25%; height: 600px"> ---- ##### Rest.li <img src="https://i.imgur.com/QHeXfDV.png" style="border: 0px; padding-right: 20px; box-shadow: none; float: left; padding-left: 10%; width: 800px"> --- *Thanks for listening!* ---- ### reference link * [PDF ~ CH8](http://images.itrevolution.com/documents/DevOps_Handbook_Intro_Part1_Part2.pdf) * [Mindmap of reading note](https://docs.huihoo.com/devops/DevOps%E5%AE%9E%E8%B7%B5%E6%8C%87%E5%8D%97%E7%B2%BE%E8%A6%81-V3-%E5%BC%A0%E4%B9%90.pdf) * [[译]LinkedIn 的发展史](http://www.jfh.com/jfperiodical/article/1979?f=jfperiodical)