PART 1:

DEVOPS Philosophy, Mindset & Culture

Over Processes and Tools.
Over Following a Plan.
Over Contract Negotiation.
Over Comprehensive Documentation.
 Business Agility Journey
Enterprise Business Agility Journey
DEVOPS & CI/CD Pipeline
 History of DevOps
Patrick Debois Phoenix
starts assessing CAMS acronym,
1st DevOps Days Damon Project
IT value chain Agile conference (Gene
Edwards
SysAdmin (Belgium) & John Willis Kim)
google group Nicole
is launched Forsgren
CI book
(Duvall) DevOps
Cameron Haight shows
1st SRE (Gartner) DevOps positive
DevOps Enterprise ChatOps impacts toDevOps Research
team at “takes off” prediction (GitHub) Enterprises
on social Industry-leading
media vendors introduce
2003 “Enterprise-class”
2001 2007 2008 2009 2010 DevOps2012
2011 tools 2013 2014 2015 2016 2017 2018
2002 NoOps 75% of DevOps for
2005 Mainframes
(Forreste Enterprises
Agile r) use
Infrastructure OpenSource toolsets DevOps in
rip up the legacy some form
Agile playbook 1st release (Gartner) DevOps
CM Agile Skills
1st State of
DevOps Association
1st DOES
Report Summit
Agile Andrew Clay Schafer Continuous Etsy – 50
Manifesto meets w/Patrick Delivery deploys/day,
Debois on Agile Book
Ops/Admin Allspaw & Hammond (Humble & Amazon DevOps
10+ deploys per day Farley) deploys Handbook
DevOps: an Agile Perspective – Agile
every 11sec
Brad Appleton 10
Day Chicago 2018
 Patrick Andrew
DuBois Schafer
Gene Kim Jez Humble

Jesse Damon
Robbins Edwards

DevOps
John
Key John Willis
Allspaw
Thinkers
The Convergence of DevOps Movement

● THE LEAN MOVEMENT.

● THE AGILE MANIFESTO.
● THE CONTINUOUS DELIVERY MOVEMENT.
● TOYOTA KATA.
● The SRE Movement.
The Convergence of DevOps Movement
➢ Continuous Delivery, CI/CD pipeline.
➢ Lean Enterprise, Implementing Lean Software
Development.
➢ DevOps Software Architect’s Perspective, Loosely-
coupled Architecture, Microservices.
➢ Cloud Native Architecture, Container, Kubernetes,
Infrastructure as code, Serverless.
➢ Site Reliability Engineering, Platform Engineering,
Chaos Engineering.
 DevOps Myths
● Myth—DevOps is Only for Startups.
● Myth—DevOps Replaces Agile.
● Myth—DevOps is incompatible with ITIL.
● Myth—DevOps is Incompatible with IS & Compliance.
● Myth—DevOps Means Eliminating IT Operations, or “NoOps”.
● Myth—DevOps is Just “Infrastructure as Code” or Automation.
● Myth—DevOps is Only for Open Source Software.
● Myth—DevOps is Only a toolchain.
● Myth—DevOps is Only a separate team.
● Myth: Good, Fast, Cheap Trade-off.
CI/CD pipeline Cloud Native Microservices
Container
Agile Kubernetes
Infrastructure as Code
ALC Serverless

Artifact
Chaos Engineering
Site Reliability Engineering
Trunk-based development Platform Engineering
“Servers are Cattles NOT Pets.”
David J. Andersen, author of Kanban
“The small changes
people make to
improve things over
time can generate large
results” (Kaizen says)

“Its not how much

you deliver, its how
little” (Jez Humble)
24 “Features in a Ship the whole
Box” box!

Very late feedback

@RealGeneKim
 Continuous Innovation and Optimization
1 “Feature at a Time”

Immediate Customer Feedback Optimize Before Deploy

@RealGeneKim
Copyright © 2016 Deliveron Consulting Services
THE ETHICS OF DEVOPS: THERE IS A BETTER WAY
Copyright © 2016 Deliveron Consulting Services
 Comparison of Lifecycles
Design,
Waterfall Definition Analysis Code &
Integration
Build+Test Test Accept Deploy
(phases) Unit-Test

Incremental
(integrations)

Agile
(sprints)

Continuous
Delivery

Continuous
Deployment

Brad Appleton DevOps: an Agile Perspective – Agile Day Chicago 2018 32

 Software Engineering vs Civil Engineering
THE MANUFACTURING vs TECHNOLOGY VALUE STREAM
 THE MANUFACTURING vs TECHNOLOGY VALUE STREAM

Manufacturing Value Stream Technology Value Stream

