Doing Cloud Right! Five Keys to Becoming an Elite DevOps Performer

© Electric Cloud | electric-cloud.com | @electriccloud
2018 Accelerated State Of DevOps Report
Doing Cloud Right! Five Keys to Becoming
an Elite DevOps Performer

Introductions – Your Speakers!
Jez Humble
CTO, DORA. Author.
@jezhumble
Anders Wallgren
CTO, Electric Cloud
@anders_wallgren
/ @electriccloud - #ecwebinar

Agenda
• What does the 2018 Accelerated State Of
DevOps Report say about elite DevOps
performers and cloud adoption?
• What are the 5 Keys to Doing Cloud Right?
Why are they so important to DevOps
success?
• What are useful strategies to adopt 5 keys,
and better adopting cloud and microservices
in your software release.

© 2018, DevOps ResearchandAssessment, LLC. All Rights Reserved.4
● Largest and longest-running research of its kind
● 5 years of rigorous research, surveying 30,000+ professionalsworldwide
● Investigates practices that lead to higher software delivery performance
● Higher software delivery performance = powerful business outcomes
● Only report to include performance benchmarks with cluster analysis
● Predictive analysisto identify specific improvement strategies
The Accelerate: State of DevOps Report

© 2018, DevOps ResearchandAssessment, LLC. All Rights Reserved.5 © 2018, DevOps ResearchandAssessment, LLC. All Rights Reserved.
Software Delivery and Operational
performance
(SDO performance)
2018 - Key Themes
SDO performance is the driver that unlocks
competitive advantages for IT
organizations.
SDO performance is the practice behind not
just creating, but also operating, software in
ways that generate powerful business
outcomes.

Identify the key
Technical Practices
that drive SDO performance
2018 - Key Themes
confirms findings from previous years.
New for 2018, key technical practices
include:
● Monitoring and observability
● Continuous testing
● Database change management
● "Shifting left" on security

Identify the key
Cultural Practices
that drive SDO performance
2018 - Key Themes
confirms the Westrum cultural model from
previous years.
New for 2018! How to influence culture
through organizational work:
● Influencing culture through
autonomy & trust
● Creating a culture of learning
(retrospectives)

Key Findings - Elite Performers

Key Findings - Year over Year

2018: Key Differences

Adding Availability
Abilityfor teams to ensure their product
or service can be accessed by end users
Software delivery +
operationalperformance is
SDO performance
Elite performers are
3.5X more likelyto have strong
availabilitypractices

Elite Performers
Data shows a new 4th high performance
group:
elite performers
Proportion of high performers has grown
YoY, but the bar for
excellence remains high
Elite performers are still able to optimize
for throughput and stability

Key Topics of Interest

New 2018 Performance Benchmarks

Doing Cloud Right
It's not just about adopting cloud, it’s
using cloud in essential ways that
matters.
Only 22% of teams are doing cloud right
Teams that use these essentials
characteristics are 23X more likely to be
elite performers
AGREED OR STRONGLY AGREED
On-demand self-service
Broad network access
Resource Pooling
Rapid elasticity
Measured service

Open Source Software
The data shows that using open source
software is correlated with high SDO
performance
Teams that use open source software are
1.75X more likely to be elite performers
Those same teams are also
1.5X more likelyto expand their open
source usage in future

Industry Doesn’t Matter
Industry does not matter for achieving
high performance for software delivery
High performers exist in both non-
regulated and
highly regulated industries alike
Any team in any industry has the
potentialto achieve a high degree of
SDO performance

Don’t Forget the Database
Integrating databasework into software
delivery positively contributes to SDO
performance
Integrating databasepractices look much
like integrating ops work in early days:
communication,config management,
includingteams, visibility
Teams could think about this like
“shifting left”

An Evolution in Testing
Automated testing played a role in prior
years’ research. We investigated if the
evolving role of testing in continuous
delivery contributes.
Continuoustesting extends automated
testing practices and positively
contributes to SDO performance

Looking Into Our Systems
Teams with a comprehensive monitoring
and observabilitysolution were 1.3 times
more likely to be an elite performer.
Having a monitoring and observability
solutionpositively contributed to SDO
performance.
Fun stats fact: monitoring and
observabilityload together.

Deeper Analysis

Surprises

Misguided Performers
Some teams optimize for caution: low
deploy frequency, high lead times, and
low deploymentfailure
That same group also reports the longest
times to restore service
for outages (1-6 months!)
Large-batch changes add complexity &
no one thinks it will happen to them, but
5% of teams
suffer the consequences

The J-Curve of Transformation
Teams begin
transformation
and identify
quick wins
Automation helps low
performers progress to
medium performers
Automation increases test
requirements, which are dealt with
manually. A mountain of technical
debt blocks progress.
Technical debt and increased complexity
cause additional manual controls and
layers of process around changes,
slowing work
Relentless improvement
work leads to excellence
and high performance!
High and elite performers
leverage expertise and
learn from their
environments to see
jumps in productivity

Outsourcing
Low performing teams are
3.9X more likelyto use functional
outsourcing than elite teams
Elite teams rarelyadopt
functionaloutsourcing
Misguided performers have the
highest use of outsourcing
of all groups

Major Takeaways

Ways to Improve SDO Performance
● Adopting essential cloud characteristics is key to truly realizing benefits
● Organizationsneed to make smart investments in technology, lean practices and
culture -- holistic transformation is important
● The data on functionaloutsourcing is in, and it’s decisive: this is not a winning bet
● Optimize for throughput, stability,and availability

