Sally Reade Partner Manager, Puppet Sally Reade is Puppet’s Partner Sales Manager EMEA. She’s previously worked at Violin Memory as their Channels Sales Director EMEA, as well as at TINTRI, WHIPTAIL, Dell EMC, Veeam Software, VMware, GE Global Exchange Services and MicroStrategy. Her reputable career spans close to 20 years.

1. Key Findings
Nigel Kersten - VP of Ecosystem Engineering, Puppet

3. About the authors
Alanna Brown
Original creator and
author of the report;
Director of Product
Marketing at Puppet.
Nigel Kersten
Longstanding report
author; VP of
Engineering at
Puppet. Former Site
Reliability Engineer at
Google.
Michael Stahnke
Sr. Director of
Engineering at
Puppet; pioneered
DevOps practices in
the enterprise before
DevOps was even a
thing.
Andi Mann
Chief Technology
Advocate at Splunk,
specializing in working
with enterprises for
decades on digital
transformation and
DevOps initiatives.

4. 2018 State of DevOps Survey
● 3,000+ respondents
● Better global representation
● Translated in French, German,
Japanese and Malay
4CONFIDENTIAL - DO NOT DISTRIBUTE
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.

5. Industry and annual revenue
CONFIDENTIAL - DO NOT DISTRIBUTE

6. Roles, departments, teams
CONFIDENTIAL - DO NOT DISTRIBUTE

7. 5 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.
CONFIDENTIAL - DO NOT DISTRIBUTE

8. Stage 0: Build the Foundation on Standardization
8
• Monitoring and alerting are configurable by the team operating the service
○ High performing teams are 24 times more likely to configure monitoring and alerting
• Reuse deployment patterns for building applications or services
○ Successful teams are 23 times more likely to reuse deployment patterns
• Reuse testing patterns for building applications or services
○ High performing teams are 44 times more likely to reuse testing patterns
• Teams contribute improvements to tooling provided by other teams
○ By using CM tools teams are 44 times more likely to contribute to other teams tooling
• Configurations are managed by a configuration management tool
○ Successful teams are 27 times more likely to always use a CM tool for CM
CONFIDENTIAL - DO NOT DISTRIBUTE

9. Key Finding 1:
In a DevOps evolution,
there are many paths to
success, but even more
that lead to failure.
9

10. 5 Stages of DevOps Evolution
CONFIDENTIAL - DO NOT DISTRIBUTE

11. Stage 1: Normalize the Technology Stack
11
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
CONFIDENTIAL - DO NOT DISTRIBUTE

12. Stage 2: Standardize and Reduce Variability
12
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
CONFIDENTIAL - DO NOT DISTRIBUTE

13. Stage 3: Expand DevOps Practices
13
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
CONFIDENTIAL - DO NOT DISTRIBUTE

14. Stage 4: Automate Infrastructure Delivery
14
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
CONFIDENTIAL - DO NOT DISTRIBUTE

15. Stage 5: Provide Self-Service Capabilities
15
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
CONFIDENTIAL - DO NOT DISTRIBUTE

16. Key Finding 2 :
Executives have a rosier view
of DevOps progress than
the teams below them.
16

18. Key Finding 3:
Start with the practices that are
closest to production, then
address processes that happen
earlier in the software delivery
cycle.
18

19. Key Finding 3
19
● Re-use deployment patterns for building applications and services
○ Successful organisations 23 X more likely to employ this practice
● Monitoring and Alerting configurable by the team operating the service
○ Successful organisations 24 X more likely to employ this practice
● Configurations managed by CM tool
○ Successful organisations 27 X more likely to use configuration management
CONFIDENTIAL - DO NOT DISTRIBUTE

20. Automation and DevOps evolution

21. Key Finding 4 :
Cross-team sharing is the key
to scaling DevOps success.
21

22. Sharing and DevOps Evolution

23. Culture and DevOps Evolution - Active Promotion

24. Key Finding 5:
Automating security policy
configurations is a critical
practice at the highest levels
of DevOps evolution.
24

25. Security Policy Configuration
25
● Mission critical
○ Internal considerations eg RBAC
○ External - eg Sarbanes Oxley, GDPR
● Contributor to success in cross team sharing - eg remote, cloud based
DBs
● Automated security policy ensures compliancies
● Building into configuration management acts as a normalizing function for
the team
● Building into application design and build to eliminate security incidents
upon release
CONFIDENTIAL - DO NOT DISTRIBUTE

26. 5 Key Findings - Summary
26
● The DevOps Journey is not Linear - it’s Evolutionary
● The 5 Key Stages and Foundational Stage (0) are currently relevant to
Organisations
● As Organizations evolve, the focus practices will also change and evolve
● The Devops Journey has multiple starting points and no final destination
● The Puppet model is to help Organizations get started and scale success
fast through best practices
● DevOps is a Culture - not a Technology
CONFIDENTIAL - DO NOT DISTRIBUTE

27. Cloud Management with Puppet

28. Application Deployment with Puppet

29. Environment Provisioning with Puppet

30. 30
Get your copy today @ puppet.com

31. Questions?
Thank You !
31