❑ The sequence of activities an organization ❑ Same principle and pattern for
undertakes to deliver upon. fast flow.
❑ The input is customer order. ❑ the input is the formulation of
❑ The sequence of activities required to a business objective, concept,
design, produce, and deliver a good or
idea, or hypothesis, go into
service to a customer, including the dual
flows of information and material.
backlog.
❑ Value stream is often easy to see and ❑ A process required to convert a
observe. business hypothesis into a
❑ fast and predictable lead times, focus on technology enable service that
creating a smooth and even flow of work, delivers value to the customer.
using techniques such as: (small batch ❑ value is created only when our
sizes, reducing work in process (WIP), services are running in
preventing rework to ensure defects are production (fast flow +
not passed to downstream work centers, deployment without causing
and constantly optimizing systems
chaos and disruptions).
toward global goals).
 FOCUS ON DEPLOYMENT LEAD TIME
Lead Time Process Time
Clock starts when request is Clock starts when we begin
made and ends when it is work on the customer request.
full filled. This omits the time that the
work is in queue, waiting to be
processed.

The Common Scenario: Deployment Lead Times Requiring Months.

Our DevOps Ideal: Deployment Lead Times of Minutes
Flow Metrics to Measure Delivery of Business Value
Doing it Fast Doing it Right
Copyright © 2016 Deliveron Consulting Services
 THE CORE, CHRONIC CONFLICT

“It’s not my machines, it’s your code”

“It’s not my code, it’s your machines!!”

“name, blame, and shame”

➢DEV comes from the SCHOOL, but OPS come from
the STREET.
➢ With AGILE, programmers and testers became Developers
and with DEVOPS, developers and operations became
DEVOPS.
Copyright © 2016 Deliveron Consulting Services
BusProdDevTestQASecOps

Copyright © 2016 Deliveron Consulting Services

 Movement, culture ,
DEFINITION framework , Model,
Approach
DEVOPS is a cultural and management philosophy that
aims to get every team member to focus on continuous
improvement and value delivery to customers.

DEVOPS is a software delivery approach that removes silos

between existing development and operations teams.

DEVOPS is an approach based on lean and agile principles in

which business owners and the development, operations, and quality
assurance departments collaborate to deliver software in a
continuous manner that enables the business to more quickly seize
market opportunities and reduce the time to include customer
feedback.
 Movement, culture ,
DEFINITION framework , Model,
Approach

DEVOPS is about humans, DevOps is a set of practices and patterns

that turn human capital into high-performance organizational
capital.

DEVOPS is a cultural movement that changes how individuals think

about their work, values the diversity of work done, supports
intentional processes that accelerate the rate by which businesses
realize value, and measures the effect of social and technical change.
It is a way of thinking and a way of working that enables individuals
and organizations to develop and maintain sustainable work
practices.
Accrued work that is “owed” to an IT system. Teams “borrow” against
quality by making sacrifices, taking short cuts, or using workarounds to
meet delivery deadlines. "build now, fix later" mentality.
Also known as design debt or code debt, is the implied cost of future reworking
required when choosing an easy but limited solution instead of a better approach
that could take more time. if technical debt is not repaid, it can accumulate
"interest", making it harder to implement changes.
 The Seven Wastes in software development
(Waste is activities that not add value)

1. Hand offs. The 5 Thieves of Time:

2. Work In Progress. 1. Too much WIP.
3. Over Engineering. 2. Conflicting priorities.
4. Task switching. 3. Unknown dependencies.
5. Delays. 4. Unplanned work.
6. Relearning the process. 5. Neglected work
7. Defects.
Cost of Misaligned Culture:
1. Wasted Time.
2. Wasted Resource.
3. Loss of competitive advantage.
 DevOps All about

● Value Focus On:

● Change. ● People.
● Speed. ● Process.
● Continuous Delivery. ● Tool.
● Continuous Improvement.

FASTER BETTER CHEAPER

 Business Case
● Long Time to Market.
● Conflict, Escalations.
● Always need Top Management Supervision & follow-up.
● Quality & Security Issues.
● Ambiguity, lack of clarity and suddenness.
● Less Outcomes.
● Dissatisfaction.

➢ Struggling: Silos, barriers, Blame, Long TTM, conflict,

team goals, outputs
 TO KNOW ABOUT DEVOPS
Culture Change
Become DevOps Not just Doing DevOps
➢ Think Differently.
➢ Work Differently.
➢ Organize Differently.
➢ Measure Differently.

➢ DevOps works for everyone.

➢ Its not one size fits all. It should vary depending on
what you’re doing, what type of organization and
software applications you use, deploy or manage.
 TO KNOW ABOUT DEVOPS

➢ People Over Process Over Tools.

➢ You Build it, You Own it, You Run it.
➢ One team, One Goal.
➢ KEEP TEAM SIZES SMALL (THE 2PT “TWO-PIZZA
TEAM” RULE).
➢ Empowered cross-functional teams.
 TO KNOW ABOUT DEVOPS

