This document discusses DevOps and its relationship to SAFe. It begins with introductions and defines DevOps. It then discusses key principles of DevOps like culture, automation, lean flow, measurement, and recovery. It outlines the different teams involved in DevOps and how it breaks down silos. The rest of the document discusses how to assess value streams and identify bottlenecks. It also outlines the explore, integrate, deploy, and release dimensions of a continuous delivery pipeline in SAFe. It concludes by providing information on a SAFe DevOps certification course.

1. • Better Together
SAFe and DevOps
Photo by Carsten Schertzer from Santa Cruz, CA, United states [CC BY 2.0 (https://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

2. Bio
• Email: Leland.newsom@yahoo.com
• Twitter: @LelandNewsom
• LinkedIn: https://www.linkedin.com/in/lelandnewsom/
• Slideshare: https://www.slideshare.net/LelandNewsom
• Past roles include:
• Developer
• Manager
• Managing Director
• Technical Director

3. Activity – What Does DevOps Mean to You
• Take 5 min to write a single word or short phrase that defines what DevOps
means to you.
• Keeps stickies with you – we’ll circle back to them shortly.
3

4. 4
Definition DevOps is those set of cultural
norms and technology
practices that enable the fast
flow of planned work from,
among others, development,
through tests into operations
while preserving world class
reliability, operation, and
security.
DevOps is not about what you
do, but what your outcomes
are.

5. 5
DevOps Authors Agree (except about acronyms)
CAMS [John Willis and Damon Edwards]
• Culture, Automation, Measurement,
Sharing
CALMS [Jez Humble]
• Culture, Automation, Lean,
Measurement, Sharing
CALMSS [Forrester/Patrick Debois]
• Culture, Automation, Lean,
Measurement, Sharing, Sourcing
CALMR [Scaled Agile Framework]
• Culture, Automation, Lean,
Measurement, Recovery
✓ DevOps exists to help the business
succeed
✓ The scope is w i d e, beyond Dev and Ops,
but centered on IT
✓ It is directly descended from Agile and
Lean
✓ Culture of collaboration and
experimentation is key
✓ Frequent feedback fuels innovation
✓ Automation helps (certainly)

6. 6
Who are the players and what makes them tick?
Dev Ops
QA
Ops
Security
EA
…
Dev
DevOps breaks down silos and fosters collaboration among teams that typically do not collaborate. This is
crucial to achieve speed and stability, since all these teams play a part in delivering ‘finished’ software to
market.

7. A CALMR approach to DevOps
• Culture Establish a culture of shared responsibility for
development, deployment, and operations.
• Automation Automate the Continuous Delivery Pipeline.
• Lean flow Keep batch sizes small, limit WIP,
and provide extreme visibility.
• Measurement Measure the flow through the pipeline.
Implement full-stack telemetry.
• Recovery Architect and enable low-risk releases.
Establish fast recovery, fast reversion, and fast
fix-forward.

8. DevOps is a Cultural shift
• Adopt a culture of shared
responsibility for development and
deployment
• DevOps requires a tolerance for
failure and rapid recovery, and
rewards risk taking
• Sharing discoveries, practices,
tools, and learning across silos is
encouraged

9. Automate the deployment process
• Automation is a key concept in DevOps
• Automate as much as you can from the
Continuous Delivery Pipeline – fewer
manual steps improves the flow of value
• Build a comprehensive toolchain to help
teams release value more frequently
• Focus on automating healthy processes. If
the underlying process is broken, fix it
before automating it

10. Focus on continuous Lean flow of value
Identify bottlenecks to the flow of
value
Decrease the batch sizes of the work
Manage and reduce queue lengths
Build Quality In
Eliminate wasteful steps in the process
https://www.youtube.com/watch?v=JoLHKSE8sfU

11. Measure everything
• Collect data on business, application,
infrastructure, and client layers
• Collect data about the deployment
pipeline itself
• Maintain different telemetry for
different stakeholders
• Broadcast measurements
• Continuously improve telemetry during
and after problem solving

12. Architect for release-ability and Recovery
• Adopt a stop-the-line mentality
• Plan for and rehearse failures
• Build the environment for both roll-
back and fix-forward
Source: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Kim,
Gene; Humble, Jez; Debois, Patrick; Willis, John

13. Activity – What Does DevOps Mean to You
• Take stickies and place on wall under which CALMR concepts they most
strongly represented.
• Discuss as group (5 min):
–Which CALMR concepts are strongly represented?
–Which ones are under represented?
–Why?
13

14. The DevOps health radar
Continuous Delivery Pipeline – Outer Rings
• 4 Dimensions
• 16 Sub-dimensions
Inner Rings
• Gray Ring – Stake holder objectives
• White ring - DevOps Capabilities
• How IT meets the business objectives
• Example – Improve Time to Market by
developing or improving our Continuous
Deployment capability
© Scaled Agile, Inc.

15. 15
Assessing Your Value Stream
Lead time (LT) – Time from when work was ready after the previous station to
completion
Process time (PT) – Actual value-added work
Percent Complete & Accurate (%C&A) – Percent of work that the next station
could process as-is
PM
accepts
Deploy to
staging
Smoke
test
QA +
UAT
Stage
signoff
PM Team Team Bus +
Team
Bus
WAIT WAIT WAIT WAIT WORKWORKWORKWORK

16. 16
Identifying the Bottlenecks
WAIT WAIT WAIT WORKWORKWORK
WAIT WAIT WAIT WORKWORKWORK
WAIT WAIT WAIT WORKWORKWORK

17. 17
Resolve the Biggest Constraint First

18. Explore dimension
Business objective (The ‘Why’)
• Alignment
IT objective (The ‘How’)
• Continuous Exploration (CE) - the process of
continually exploring the market and user
needs, and defining a Vision, Roadmap, and
set of Features that address those needs.
Sub-dimensions (The ‘What’)
• Hypothesize – hypothesis to be validated
through CD pipeline
• Collaborate & Research – Understand
stakeholder needs
• Architect – for CD and DevOps
• Synthesize – build backlog

19. Integrate dimension
Business objective (The ‘Why’)
• Quality
IT objective (The ‘How’)
• Continuous Integration (CI)
Sub-dimensions (The ‘What’)
• Develop - implement the story
• Build – compile source files into deployable
binaries & verify code functions as developer
intended
• Test end-to-end – validate changes against
acceptance criteria in an integrated prod-like
environment
• Stage – host in prod-grade environment from
which code can be deployed to production

20. Deployment dimension
Business objective (The ‘Why’)
• Time to market
IT objective (The ‘How’)
• Continuous Deployment (CD)
Sub-dimensions (The ‘What’)
• Deploy – into production with high frequency
and low risk
• Verify – they behave as expected before
releasing to end users
• Monitor – Measure system and user behavior
• Respond – proactively detect and resolve prod
issues before they cause business disruption

21. Release dimension
Business objective (The ‘Why’)
• Business value
IT objective (The ‘How’)
• Release on Demand
Sub-dimensions (The ‘What’)
• Release – to customers
• Stabilize – sustain high levels of business
continuity & data protection
• Measure – test hypothesis of business value &
evaluate hypothesis
• Learn – from hypothesis whether to pivot or
persevere as well as how to improve the flow of
value

22. Learn More
22
• http://www.scaledagileframework.com/built-In-quality/
• http://www.scaledagileframework.com/continuous-delivery-pipeline
• http://www.scaledagileframework.com/inspect-and-adapt/
• 2017 State of DevOps Report
–https://puppet.com/resources/whitepaper/state-of-devops-report

23. SAFe SDP Course
• Two-day course provides a comprehensive overview for understanding the DevOps competencies needed to
accelerate time-to-market by improving the flow of value through the Continuous Delivery Pipeline. Attendees will
map the current value stream through their delivery pipeline from idea to cash, and identify practices that will
eliminate bottlenecks to flow.
Key Areas of Competency:
• Describe what DevOps is and why it is important
• Build a culture of shared responsibility across the value stream
• Continuously explore user needs
• Describe architectural considerations for continuous delivery
• Build and integrate the system continuously
• Improve the quality of the system with continuous testing
• Deploy systems to staging and production environments continuously
• Release systems to customers and manage recovery as necessary
• Maintain security by inspecting continuously for vulnerabilities
• Measure the flow through the Continuous Delivery Pipeline
• Support a SAFe DevOps transformation in the enterprise
https://www.scaledagile.com/certification/courses/safe-devops/
SAFe® Authorized Course Attending this course gives
students access to the SAFe DevOps Practitioner exam
and related preparation materials.