Why is DevOps vital for my company’s business
•Transferir como PPTX, PDF•
1 gostou•221 visualizações
The document discusses why DevOps is vital for companies in the modern business landscape. It notes that software is now central to many businesses and products, like cars which contain over 150 million lines of code. DevOps applies lean principles to streamline the process of delivering software by reducing waste and improving feedback loops between development and operations teams. Implementing DevOps through systems thinking, amplifying feedback, and continuous experimentation can lead to benefits like less risk, faster feedback, and increased value delivery and organizational efficiency.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (13)
Semelhante a Why is DevOps vital for my company’s business
Semelhante a Why is DevOps vital for my company’s business (20)
Mais de Giulio Vian
Mais de Giulio Vian (20)
Último
Último (20)
Why is DevOps vital for my company’s business
- 1. Why is DevOps vital for my company’s business? Giulio Vian — DevOps Lead
- 2. Agenda Modern world landscape DevOps in current landscape Putting it into practice
- 4. “Software Is Eating The World” — Marc Andreessen
- 5. Remember?
- 6. Replaced by portable computers
- 7. “Why Every Business is a Software Business” – Watts S. Humphrey Three management principles from 2002
- 8. Modern Cars Software in a modern 2016 car is 150 million lines of code 10% of costs for a D-segment, or large, car It grows at a compound annual rate of 11 percent Software enables critical automotive innovations
- 9. “Why Every Business is a Software Business” – Watts S. Humphrey Management Principles: 1. Recognize That You Are in the Software Business
- 10. “Why Every Business is a Software Business” – Watts S. Humphrey Management Principles: 1. Recognize That You Are in the Software Business 2. Quality Must Be the Top Priority
- 11. “Why Every Business is a Software Business” – Watts S. Humphrey Management Principles: 1. Recognize That You Are in the Software Business 2. Quality Must Be the Top Priority 3. Quality Software Is Developed by Disciplined and Motivated People
- 12. Teamwork and Care Illustration © Salvi Harps 2018
- 13. What is DevOps?
- 14. IT roles
- 15. DevOps is about… Dev Ops IT
- 16. … removing walls Dev Ops IT Business Customers
- 17. Definition DevOps is the result of applying Lean principles to the technology value stream.
- 18. Lean definition & principles Lean manufacturing is a systematic method originating in the Japanese manufacturing industry (Toyota) for the minimization of waste 5 principles are: Identify Value from customer perspective Map the Value Stream how each step of the process contributes Create Flow by reducing waste Establish Pull so that customer kick off the chain Seek Perfection by reviewing again and again your process
- 19. software delivered every 90 seconds…
- 20. every 15÷30 minutes, maybe “we release hundreds of times per week” Patrick Kua, N26 CTO (Feb 2018)
- 21. Research confirms Elite Performers according to Google’s “State of DevOps” Report
- 22. Lean in practice Approach Small batches Release often Fail-fast People empowerment Benefits Less risk Faster feedback Less waste (i.e. costs)
- 23. Small batches & Release often
- 24. Failure is the new norm
- 25. Putting it into practice
- 26. The Three Ways
- 27. Learning
- 28. First Way: Systems Thinking
- 29. First Way: Systems Thinking
- 30. First Way: Systems Thinking
- 31. Second Way: Amplify Feedback Loops
- 32. Third Way: Culture of Continual Experimentation and Learning
- 34. Is DevOps a product? 34
- 35. Do I need the Cloud?
- 36. DevOps applies to Mainframes as well
- 38. Is DevOps is a job role? 38
- 39. Can Dev and Ops be different orgs?
- 40. What’s the ROI ? Westpac Bank (New Zealand) Measured overall organisation efficiency For every $1 spent on a problem, Westpac was delivering a return of about 20-22 cents After DevOps transformation, that number is just shy of 40 cents 2x increase in the value delivery
- 41. An ingredient for growth? “In August 2017, we had 450,000 customers. We now have more than 2.3 million customers” Patrick Kua, N26 CTO (March 2019)
- 42. Bibliography & References (1/3) “Software Is Eating The World” — Marc Andreessen WSJ August 20, 2011 https://www.wsj.com/articles/SB10001424053111903480904576512250915629460 Why Every Business Is a Software Business” — Watts S. Humphrey Informit, Feb 22, 2002 http://www.informit.com/articles/article.aspx?p=25491 “This Car Runs on Code” — Robert N. Charette Feb 2009 https://spectrum.ieee.org/transportation/systems/this-car-runs-on-code https://www.visualcapitalist.com/millions-lines-of-code/ https://www.mckinsey.com/industries/automotive-and-assembly/our-insights/rethinking-car- software-and-electronics-architecture https://commons.wikimedia.org/wiki/History_of_accountancy https://queue.acm.org/detail.cfm?id=2945077 https://community.risingstack.com/how-n26-built-a-modern-banking-software-with-javascript- microservices/
- 43. Bibliography & References (2/3) State of DevOps 2019 https://cloud.google.com/blog/products/devops-sre/the-2019-accelerate-state-of-devops- elite-performance-productivity-and-scaling The NIST Definition of Cloud Computing https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf “The real ROI of DevOps” — Justin Arbuckle, February 3, 2017 https://jaxenter.com/real-roi-devops-131520.html ”Case Study: Compuware DevOps Transformation” — David Rizzo, May 7, 2018 https://itrevolution.com/case-study-compuware-rizzo/ https://www.visualcapitalist.com/wp-content/uploads/2019/05/the-future-of-talent-in- banking.html
- 44. Bibliography & References (3/3) The DevOps Handbook — G.Kim, P.Debois, J.Willis, J.Humble (IT Revolution 2016) Accelerate — Nicole Forsgren, Jez Humble (Trade Select 2018) Project to Product — Mik Kersten (IT Revolution 2019) The Mythical Man-Month — Frederick P. Brooks Jr. (Addison Wesley 1995, 2nd ed.) Site Reliability Engineering — B.Beyer , C.Jones, J.Petoff, N.R.Murphy (O′Reilly 2016) Making Work Visible — Dominica Degrandis (IT Revolution 2017)
- 45. The End
Notas do Editor
- Buonasera a tutti In this session I will introduce you to DevOps and why is becoming (or will soon be) a vital component of your organisation’s strategy I am Giulio Vian and work at the Dublin BuildIt Studio, part of Wipro Digital and my role is to help customers succeed in their digital transformation initiatives. As I am not a native English speaker hope you will forgive my mistakes.
- This is the agenda for the session First I will highlight some major trends of current social and business landscape Then I will define and describe DevOps and where it fits Lastly I will briefly give some advice on implementing DevOps in an organisation
- So let’s start with the first section about current social and business landscape
- In 2011, Marc Andreessen wrote an article titled “Why Software Is Eating The World” for WSJ He examined how new companies displaced established businesses: Borders by Amazon, Blockbuster by Netflix, and so on. Andreessen is the co-author of Mosaic, the first browser of the Internet. He sits on the board of directors of Facebook, eBay, and Hewlett Packard Enterprise, among others. Source: https://www.wsj.com/articles/SB10001424053111903480904576512250915629460
- Andreessen detailed and technical analysis needs no real explanation: many of us remember these tools. Paper maps, Film cameras, Disk players, Phone boots, and so on. I used them all!
- all replaced by the portable computer we call smartphone. Through the magic of software it replaced so many communication, recording and playback technologies.
- Probably Watts S. Humphrey isn’t much known outside the software engineering field, but maybe you bump into the Capability Maturity Model (CMM) that he invented. In his 2002 article titled “Why Every Business Is a Software Business” he enucleates three principles for organisations. Informit, Feb 22, http://www.informit.com/articles/article.aspx?p=25491
- A striking example of reliance on software is car manufacturing. We see some numbers: a 2018 article from McKinsey says that software is taking more and more of a car engineering and cost: 150 million lines of code is more than Microsoft Windows OS or the Facebook platform. What I found most striking in that piece is the statement “Software enables critical automotive innovations”. Does this means that you cannot innovate without software? https://spectrum.ieee.org/transportation/systems/this-car-runs-on-code Feb 2009 “This Car Runs on Code” By Robert N. Charette https://www.visualcapitalist.com/millions-lines-of-code/ https://www.mckinsey.com/industries/automotive-and-assembly/our-insights/rethinking-car-software-and-electronics-architecture
- First: Recognize That You Are in the Software Business Remember he wrote this in 2002 well before many transformation entered our ordinary life, still he points that every business depends on software. If you agree than you are half way through understanding DevOps.
- The second principle is that Software Quality Must Be the Top Priority. If your business depends on software, bad software will harm your bottom line. Financial industry showed up on newspaper front pages for quality and security issues despite care and regulations. DevOps helps by pushing quality controls upstream (shift left) and demanding investment in automated checks. Note that this principle makes no reference to any process, it asks for best-in-class outcomes. As a management principle it wants to guide your organisation and investment priorities.
- The last principle speaks about personnel management: Quality Software Is Developed by Disciplined and Motivated People. It is interesting the choice of these two adjectives.
- You need people that looks for perfection and teamwork, not Marvel superheroes It suggests team players, that care about rules, and know when to break them. Motivated balances the Disciplined: modern organisation are not assembly lines, they live and breath on intellectual work. You need people committed and caring about quality outcomes, eager to stay in touch with new technology. Source: https://youtu.be/-uaULx1WUzk?t=376
- We spent enough time on framing the discourse, it is time to move to the heart of the topic.
- Information Technology has lots and lots of different roles…
- …each role is a small fiefdom. The biggest groups in IT organisations are Developers and IT Operations. DevOps is a portmanteau of these: Developers and IT Operations. The term itself is ten years old (2009). The issue is that each group is defensive and complex parliamentary procedures go on between the two groups.
- DevOps aims at a continuous exchange of information and artefacts between interested groups. It advocates to remove barriers between these two groups in IT organisation and between IT and related groups of customers. Instead of high walls between specialties, IT must become porous and let the business flow smoothly.
- The DevOps Handbook represent a milestone in the IT industry. The authors’ definition is «DevOps is the result of applying Lean principles to the technology value stream»: we will see what it means in detail.
- Lean comes from manufacturing, most famous is Toyota. It focus on what creates value in the stream of work and what is waste.
- So, imagine an IT department efficient as car assembly line, delivering a new car every 90 seconds. (picture is from BMW factory) The analogy breaks down as a software feature is not a complete car, but the Lean principles, from modern manufacturing, are equally foundational. IT work benefits from techniques like automation, pull-model, value stream etc Reshaping IT processes you can obtain a constant flow of value to internal and external customers. No need to explain how this can favourably impact your Time-to-market for new products and services.
- The 90 seconds is a reality in huge systems like Facebook, but in Finance we see some examples of best-in-class amongst start-ups. N26, the online German bank is delivering many times per hour! Many of these changes are not visible to users but collectively build up new features. https://community.risingstack.com/how-n26-built-a-modern-banking-software-with-javascript-microservices/
- State of DevOps is an annual report, now from Google, that examines the DevOps transformation across industries. There is evidence of positive impacts on the bottom line for best performers compared to worse performers. https://cloud.google.com/blog/products/devops-sre/the-2019-accelerate-state-of-devops-elite-performance-productivity-and-scaling
- How this lean works in practice? We do no have time to detail everything: I will highlight two elements. https://queue.acm.org/detail.cfm?id=2945077
- A cargo ship is a good analogy to describe the characteristics of quarterly / annual releases: It consumes a huge amount of resources and costs a lot, in the order of M$. Requires lot of infrastructure and is as efficient as possible (fill ratio, route efficiency). And takes many weeks to deliver. On the other hand the cost of intra-city postal delivery is minimum, less efficient but quick (intra-day). This translates in faster feedback for senders. Clearly the risk is different. What if the address is wrong? A container is sent to the wrong side of the world and takes many weeks to be shipped to the original destination; a letter would be redelivered within days at much lower cost. Finally post is delivered daily, cargos … not.
- Approach software with a scientific mindset: each release changes how the system interacts with users. The outcome could be positive or negative. Every change is an experiment because we do not know future, people’s reactions, market condition. We need to focus on monitoring outcomes, anticipating failure costs and recovery procedures. No bone nor egg is broken here.
- So how we translate these ideas in our business?
- The Handbook describes the DevOps transformation by following the Three Ways.
- The ways are not exclusive but steps in a growth path: when you learn calculus in University, you still need the four basic operations you learned in primary school. Also the concept of number does not stay the same: it is refined and enriched. Similarly as there is not end limit in studying and researching math, there is no end goal in improving the process and reducing waste. The social and business environment changes and your organisation needs to constantly adapt.
- DevOps is NOT an IT Transformation: it is about the entire value stream that uses technology. Technology is a mean that connects Business to Customers that why IT is a crucial ring of the chain. Once major obstacles are removed from this stream, an organisation can move to the next Way or level. One delivers value when a feature is deployed in production Question: how long this takes in your organisation? You know where time is spent? Is the work visible?
- Compliance and security checks become part of automation and move as-early-as-possible in the chain
- Sadly many thinks that the First Way is all there is about DevOps. If one stops here, they won’t get the long-term benefits
- It is impossible to have perfect requirements and perfect implementations, that is why we need fast feedback mechanism. Stop delivering as soon as you discover a problem in the chain, it prevents the problem to become become worse. Focus on fixing any quality issue that slipped through instead of procrastinating solutions.
- If you do not improve constantly, your quality will degrade over time. The next level is about feedback: it entails removing communication obstacles that makes outcome of a release opaque. There is an important theme here: using a scientific approach to delivering value based on measures and facts.
- A more advanced techniques requires more investment. Develop two alternative implementations of the same change and offer it to two small subsets of your users. This technique is known as A/B or split testing.
- It should be clear that no product will be able to bring DevOps and the Three Ways into your organization.
- Myth #7—DevOps is Only for Open Source Software Although many DevOps success stories take place in organizations using software, such as the LAMP stack (Linux, Apache, MySQL, PHP), achieving DevOps outcomes is independent of the technology being used. Successes have been achieved with applications written in Microsoft.NET, COBOL and mainframe assembly code, as well as with SAP and even embedded systems. https://itrevolution.com/devops-handbook-debunking-devops-myths/ Also “The DevOps Handbook”
- To break barriers down, you can create multi-disciplinary stream-focused teams. Shift Performance metrics from Individuals to Teams, from Activities to Outcomes.
- And, despite the job market labels, hiring, so called, DevOps Engineers, will not transform your organisation. You risk to have a ultra-fast deliver pipeline… still shipping twice a year, a pure cost centre in the organisation.
- This is a question to IT managers… but also to HR and up to the CEO
- Justin Arbuckle, The real ROI of DevOps February 3, 2017 https://jaxenter.com/real-roi-devops-131520.html Case Study: Compuware DevOps Transformation David Rizzo May 7, 2018 https://itrevolution.com/case-study-compuware-rizzo/ Stop using ROI as the main IT driver Overall efficiency will improve by reducing waste Think of investing in IT as a survival strategy
- DevOps impacts on bottom line. https://medium.com/insiden26/what-hypergrowth-is-like-at-n26-bd3f3667cc46 5x in 18 months