➢ Social Coding. (Public Repository)

➢ Social Coders, Social Metrics.
➢ Pair Programming.
➢ DevOps Proactive Monitoring: Observability instead
of monitoring (Unknown unknowns).
➢ You Can’t monitor Everything.
➢ Blameless Incident Review.
➢ Multiple contributing factors Instead of single root
cause.
➢ Fail fast << Learn Fast
 TO KNOW ABOUT DEVOPS
➢ Speed does Not mean Low Quality.
➢ Low Quality = Slower & more rework
➢ Stability + Speed = Quality
➢ multiple test cycles in multiple environments is NOT
the correct approach to improve Quality
➢ To get Quality + Speed: (Build Quality In & have
Continuous Delivery practices).
➢ Small Batches + frequent Delivery = Improved
feedback & quality
 TO KNOW ABOUT DEVOPS
➢ Shifting from outputs to outcomes.
➢ Progress over Perfection.
➢ Loosely Coupled Architecture.
➢ Starting Small.
➢ Standardize process of prioritization.
➢ Shift Lift.
➢ Making work visible with Value Stream View.
➢ Manage Workload, work in process WIP limits.
 DevOps Model
• The Three Ways
– Systems Thinking Values
in the Agile
– Amplify Feedback Loops Manifesto and Lean Theory of
– Culture of Continual Experimentation Constraints.

