Getting quality software into production quickly and efficiently is a major priority for organizations of all types. Yet many find that development teams’ focus on “innovation and experimentation” conflicts with Ops’ mandate to mitigate risk and increase predictability. This cultural and organizational mismatch puts transformation success at risk, and generates a constant state of "release anxiety." Join Gene Kim, Electric Cloud advisor, researcher and co-author of several DevOps books, including the “Phoenix Project,” and Anders Wallgren, Electric Cloud CTO, as they share top lessons learned from large organizations and concrete tips for bridging the gap between Dev and Ops. Learn how you can increase delivery velocity, while also improving quality, security and auditability at large-scale organizations. During this discussion, you will learn: The hidden downside of “two-pizza teams” Patterns for embracing shared automation and metrics to facilitate collaboration between Biz, Dev and Ops Best practices for self-service pipelines to enable Devs and Ops to move faster and easily adopt new technology Patterns for incorporating InfoSec into DevOps And more

1. © Electric Cloud | electric-cloud.com
Bridging the Gap Between Dev + Ops
Eliminating Release Anxiety

2. © Electric Cloud | electric-cloud.com
Speakers
Gene Kim
Author, CTO,
Researcher, Electric
Cloud Advisor
@realgenekim
Anders Wallgren
CTO
Electric Cloud
@anders_wallgren
/ @electriccloud - #ecwebinar

3. © Electric Cloud | electric-cloud.com
SOFTWARE IS EATING THE WORLD.
Marc Andreesen, 2011
#finserv #iot #saas #services #media #transportation #more…

4. © Electric Cloud | electric-cloud.com
Digital Innovation Drives Market Capitalization

5. © Electric Cloud | electric-cloud.com
Are we all pulling in the same direction?
Create!
Innovate
Maintain!
Scale
Adopt / test new technologies
Track Approvals
Secure
Enforce “standards”
Experiment
Move fast
Meet SLAs
Make it repeatable
DEV
“Change is
status quo”
OPS
“Status quo is
status quo”Refactor and simplify
Manage change
Ensure Performance
Use best tool for each job
Different goals, skill sets,
culture, org design

6. © Electric Cloud | electric-cloud.com
DEV THROUGHPUT OVERWHELM OPS,
CREATING RELEASE ANXIETY

7. © Electric Cloud | electric-cloud.com
“What is DevOps?”
CULTURE | AUTOMATION | MEASUREMENT | SHARING
A set of practices incorporating Lean, Agile and other concepts in
order to improve software delivery capabilities.
DevOps teams place an emphasis on:
Shared Visibility
Dev, QA, Ops,
LOB, HR, Finance,
partners...
Shared Control
Ops and Dev
methods and tech
Shared Services
Disposable, on-
demand resources
and services
Shared Goals
Working together
to deliver VALUE

8. © Electric Cloud | electric-cloud.com
Converging
on the
Value Stream
1Bridging
the gap:

9. © Electric Cloud | electric-cloud.com
Value Stream: Understanding the Path To Production

10. © Electric Cloud | electric-cloud.com
Modeling the Value Stream: Release Pipelines
• Translate sticky-notes/whiteboard into
a Release Pipeline – it becomes an
“executable” Value Stream.
• Tribal knowledge becomes documented
and actionable.
• Everyone converges on this model as a
shared artifact for collaboration,
control and visibility across the entire
process.

11. © Electric Cloud | electric-cloud.com
Considerations for Pipeline Modeling
• Model everything for consistency and
reusability
o Separate / “abstract away” Application
components from Environment/Config,
processes and point tools
o Use parameters and shared components
o Automate approval gates
o Enable self-service consumption (more later!)
• Pipeline as Code / Pipeline as a Product
o Collaborate: version in SCM, test, refactor,
incrementally improve over time
• Allow easy access according to needs
o Eg, DSL, CLI, APIs and GUI

