Slide 1
Slide 1 text
10 Years of DevOps
~ Are you ready for Change?
Slide 2
Slide 2 text
MOTIVATION FOR CHANGE
Slide 3
Slide 3 text
Why Changes?
• To follow leaders like Google / FB
• New techs are cool, ex: docker, K8s
• Copy competitor
• New competitor in town
• Stay competitive
• Arch. needs to scale out
• Technical debt, arch. modernization
• Throughput, latency, correctness
• Velocity & (Cost) Efficiency
Slide 4
Slide 4 text
Competition - IBM, MS v.s. Google
Slide 5
Slide 5 text
Arch. Scale Out - Uber
Uber: https://stackshare.io/stack-history-timeline-uber-tech-stack-evolution
Slide 6
Slide 6 text
Velocity & Efficiency - Nokia
• Symbian (2010) took a whole 48 hrs to build
• Means 2 days later to find out changes work or not
• Pipeline cadence & feedback cycle are important
• We agree with “The Mythical Man-Month” but that does not
apply to high IT performance org. (ex: Google)
• DevOps helps scale IT productivity
Slide 7
Slide 7 text
Productivity
Slide 8
Slide 8 text
CULTURE & PROCESS
“Culture is how we think, what habits we create and what we
do when we're interacting with each other every day.”
Slide 9
Slide 9 text
From Worst to Best Quality
picture src: https://www.slideserve.com/ivanbritt/nummi-powerpoint-ppt-presentation
story: https://www.slideshare.net/KellyCar/managing-change-lessons-from-the-global-prof-singh
Slide 10
Slide 10 text
Culture Explain
• Amazon
• 3 big ideas: put customer first, invent and be patient.
• Great experience, a legendary kind
• Embrace continuous experience improvements
• Netflix Culture Deck
• Viewed 19,000,000+ times
• “The most important document ever to come out of the
Valley.”
• Freedom & Responsibility
• Great teams keep best talent, big salary
Slide 11
Slide 11 text
Culture for IT Engineering
Psychological safety
• Westrum organizational culture
Learning organization
• Spotify Engineer Culture
Slide 12
Slide 12 text
Good v.s. Excellent
• Ex: Trunk-based development (TBD)
• Practice TBD enables team skills like canary
release, stage rollout, …
Culture for IT Engineering - Conti.
Very very few use trunk-
based development
Elite companies
scale well with it
New unicorns
advertise it
Best-selling books
promote it
Statistic data
prove it
Slide 13
Slide 13 text
WHAT CAN WE DO
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
In DevOps, what to Change for RD?
Slide 16
Slide 16 text
• DevOps focus on developer and operations
• Testing is absence from the the term
• Testing is a pervasive activity throughout development (like the air)
In DevOps, What to Change for QA?
image: Dan Ashby [https://danashby.co.uk/2016/10/19/continuous- testing- in- devops/]
Slide 17
Slide 17 text
In DevOps, What to Change for OPs?
source: CNCF Cloud Native Landscape
Slide 18
Slide 18 text
• Changing might cause failure
• No change is the same risk as changing
• Do it before too late
We are good why still change?
Slide 19
Slide 19 text
Personal Win
Company Competitive
Slide 20
Slide 20 text
• Technical Vision - Embrace changes
• Growing Technical knowledge - Establish “Chapter & Gild”
• Tech Debt Management - Do it early & consciously
• From Local to Global Improvement - Advertise it & contribute to
community
Takeaway
‘We keep improving our culture as we grow.
We try to get better at seeking excellence.’’
~ Netflix culture deck