DevOps Point of View An Enterprise Architecture perspective Amsterdam, 2020 Management summary “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”1 Setting the scene Goal of this Point of View In the current world of IT and the development of This point of view aims to create awareness around the IT-related products or services, companies from transformation towards the DevOps way of working, to enterprise level to smaller sizes are starting to help gain understanding what DevOps is, why you need it use the DevOps processes and methods as a part and what is needed to implement DevOps. of their day-to-day organization process. The goal is to reduce the time involved in all the An Enterprise Architecture perspective software development phases, to achieve greater Even though it is DevOps from an Enterprise Architecture application stability and faster development service line perspective, this material has been gathered cycles. from our experiences with customers, combined with However not only on the technical side of the knowledge from subject matter experts and theory from organization is DevOps changing the playing within and outside Deloitte. field, also an organizational change that involves merging development and operations teams is Targeted audience required with an hint of cultural changes. And last but not least the skillset of all people It is specifically for the people within Deloitte that want to involved is changing. use this as an accelerator for conversations and proposals & to get in contact with the people who have performed these type of projects. By all means, it is a deck that can be shared within Deloitte and with our customers to provide a more holistic 1 Charles Darwin view. © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 2 DevOps practitioners For questions or remarks, feel free to reach out to our DevOps practitioners Eric Onderdelinden Mark Maijs Donald Pondman Director Senior Manager Manager Enterprise Architecture Enterprise Architecture Enterprise Architecture Deloitte Consulting Deloitte Consulting Deloitte Consulting +31 6 83 33 98 16 +31 6 83 89 02 14 +31 6 83 33 02 56 [email protected] [email protected] [email protected] Balázs Nagy Boris Smits Marlies Quekel Senior Consultant Consultant Analyst Enterprise Architecture Enterprise Architecture Enterprise Architecture Deloitte Consulting Deloitte Consulting Deloitte Consulting +31 6 13 31 37 65 +31 6 82 67 44 36 +31 6 50 07 02 16 [email protected] [email protected] [email protected] © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 3 Contents What is DevOps? 5 Why do I need DevOps? 9 Where is DevOps applicable? 12 What is needed for DevOps to work? 14 • People 16 • Process 24 • Technology 27 • Operating Model 33 How do I implement DevOps? 38 Deloitte Accelerators 42 Client Examples 46 © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 4 What is DevOps? © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 5 What is DevOps? DevOps is a new way-of-working that improves value delivery for the customer and enables benefits for both development and operations Definition Goal DevOps is a new approach to optimize and DevOps primary goal is to improve the flow manage end-to-end service delivery and from an idea towards value for the customer, operations. It applies a set of principles to enabled by an environment in which transform the entire software delivery lifecycle multidisciplinary teams work collaboratively to to introduce new practices enabled by continuously deliver high quality solutions, in a technology faster pace, that qualify for operations New DevOps practices: DevOps principles • Continuous Integration Benefits • Continuous Testing • Culture of shared responsibility • Increases the frequency and and collaboration • Continuous Delivery quality of deployments and releases • End-to-end ownership of services • Continuous Operations Improves innovation and risk- • Multi-disciplinary teams • taking • Incremental value delivery • Realizes faster time to market • Flow optimization in the delivery Applying DevOps principles process • Improves solution quality and to the SDLC lead to new operational reliability • Automate (almost) everything practices that benefit both • Improves the Mean Time to • Measurement of everything Development and Operations Recover (MTTR) • Continuous improvement © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 6 The History of DevOps DevOps is becoming the norm in software delivery and is increasingly being adopted & matured across enterprises, becoming the new best practice The chronic conflict The grass roots movement DevOps State of DevOps between Dev & Ops is takes off incorporated into report defines 5- explored SAFe stage approach DevOps expands upon the 2008 Based on personal experience 2010 practices of “infrastructure as 2015 SAFe is rapidly gaining 2018 From level 0 to 5, a living in the world of Dev and code” and continuous integration traction in the enterprise descriptive, pragmatic Ops, Patrick Debois from and deployment. DevOps principles arena, where DevOps is approach is introduced Belgium starts investigating start being applied to the IT value adopted and scaled to guide teams and the chronic conflict between stream. across. mature DevOps Dev and Ops. initiatives, a report sponsored by Deloitte Pre-DevOps The “DevOps” term is “DevOps is the DevOps is the Enterprises embed coined future” new norm for more IT functions Pre- In IT, traditional 2009 2011 2016 high-performing 2019 in their teams next 2008 waterfall methods of Andrew Shafer and Patrick March 2011, Gartner companies to ‘Dev’ and ‘Ops’ Debois meet at the predicts “By 2015 application “Clearly, what was “organizations are DevOpsDays 2009 and later DevOps will be adopted development were state of-the-art three embedding security at Velocity conference, the by 20% of the Fortune losing ground to years ago is just not (DevSecOps), privacy, term is picked up: 2000.” iterative methods such good enough for policy, data (DataOps) as agile. Speed “10+ Deploys a Day – a Most CIOs and IT today’s business and controls into their became the goal, collaboration between Dev organizations are looking environment.” DevOps culture and which took priority & Ops at Flickr” – Velocity, into doing work processes.” p.18, 2016 State of over development and 2009. differently. Deloitte Tech Trends deployment processes. DevOps Report 2019 © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 7 DevOps practices DevOps practices apply continuous automation cycles throughout software development and operations processes Continuous Integration Continuous Delivery the streamlining of internal is the process of delivering development by integrating code that is production code into a shared ready and is kept in an repository several times a always releasable state, so day. Each check in is then it can be deployed verified by an automated (automatically) to build, allowing teams to production at any given detect problems early in time based on business the cycle needs Continuous Testing Continuous Operations automating and integrating is proactively managing the tests into the software solution based on feedback delivery chain, and loops. Monitoring and automatically executing telemetry become part of those tests against each the backlog. Processes build of the code base such as patching also fall under this practice © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 8 Why do I need DevOps? © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 9 Traditional function separation for Development and Operations Prior to DevOps change release frequency was low, Development and Operations worked separately to serve business demands, having completely opposite mindsets Business Request Demand features Stability Development Operations Changes Features Safeguards Stability 1. Focusses solely on development activities 1. Focusses solely on operational activities 2. Operational requirements are unclear between 2. Operational requirements are unclear, needing environments making the hand-over cumbersome ad-hoc changes to the environment 3. Operational feedback is only retrieved after 3. Operational understanding and experience is completing a release gained only when the app is released 4. After releasing, developers are no longer 4. Operators manage and control software involved written by others © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 10 DevOps unifies the mindset of Development and Operations Today business wants to release on demand. With DevOps, both functions continuously collaborate to align business demands within the software delivery lifecycle Business Request Demand features Stability Development Operations Changes Features Safeguards Stability End-to-end management and The DevOps culture emphasizes traceability of software a common goal over the delivery during development whole value delivery chain and issue solving All members understand IT governance (e.g. security) change, are responsible and is embedded within the accountable as a whole, and software development best trust each other to deliver practices The DevOps technology Integrated software testing embraces CI/CD to automate DevOps approach to validate code the broken delivery funnel quality earlier in the process © 2020 Deloitte The Netherlands Deloitte DevOps Point of View 11 Where is DevOps applicable? © 2020 Deloitte
Details
-
File Typepdf
-
Upload Time-
-
Content LanguagesEnglish
-
Upload UserAnonymous/Not logged-in
-
File Pages55 Page
-
File Size-