12. © Electric Cloud | electric-cloud.com
Example of Release Pipeline
Automated or Manual
Approval Gates

13. © Electric Cloud | electric-cloud.com
Gene: Tisson Matthew, “Making Of Amazon PrimeNow”
• Highly autonomous teams
can make it difficult to do
enterprise-level
initiatives
• One of my favorite stories
from DevOps Enterprise

14. © Electric Cloud | electric-cloud.com
Pipeline Metrics: How is the Release doing?
Pipeline Metrics:
How is the Release doing?
2Bridging
the gap:

15. © Electric Cloud | electric-cloud.com
Considerations for Pipeline Tracking
• Automate collection of data from point tools,
environments, and pipeline jobs; no ETL
o Complete visibility across everything yields faster and
better decision-making.
o Use historical data from multiple releases to identify trends
and risk
• Tailor dashboards for each stakeholder (eg, environments
vs. application health and status)
o Drill-down to task level for troubleshooting or
optimization
o Shared visibility improves collaboration and alignment
• Automate auditing and compliance checks for pipeline
approvals and promotions
• Consolidate tracking of hybrid environments,
microservices, resources, deployed application versions,
release plans vs. actuals, etc

16. © Electric Cloud | electric-cloud.com
Pipeline & Architecture Characteristics
…make large scale changes to the design of its system without the permission of
someone outside the team, or depending on other teams
...complete its work without fine-grained communication and coordination with people
outside the team
...deploy and release its product or service on demand, independently of other
services the product or service depends upon
...do most of its testing on demand, without requiring an integrated test environment
...perform deployments during normal business hours with negligible downtime
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report

17. © Electric Cloud | electric-cloud.com
The Value Of Platforms
Enable developer productivity
• Self-service
• On-demand
• Immediacy and fast feedback
• Focus and flow
• Joy
Monitoring, deployment, environment creation, security
scans, orchestration…

18. © Electric Cloud | electric-cloud.com
Pipelines-as-a-Service
3Bridging
the gap:

19. © Electric Cloud | electric-cloud.com
Benefits of a Self-Service Model
Reusable components delivered on-demand
enables and enforces consistency
• Start fast and adapt quickly
o Rapidly onboard new teams and applications (reuse is
faster than starting from scratch!)
o Easily adapt the pipeline to support new use cases or
tooling (don’t re-invent the wheel)
• Enable Developers to Get Stuff Done!
o Provide on-demand access: from environment provisioning
to security checks and more!
o Help developers “do the right thing” at speed!
• Ensure fidelity and compliance
o Ensure consistency of environments and processes
o Make security and compliance the path of least resistance

20. © Electric Cloud | electric-cloud.com
Considerations for Pipelines-as-a-Service
• Automate the most common stuff first
o Provisioning and deployment; Test automation
o Security tests/anomaly/drift detection to identify
vulnerabilities and bypassed processes
• Provide access to on-demand components via GUI,
CLI, or code
• “Wrap” legacy scripts as reusable component to they
can be orchestrated consistently
• Parameterize input to allow for reuse across artifact
versions, environment configs, other components
• Train teams how to take advantage, and how to give
feedback.
o Enhance your self-service components over time

21. © Electric Cloud | electric-cloud.com
DevOps Enterprise in London: June 25-26
• Spanning the business / technology divide
• Verizon Enterprise
• Nike EMEA
• Capital One
• KeyBank
• Experience reports, repeat experience reports, subject
matter experts, next-generation Ops and infrastructure

22. © Electric Cloud | electric-cloud.com
Post-DOES: Hands-on Workshops
*Also being held in after DOESUS, Las Vegas

23. © Electric Cloud | electric-cloud.com
1. Map and Model the Value Stream as a pipeline
2. Automatically track pipeline performance
3. Make that pipeline available as-a-service
Bridging the Gap: Scaling DevOps across the Org

24. © Electric Cloud | electric-cloud.com
Q&A