• CAMS
– Culture – People > Process > Tools
Focus on People by Creating and maintaining a stable and safe environment where
your people can learn, share, experiment, succeed, and even fail
– Automation – Infrastructure as Code
Reduce the mundane tasks and automate. (the accelerator that help you unluck the
other DevOps benefits
– Measurement – Observability
There must be well defined metrics with incentives.
– Sharing – Collaboration/Feedback/learning Culture.
THE THREE WAYS: THE PRINCIPLES
UNDERPINNING DEVOPS

Flow, System Thinking

Amplify Feedback Loops

Culture of Continual Experimentation & Learning

The “traditional” view of Security

DEV TEST PRE SEC PROD

The “Shift Left” view of Security

SEC

67
DEV TEST PRE PROD
There may be a way to
restore the peace!
Eliminating duplicate
administration, making the ITIL
Processes as lean as possible.
Introducing…

69
 What can Agile/Scrum learn from ITIL?

• Customer focus (reliability)

• Feedback loop (mostly incident
management)
• Uniform process
• Discipline

What can ITIL learn from Agile/Scrum?

• Need for speed
• Customer focus (adding value)
• Limiting WiP
• Feedback loop (what customers
really want)
& DevOps
& ITIL
What they share
• DevOps Core Principles and ITIL 4 Guiding Principles.
• DevOps Values and ITIL 4 Dimensions.
• DevOps’ “Three Ways” and ITIL 4 Service Value System.
• They are both aligned to Lean and Agile, which mostly implies:
– Value Streams (end-to-end) to deliver customer value.
– Value co-creation.
– Continual Improvement.
– Culture & Leadership.
– Optimization, eliminating waste.
– Automation. The Guiding Principles
14

– Work in iterations. 1. Focus on Value

– Visualization. 2. Start Where You Are
3. Progress Iteratively with Feedback
– Team based. 4. Collaborate and Promote Visibility
5. Think and Work Holistically
6. Keep it Simple and Practical
7. Optimize and Automate
DEVOPS Adoption and Transformation
 Hypothesize

DEVOPS Measure
Learn 5

4
Collaborate &…
Architect

Maturity Stabilize
3

2
Synthesize

Assessment Release

Respond
1 Develop

Build

Monitor Test End-To-…

Verify Stage
Deploy

Current Level of
Importance (I) Practice (P) SCORE
(1-5) (1-5) (0-5) GAP Rank
Nine Pillars of DevOps Practice Topics (1=low, 5=critical) (1=not yet, 5=always) 5-(((Ix(5-P))/5)+1) (1-N)

Collaborative Culture Practices 4.29 1.43 1.94 1

Continuous Security Practices 3.88 1.50 2.29 2
Continuous Monitoring Practices 4.00 1.71 2.37 3
Design for DevOps Practices 3.33 1.44 2.63 4
Continuous Delivery/Deployment Practices 3.71 2.00 2.77 5
Elastic Infrastructures Practices 3.89 2.33 2.93 6
Continuous Testing Practices 3.44 2.44 3.24 7
Continuous Integration Practices 3.91 3.27 3.65 8
Collaborative Leadership Practices 3.80 4.40 4.54 9
Your biggest challenge for the
implementation of DevOps?

5%
Information
Issues
50 %
37 %
People Issues
Process
Issues

8%
Technology
Issue
 CONWAY’S LAW
How to Design Our Organization and
Architecture with Conway’s Law in Mind

▪ “organizations which design systems... are

constrained to produce designs which are
copies of the communication structures of these
organizations…. The larger an organization is,
the less flexibility it has and the more
pronounced the phenomenon.”
 ORGANISATIONAL
ARCHETYPES

• Functional Oriented Organization

• Matrix Oriented Organization
• Market Oriented Organization

ENABLE MARKET-ORIENTED TEAMS (“OPTIMIZING

FOR SPEED”)
 Functional Matrix Market Oriented
Organization Organization Organization
• Optimize for expertise, • Mix of Both • Optimize for
division of labor, or responding quickly
reducing cost. to customer needs.
• Tall hierarchical • Flat organizational
organizational structure.
structure. • Adopt DevOps.
• Have Development &
Operations Team
separately.
 So, To get Greater Outcome
• Design Team boundaries in accordance with Conway’s Law.
• Create loosely coupled architectures to enable developer
productivity and safety.
• Keep team sizes small (The two pizza team rule).
• Create shared services to increase developer productivity.
• Embed DevOps engineer into our service teams.
• Assign an DevOps liaison to each service team.
• Integrate OPS into Dev Rituals.
• Invite DevOps to our dev stand-ups and retrospectives.
• Make relevant DevOps work visible on shared KANBAN board.
 DevOps Team Topologies (Matthew Skelton)
Anti-Type A: Anti-Type B: Anti-Type C:
Dev & Ops Silos DevOps Team Silo Dev Don’t Need Ops

Dev Ops Dev DevOps Ops Dev DevOps Ops

Anti-Type D: Anti-Type E: Anti-Type F:
DevOps as Tools Team Rebranded SysAdmin Ops Embedded in Dev Team

Dev DevOps Ops Dev DevOps Ops Dev DevOps Ops

Type 1: Type 2: Type 3: Type 4:

Dev+Ops Fully Shared Ops Ops as IaaS DevOps-as-a-Service
Collaboration

Dev Ops DevOps Dev DevOps Ops Dev DevOps Ops

Type 5: Type 6: Type 7: Type 8:
Temp DevOps Team DevOps Evangelists Team SRE Team (Google Container-Driven
Model)

Dev DevOps Ops Dev DevOps Ops Dev DevOps SREOps Dev DevOps Ops

Brad Appleton 83
MEASURING UP
against other movements

DevOps
shouldn’t be like

Dev Ops
 SRE versus DEVOPS
But… does devOps always implement all of DevOps in
reality?

Dev | Ops (wall of confusion)

DevOps SRE
In practice typically leads to: In practice will hopefully lead to:
• CI/CD pipelines • Higher reliability after code deploy
• Infra-code at least for test environments • Better operability
• DevOps Team • Better life for Ops team
• Better quality engineering (hopefully) • The right balance of speed vs safety
• Start with Changing the Mindset & Culture through
workshops.
• Engineering Capacity Assessment.
• Start Simple
• Start with Green field.
• Start with Version Control.
• START WITH THE MOST SYMPATHETIC AND
INNOVATIVE GROUPS
• Even if we have the highest levels of executive
sponsorship, we will avoid the big bang approach.
• three-step path to enhancing collaboration in our
culture.
• Reduce separate teams in the value chain by
eliminating silos and creating cross-disciplinary
teams,
• use self-service to virtually remove other teams, and
• align goals, and promote collaboration and mutual
support in the remaining teams.
• Embed Ops engineers in your development teams,
assign both teams to be in one chat room, and allow
them to read each other's source code.
Where to start first?
How to implement DevOps culture?

Define
Raise
Standard
awareness
Tools

Define
agile Educate
processes
Raising awareness about importance of
implementing DevOps

DevOps Understanding
DevOps Identify
cost/benefit implementation
seminars impediments
matrix steps
Define Standard Set Of Tools
Standard
Standard release
version Standard management
control deploy tool
tool tool

Standard Standard test

build tools
- pick the tools that work for your organization and processes
- pick the tools that promote collaboration and sharing among your people.
- Don't add on more tools than you need, keep it simple,
- put a high priority on tools being able to integrate with others and
dynamically adapt to a changing environment.
- DevOps Toolchain: For infrastructure as code you should design out your
operational environment first before creating it like how any application
should be built. Don't just grab tools and go. Plan out how you want this all
to fit together.
Define agile processes

Standard development
process

Standard version control

and code review process

Standard test process

Standard release process

Educate

Teach your organization to use tools

and processes that you have defined

Teach your developers to implement

tests

Teach your operations to trust

developers
DevOps
Thank You

DevOpsGuys
DevOps as a Service