Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The DevOps Playbook: How to Start, Scale, and Succeed

237 views

Published on

Over the past few years, Puppet’s annual State of DevOps Report has shown that DevOps practices have a positive impact on business results, improving speed, agility, security, and stability. This link is widely acknowledged; what’s less clear is how to achieve these results.

Our 2018 State of DevOps Report is a prescriptive guide to achieving DevOps success: from building the foundation to scaling across teams. Based on the experiences of over 3,000 survey respondents, we’ve mapped distinct phases of the evolution and the key practices needed to advance to each stage.

In this webinar, the report’s authors discuss findings from the report, the five stages of DevOps evolution, and how they apply to your organization.

Published in: Technology
  • Be the first to comment

The DevOps Playbook: How to Start, Scale, and Succeed

  1. 1. How to start, scale and succeed Presented by Alanna Brown, Nigel Kersten, Andi Mann and Michael Stahnke
  2. 2. About the authors Alanna Brown @alannapb Nigel Kersten @nigelkersten Michael Stahnke @stahnma Andi Mann @andimann
  3. 3. 2018 State of DevOps Survey ● 3,000+ respondents ● Better global representation ● Translated in French, German, Japanese and Malay 4 Survey responses by region Over the past 7 years, we’ve gathered 30,000+ responses from around the world, making the State of DevOps Report the largest and most comprehensive study on the topic of DevOps.
  4. 4. Roles, departments, teams
  5. 5. We want to hear from you! ● How did you expand DevOps success beyond a single team? What worked and what didn’t? ● How do you collaborate with ITSM and ITIL in this new DevOps world? ● What’s hard with about automating incident response in your organization? ● How did you get executive buy-in? If you’re an executive, what do you need to know to support your team as they adopt DevOps practices? ● How do you make sure your organization is doing monitoring and alerting the right way?
  6. 6. Key findings 7 ● In a DevOps evolution, there are many paths to success, but even more that lead to failure. ● Executives have a rosier view of their DevOps progress than the teams they manage. ● Start with the practices that are closest to production; then address processes that happen earlier in the software delivery cycle. ● Cross-team sharing is the key to scaling DevOps success. ● Automating security policy configurations is mission-critical to reaching the highest levels of DevOps evolution.
  7. 7. In a DevOps evolution, there are many paths to success, but even more that lead to failure. 8
  8. 8. 5 Stages of DevOps Evolution
  9. 9. 5 Stages of DevOps Evolution 10 Stage 1: Normalization Application development teams use version control Teams deploy on a standard set of operating systems Stage 2: Standardization Teams deploy on a single standard operating system Build on a standard set of technology Stage 3: Expansion Individuals can do work without manual approval outside team Deployment patterns for building apps/services are reused * Infrastructure changes are tested before deploying to production Stage 4: Automated Infrastructure Delivery System configurations are automated Provisioning is automated * System configs are in version control * Infrastructure teams use version control * Application configs are in version control * Security policy configs are automated Stage 5: Self-service Incident responses are automated Resources available via self-service * Applications are rearchitected based on business needs * Security teams are involved in technology design and deployment Stage 0 Monitoring and alerting are configurable by the team operating the service Reuse deployment patterns for building applications or services Reuse testing patterns for building applications or services Teams contribute improvements to tooling provided by other teams Configurations are managed by a configuration management tool * These practices are highly correlated with the stage.
  10. 10. Stage 0: Build the Foundation 11 • Monitoring and alerting are configurable by the team operating the service • Reuse deployment patterns for building applications or services • Reuse testing patterns for building applications or services • Teams contribute improvements to tooling provided by other teams • Configurations are managed by a configuration management tool
  11. 11. Stage 0: Monitoring and alerting are configurable by team operating the service 24xmore likely to always enable configuration of monitoring and alerting
  12. 12. Stage 0: Reuse deployment patterns for building applications or services 23xmore likely to always reuse deployment patterns for building applications or services
  13. 13. Stage 0: Reuse testing patterns for building applications or services 44xmore likely to always reuse testing patterns for building applications or services
  14. 14. Stage 0: Configurations managed by configuration management tool 27xmore likely to always manage configurations using a configuration management tool
  15. 15. Stage 0: Contribute to other teams’ tooling 44xmore likely to always contribute to other teams’ tooling
  16. 16. Stage 1: Normalize the Technology Stack 17 Stage Defining Practices Contributors to Success ● Application development teams use version control ● Deploy on a standard set of operating systems ● Build on a standard set of technologies ● Put application configurations in version control ● Test infrastructure changes before deploying to production ● Source code is available to other teams 1
  17. 17. Stage 2: Standardize and Reduce Variability 18 Stage Defining Practices Contributors to Success ● Deploy on a single standard operating system ● Build on a standard set of technologies. ● Reuse deployment patterns for building applications and services ● Re-architect applications based on business needs ● Put system configurations in version control 2
  18. 18. Stage 3: Expand DevOps Practices 19 Stage Defining Practices Contributors to Success ● Individuals can do work without manual approval outside team ● Reuse deployment patterns for building applications and services ● Infrastructure changes are tested before deploying to production* ● Individuals accomplish changes without significant wait times ● Post-incident reviews occur and results are shared ● Build on a standard set of technologies ● Teams use continuous integration ● Infrastructure teams use version control ● Service changes can be made during business hours 3
  19. 19. Stage 4: Automate Infrastructure Delivery 20 Stage Defining Practices Contributors to Success ● Automate system configurations ● Automate provisioning ● Application configurations are in version control* ● Automate security policy configurations ● Resources made available via self service 4
  20. 20. Stage 5: Provide Self-Service Capabilities 21 Stage Defining Practices Contributors to Success ● Incident responses are automated ● Resources available via self- service ● Re-architect applications based on business needs* ● Security teams are involved in technology design and deployment* ● Security policy configurations are automated ● Application developers deploy testing environments on their own ● Success metrics for projects are visible ● Experiences and lessons are shared externally ● Provisioning is automated 5
  21. 21. Cross-team sharing is the key to scaling DevOps success. 23
  22. 22. Sharing and DevOps evolution
  23. 23. Executives have a rosier view of DevOps progress than the teams below them. 25
  24. 24. Start with the practices that are closest to production, then address processes that happen earlier in the software delivery cycle. 27
  25. 25. Automating security policy configurations is a critical practice at the highest levels of DevOps evolution. 28
  26. 26. Questions 29
  27. 27. 30 Get your copy @ puppet.com/state-of-devops-report

×