Doing Cloud Right
The 5 Keys

Polling Question

Cloud adoption and Tectonic Shifts
Challenges and opportunities
• ApplicationArchitecture
o Monolith → Loosely Coupled / Cloud Native / Microservices / Functions-AAS
• Delivery Architecture
o Traditional Releases → Continuous Delivery Pipelines
• Operational Architecture
o Bare-metal → VM → Cloud VM → Container → K8 → Serverless
o “Hybrid” is the “new normal”
• Orchestration Architecture
o Manual → Scripted → Abstract Models/Declarative (aka *-as-code)
Pressures from both the Left and the Right!

And Enterprise Release is Already Hard!
• “I need to release not just one single application, but multiple
applications to multiple platforms or clouds.”
• “I need to control and track the exact release payload and version,
deployed to any cloud/any environment.”
• “I have to support traditional releases side by side with DevOps
Initiatives that have much faster release cycles.”
• “I need top down visibility and alerting so I don’t have to dig around to
find out how my release is doing, where it’s stuck, or who it’s waiting
for.”

1Self-Service
Enable Self-Service
On-demand access to environments, resources, and tools
• What does Self-Service mean in the context of
cloud and release? How are businesses leveraging?
• Best Practices for Release Pipeline
▪ Granular and loosely coupled enables self-
service
▪ Give Developers and Testers Keys to the Car
▪ Control and manage access more effectively to
better support governance & auditability

2Broad Access
Broad Access
Multi-cloud, multi-platform, common experience
• What does Broad Access mean in the context of
cloud and release? How are businesses leveraging?
▪ Go model based; decouple applications,
environments, and target infrastructure
▪ Enable system architecture thinking
▪ Get your databases intimately involved in the
pipeline

3Resource Pooling
Pooling Resources
Maximize utilization of resources
• What does Resource Pooling mean in the context of
cloud? How are businesses leveraging?
▪ Whenever possible, enable dynamic provisioning
of pre-prod environments
▪ Allow scheduling and reserving of static
resources to minimize blocking
▪ Ensure environment configuration consistency
and repeatability to reduce “fear based hording”

4Resource Elasticity
Elasticity
Speed and Scale.
• What does Resource Elasticity mean in the context
of cloud? How are businesses leveraging?
▪ Scaling out build, test, and CI jobs
▪ Leverage cloud for dynamic pre-production
environments
▪ Shifting left – provision production like
environments sooner!

5Measured Service
Measured Service
Feedback, Optimize, Eliminate Bottlenecks.
• What does Measured Service mean in the context of
cloud? How are businesses leveraging?
▪ Enable visibility from code check-in to production
deploy!
▪ Use cloud APIs to track and optimize pre-
production environments across platforms
▪ Enable more frequent deployments to DEV and
QA environments
▪ Measure all aspects of the pipeline! Identify and
eliminate bottlenecks

COMMIT PIPELINE [N]
DEV BUILD TEST
COMMIT PIPELINE [1]
DEV BUILD TEST
RELEASE PIPELINE [“N”]
INTEGRATION PRE-PROD PROD
Provision
Configure
Smoke, Other Tests
. . .
OPTIONAL ACCEPTANCE
Deploy (1…N)
Provision
Configure
Smoke, Other Tests
. . .
OPTIONAL APPROVAL
Deploy (1…N)
OPTIONAL ACCEPTANCE
Pipeline Orchestration
Environment Management
Build/Test Automation
Cloud Resource Management
Deployment Automation
Application Release Orchestration
Build
Unit / Other Tests
. . .
Publish Artifact
OPTIONAL APPROVAL
Provision
Configure
Functional, Other Tests
. . .
OPTIONAL APPROVAL
De-provision
Deploy
OPTIONAL ACCEPTANCE
Provision
Configure
Smoke, Other Tests
. . .
De-provision
Deploy (1…N)
OPTIONAL ACCEPTANCE
OPTIONAL APPROVALCloud Helps Here!
Your Pipeline in a Cloud & Cloud-Native Era

Example Pipeline
Automated or Manual
Approval Gates

Closing Thoughts on 5 Keys to Doing Cloud Right
• Keys Are Critical to Success. It’s not enough to just ”move to the
cloud”! Doing Cloud Right is both an opportunity and a challenge
• Start fast and adapt. Give stakeholders access to resources they
need ASAP. Pipeline framework needs to support legacy and cloud-
native as you transition.
• Don’t Forget Control! Make sure your release platform provides
flexible governance so the kids don’t crash the car.
• Cloud demands visibility – focus on centralized system visibility to
integrating data from all your cloud deployment and monitoring
tools.
• Scale and Speed – moving to cloud will demand more agility and
scale from your pipeline and release process.

Thank You
Telecom/Networking
Other Systems
ISV, Internet
& Entertainment
Heavy Industry
Financial
Services
Automotive Medical Devices
Semiconductor
Aerospace /
Defense
Mobile Devices
Q&A

Doing Cloud Right! Five Keys to Becoming an Elite DevOps Performer

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Doing Cloud Right! Five Keys to Becoming an Elite DevOps Performer

Similar to Doing Cloud Right! Five Keys to Becoming an Elite DevOps Performer (20)

More from DevOps.com

More from DevOps.com (20)

Recently uploaded

Recently uploaded (20)

Doing Cloud Right! Five Keys to Becoming an Elite DevOps Performer