2015 06-24 innovation in the large enterprise final-v2
3 likes3,453 views
This document discusses DevOps practices at a large retail company. It describes how the company implemented DevOps strategies like empowering full stack teams to own products and services end-to-end, making work visible through metrics and dashboards, and establishing a collaborative culture between development and operations teams. It provides examples of pilots done to shift infrastructure provisioning, application deployment, and automation processes from a legacy to a modern DevOps approach with benefits like reduced time and steps. The document emphasizes the importance of culture change, executive buy-in, focused pilots, and community involvement for successful DevOps adoption at large enterprises.
2015 06-24 innovation in the large enterprise final-v2
- 1. innovation in the LARGE enterprise Jeff Einhorn @jeffeinhorn
- 2. hello 2 1,795 stores in 49 states +347,000 team members 7 HQ locations 2 data centers 41 distribution centers
- 3. inspiration 3 ideas can sprout from a number of different sources including things you’ve • seen • heard • read • learned • experienced
- 4. inspiration 4 YOU don’t have to reinvent the wheel seek out, learn from, leverage great work that already exists
- 5. inspiration 5 get, stay connected with the broader tech community
- 6. inspiration continuous learning is critical to being able to generate new ideas, refine existing work, or kill an afternoon 6
- 7. 7 inspiration what’s driving you, your team, your clients, or the business crazy?
- 8. gettingfocused QUADRANT 1 § Crises § Deadline driven projects § Fire-fighting QUADRANT 2 § Building capabilities § Maximizing opportunities § Risk management QUADRANT 3 § Interruptions § Most meetings and e-mail QUADRANT 4 § Trivia § Busy work § Time wasters urgent not urgent notimportantimportant spending too much time putting out fires and only getting more and more behind Stephen Covey’s approach to time management is to create time to focus on important things before they become urgent. Sometimes this just means doing things earlier. The real skill is to commit time to processes that enable you to do things more quickly or more easily, or ensure that they get done automatically.
- 9. help! 9 DevOps the solution to everything that’s wrong in your life
- 10. but…… 10 DevOps seems to describe a lot of things • culture • tools • technology what is it?
- 12. community culture Shared Goals versus Operations = Stability & Development = Features Operations & Development engineers participating together in the entire service lifecycle, from design through the development process to production support what it looks like @ Target § Open Labs § Challenges § FlashBuilds § Coaching § #ChatOps § #HugOps § DevOpsDays § Leader Summits
- 13. products&services ownership Product/Service Ownership versus Project Products & Services are delivered, continuously improved and managed for the long term by end-to-end by full stack teams focused on meeting customer needs what it looks like @ Target § Project Argus § real Product ownership
- 14. makeworkvisible Request 30 min .75 days C/T 25 min Step 4 53 min 11 Days 6.3 hours 47 Days End User C/T 105 min Step 7 C/T 30 min Step 2 C/T 53 min Step 3 C/T 75 min 7.7 Days 15 min 1.5 Days C/T 17 min Step 3.1 C/T 13 min Step 3.3 C/T 23 min Step 3.2 C/T 15 min Step 1 C/T 75 min Step 5 C/T 75 min Step 6 C/T 75 min 6.5 Days C/T 25 min 3.4 Days C/T 105 min 16 days C/T 15 min Step 6.1 C/T 75 min Step 6.2 C/T 15 min Step 6.3 Delivered measurement Sub-optimization versus Identifying Bottlenecks Measure everything you want to improve. Value stream process before you start, measure deployments, time to deploy, incidents per deploy, blast radius/severity of incidents. Report on service adoption & competing service adoption to better understand customer needs and how to improve what it looks like @ Target § value stream mapping § dashboards tied to business critical KPIs § end-of-sprint demos
- 15. powertothepeople empowerment Automated Build & Deploy of App/Infrastructure versus separate engineers hand crafting pieces Engineers have access to the tools they need and can improve existing processes to solve problems and improve delivery what it looks like @ Target § self-service api access to create § networks § servers § compute
- 16. keepingintouch feedback Frequent Small Changes versus Large Changes Agile Sprints versus Annual Planning Operations & Development makes small changes frequently to learn quickly from failures & customer feedback then adjusts future works what it looks like @ Target § open demos (i.e., everyone is invited) § consistent communication cadence § #ChatOps § strategic collocation
- 17. techfoundation technology practices Reusable Automation & Services versus Scripting & Monolithic applications Infrastructure as Code, Shared Source Code, Social Coding, Agile Practices, Continuous Integration/ Delivery, Scrum, Agile what it looks like @ Target § CI/CD tooling § Scrum practices § sprints § release planning § standups § retrospectives § demos
- 18. Customer DevOps@TGT Empathy Collaboration Test & Learn Dev Ops Ownership Products & Services are delivered, continuously improved and managed for the long term by end-to-end by full stack teams focused on meeting customer needs (Product/Service Ownership versus Project) Feedback Operations & Development makes small changes frequently to learn quickly from failures & customer feedback then adjusts future works (Frequent Small Changes versus Large Changes) (Agile Sprints versus Annual Planning) Measurement Measure everything you want to improve. Value stream process before you start, measure deployments, time to deploy, incidents per deploy, blast radius/severity of incidents. Report on service adoption & competing service adoption to better understand customer needs and how to improve (Sub-optimization versus Identifying Bottlenecks) Empowerment Engineers have access to the tools they need and can improve existing processes to solve problems and improve delivery (Automated Build & Deploy of App/ Infrastructure versus separate engineers hand crafting pieces) Tech Practices Infrastructure as Code, Shared Source Code, Social Coding, Agile Practices, Continuous Integration/Delivery, Scrum (Reusable Automation & Services versus Scripting & Monolithic applications) Culture Operations & Development engineers participating together in the entire service lifecycle, from design through the development process to production support (Shared Goals versus Operations = Stability & Development = Features)
- 19. didImention… 19 estimate of organizations attempting to use DevOps without specifically addressing their cultural foundations will fail by 2018 http://www.gartner.com/newsroom/id/3032517 culture is important 90%it eats strategy for breakfast, lunch, dinner and as a midnight snack
- 20. ourgrowingmethods 20 internal DevOps mini-conference internal social media site quarterly day long hackathon monthly session to share, get feedback, inspire & be inspired
- 21. casestudy 21 nice story so far … what does reality look like?
- 23. whydothis 23 hint: people look like this more often than not
- 24. IaaS to get infrastructure on demand with all components, access needed to make things work OpenStack PaaS to quickly prove out new ideas OpenShift Automation to create a foundation to build out services for everything in IT Chef, Jenkins, etc. step1|developstrategy empower customers to use service management for 24
- 25. step2|layfoundation 25 get what you need to succeed hint: executive support to get the team, space and time needed to build out new capabilities
- 26. step3|getshiftdone 26 legacy approach modern approach projects long cycle times siloes & hand-offs fractured accountability end state integration, testing complex products/services short cycle times tight collaboration end-to-end accountability continuous integration, testing simple
- 28. IaaSpilot • identified software development team aligned to strategic priority • provided team with • 1 embedded engineer • 1 part-time CI/CD coach • 1 part-time tool consultant • collocated work environment • IaaS + custom PaaS environment • CI/CD tooling environment • team conducted 2-day sprints over 30 days with full Scrum ceremonies • team worked directly with self-service infrastructure tools 30minutes3months legacy approach modern approach
- 29. PaaSpilot 29 create development environment • reduced number of steps (from 11 to 1) • reduced number of requests (from 11 to 0) • shift from Service Catalog to Self-Service Portal • eliminate dependencies, pre-requisites, and hand-offs 15minutes8weeks legacy approach modern approach
- 30. Automationpilot 30 create pipeline infrastructure • reduced number of steps (from 13 to 2) • reduced number of requests (from 13 to 1) • shift from Service Catalog to Self-Service Portal • eliminate dependencies, pre-requisites, and hand-offs • use Chef to deploy Chef 10minutes9months legacy approach modern approach
- 31. IaaS 1000+ VMs spinning up every day after 6 months OpenStack PaaS Dozen’s of developers via word of mouth and no support team OpenShift Automation Thousands of Nodes & Cookbooks for everything. Checkout our community BigIP cookbook – 800k downloads Chef, Jenkins, etc. signsofsuccess adoption is your measure of success 31
- 32. keylearnings 32 be focused be bold pilot iterate ownership matters #make_awesome_happen you build it, you run it Werner Vogels, Amazon CTO
- 34. setcourse 34
- 36. getstuffdone 36
- 39. keepintouch 39 Jeff Einhorn Twitter @jeffeinhorn #DOTGT Target Tech Blog http://target.github.io The Goat Farm http://goatcan.do