Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

Rethinking Your DevOps Strategy

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Cargando en…3
×

Eche un vistazo a continuación

1 de 30 Anuncio
Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

Similares a Rethinking Your DevOps Strategy (20)

Anuncio

Más de Mandi Walls (20)

Más reciente (20)

Anuncio

Rethinking Your DevOps Strategy

  1. 1. Rethinking Your DevOps StrategyMandi Walls
  2. 2. Hi There Mandi Walls Technical Community Manager in EMEA @LNXCHK mandi@chef.io With Chef since November 2011 EMEA-based since September 2014
  3. 3. Every Business is a Software Business We’re going to be a software company with airplanes CIO, Alaska Airlines
  4. 4. DevOps A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.
  5. 5. What Is DevOps Strategy? • Tools • People • Goals • Priorities • Projects • Communication • ???
  6. 6. What is Your DevOps Strategy? • Buy A Tool • Require already-busy people to learn to use it • Create obtuse workflows • Wonder why DevOps didn’t work for you • Hide the evidence
  7. 7. Thinking About Goals
  8. 8. DevOps is NOT the Goal • Sort of got lost in Agile • “We’re all going Agile”
  9. 9. Why Are You Looking at DevOps? • Shorter Time-to-Market for new features • Faster remediation of bugs • Faster response to customer needs and issues • Reduce outages
  10. 10. Articulate Goals • Set measureable improvements You need to be measuring things at the beginning, too. Are you? • Support experimentation You don’t know yet what’s going to lead to the best improvements • Publish your goals and broadcast your improvements
  11. 11. Prioritize tasks • Take work away from teams learning new procedures • Over-burdening teams learning DevOps will not create success • Never completing a single DevOps conversion will not create success • Changing course over and over for whatever reason will not create success
  12. 12. Support experimentation • Some tasks won’t have “best” practices Many will have better practices that you should try • None of this happens overnight
  13. 13. Technology
  14. 14. What Are Your Teams Already Doing? • Are you using change control for everything that affects production? • Is your source code viewable by everyone in the organization? Multiple apps working in same tech stack benefit from shared knowledge • Are you Automating? • Are you sharing outcomes, metrics, data? • Have you gotten caught up in shiny things that haven’t helped your goals?
  15. 15. Technology is to Help You “We are able to focus on the small things that usually fall through the cracks, rather than on only the basics of the job. So many of the routine tasks are just taken care of for us. Seeing other offices that choose to do things differently and not embrace having the product do the “heavy lifting” are beyond my understanding. In particular, the extensive reporting in the product is so helpful for seeing how business is doing and what needs follow up.” hometrak.com/client-spotlight-lynn-gardini/ If a tool is making work harder, and your teams are working around it, change the tool.
  16. 16. Automation is Not Scary • Applications might need some refactoring if they weren’t built to be used at scale • Scale requires automation • Bad architectural decisions can hold you back These are bits, not bricks
  17. 17. Culture
  18. 18. Culture Change is Hard Permanent change isn’t built with contractors
  19. 19. Increasing Number of Resources • Postmortems • Building blameless cultures • Building cultures with open communication Healthcare industry • Building cultures with shared responsibility Manufacturing
  20. 20. People
  21. 21. Your Employees • Contractor culture No responsibility, no long-term strategy, no investment • Burdened by cuts during recession • Prioritize, do not dump more tasks on them and expect success
  22. 22. Should I build a DevOps team? • Yes and No • Yes: as a short-term solution to help with prioritization and resources • NO: as a long-term reassignment of operations task to another layer of organization Development Operations Development DevOps Infrastructure Operations
  23. 23. Making Space in the Day • Stop everyone doing low-value work • Is this work helping us reach our goal? • Is anyone using the outputs of this work? • Can it be automated? • Is it as important as something else? • Will the world burn if we don’t do it as often? https://hbr.org/2016/06/stop-doing-low-value-work
  24. 24. Rewards and Celebration • Give people a venue for pride • Internal talks and showcases • Internal DevOps Days • Invite speakers • Send people to events • Have a budget for parties or swag
  25. 25. Tools Culture People
  26. 26. Time • It’s easy to get frustrated • Corporate cultures that favor short-term results make long-term improvements challenging • Re-orgs, new executives, other changes will get in the way • Have an elevator pitch for what your initiative is doing right when the environment changes We are steadily improving the time to market in our consumer products by embracing agile development practices, proactive metrics and monitoring collection, automation, and rapid releases.
  27. 27. Attack the Mountain One Step at a Time • Your organization has a lot of applications • Built by a number of teams and maybe external vendors • You need to get a good first-pass process the whole way from idea to production release on one of these applications before setting everyone free • Iterate when you’ve learned a lesson
  28. 28. • Remember the three areas: Tools, People, Culture • Lots more information, practices, use cases available now than there were two or three years ago • Set your goals and measure your improvements. • Celebrate!
  29. 29. We are Chef • https://www.chef.io • https://learn.chef.io • Visit our booth to talk about Chef, system automation, continuous delivery, improving IT velocity, hugs, and stickers

Notas del editor

  • If you’re struggling to just keep the lights on, taking on a big new initiative is going to be tough. Look for tools that help you really get improvement
  • You don’t have to rehire the whole team. You will have to retrain a number of people. You will have to give them time to learn stuff. The sysadmin who’s been at your company for 25 years didn’t learn everything overnight 25 years ago, and you can’t expect that this time around either.

×