Strengthening Alignment and Engagement between Software and Ops - - PowerPoint PPT Presentation

▶
strengthening alignment and engagement between software
SMART_READER_LITE
LIVE PREVIEW

Strengthening Alignment and Engagement between Software and Ops - - PowerPoint PPT Presentation

Jul 07, 2023 147 likes •835 views

Strengthening Alignment and Engagement between Software and Ops Teams README.md Jonathan Lowsley VP of Systems Engineering Dealer Inspire / Cars.com jlowsley@gmail.com "Agile Infrastructure" the root of DevOps DevOps is the

slide-1
SLIDE 1

Strengthening Alignment and Engagement between Software and Ops Teams

slide-2
SLIDE 2

README.md

Jonathan Lowsley

VP of Systems Engineering Dealer Inspire / Cars.com jlowsley@gmail.com

slide-3
SLIDE 3

"Agile Infrastructure"

the root of DevOps

slide-4
SLIDE 4

“

DevOps is the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity.

slide-5
SLIDE 5

DevOps Values

Culture Automation Lean Measurement Sharing

slide-6
SLIDE 6

In Name Only: DevOps as a Buzzword

slide-7
SLIDE 7

Beware: DevOps as a Buzzword

Search Term: "DevOps Engineer"

slide-8
SLIDE 8
slide-9
SLIDE 9

“

"ok ops you do 'the devops', that's an opsy thing to do"

  • devs

"gladly! oh by the way you have to do it too, we'll do it together"

  • ops
slide-10
SLIDE 10

people

Optimize for Impact

process

tools

slide-11
SLIDE 11

DevOps Topologies

What does DevOps look like? What are the most successful organizational patterns?

slide-12
SLIDE 12
slide-13
SLIDE 13
slide-14
SLIDE 14
slide-15
SLIDE 15
slide-16
SLIDE 16
slide-17
SLIDE 17

DevOps and Scrum in 3 Contexts

1. Ops Upstream of Dev Team 2. Ops Downstream of Dev Team 3. Tight Collaboration between Dev and Ops

slide-18
SLIDE 18

Operations Upstream

Interfacing with Ops when Ops is a dependency

slide-19
SLIDE 19

customers stakeholders PO SM dev team dependencies

Ops

slide-20
SLIDE 20

software development

slide-21
SLIDE 21

infrastructure work software development

slide-22
SLIDE 22

Involve Ops Early and Often

slide-23
SLIDE 23

software development infrastructure work

slide-24
SLIDE 24

Make Inroads

develop meaningful relationships

slide-25
SLIDE 25

DDTA

Do Don't Try Avoid

ideas and practices most would agree we should do ideas and practices that are by in large counter productive ideas and practices you may want to try out ideas and practices you may want to avoid

slide-26
SLIDE 26

DDTA

Do Don't Try Avoid

slide-27
SLIDE 27

Operations Downstream

Ops and Security as customers

slide-28
SLIDE 28

customers stakeholders PO SM dev team dependencies

Ops

slide-29
SLIDE 29

Use the Funnel

slide-30
SLIDE 30

“

As a Systems Engineer I want to run a reasonable number of servers to support the application...

slide-31
SLIDE 31

“

As a Security Analyst, I need all stored credit card data to be encrypted, so that

  • ur company can achieve PCI DSS

compliance.

slide-32
SLIDE 32

Other Story Examples

◇ database crashing regularly ◇ excessive logging ◇ unauthenticated endpoints ◇ changes to infrastructure

slide-33
SLIDE 33

DDTA

Do Don't Try Avoid

slide-34
SLIDE 34

Operations Collaboration

Tight integration between Dev Team and Ops

slide-35
SLIDE 35

customers stakeholders PO SM dev team dependencies

Ops

slide-36
SLIDE 36

Working in the Same Repository

◇ use infrastructure tools that have declarative language ◇ infrastructure as code ◇ increase visibility into infrastructure ◇ welcome suggestions (PRs) from people with different skill sets and backgrounds ◇ be a good VCS citizen, use pull requests, work within existing processes and standards

slide-37
SLIDE 37

Tools can be dangerous

slide-38
SLIDE 38

#Dockerfile FROM node:8-alpine RUN apk --no-cache add curl COPY package.json /app/package.json WORKDIR /app ENV SMTP_USER="someone@example.com" ENV SMTP_PASS="M95!e7hUiA613jc043^Y@v7l" RUN npm install nodemon -g RUN yarn install && yarn build ...

slide-39
SLIDE 39

Troubleshoot Together

infrastructure problems software problems unexpected, exotic interactions

  • h my!
slide-40
SLIDE 40

Embedded Ops in Dev Teams

Plan with the Team, Sprint with the Team

slide-41
SLIDE 41
slide-42
SLIDE 42

Planning Poker

◇ expect over and under estimation ◇ meaningful conversations: lead time and complexity ◇ devs learn about product infrastructure ◇

  • ps learn about product software

◇ builds empathy

slide-43
SLIDE 43

DDTA

Do Don't Try Avoid

slide-44
SLIDE 44

Ops Focused User Stories

◇ user stories that involve Ops work ◇ build shared focus ◇ can be written or proposed by any unit: Ops, Devs, PO, Security team, etc. ◇ describe infrastructure needs and changes ◇ tied to customer outcomes ◇ help align to a meaningful purpose ◇ solidify commitment and increase engagement

slide-45
SLIDE 45

“

As a customer, I can connect to the website with the latest and strongest encryption possible, protecting my personal identifying information and privacy.

slide-46
SLIDE 46

DDTA

Do Don't Try Avoid

slide-47
SLIDE 47

Ops in Sprint Review

◇ Ops involved in sprint work == Ops involved in sprint review ◇ breathes meaning into behind the scenes work ◇ facilitates infrastructure awareness

slide-48
SLIDE 48

Demoing Infra Work

◇ avoid details, keep it simple ◇ use visual representations ◇ focus on what changed

slide-49
SLIDE 49
slide-50
SLIDE 50

Before

◇ The Application Load Balancer was using a legacy Transport Layer Security cipher suite with weak encryption, signing, and hashing algorithms ◇ Customers using our website did not have the most secure connections.

slide-51
SLIDE 51
slide-52
SLIDE 52

After

◇ Using an open source Puppet module we were able to deploy new x509 TLS certificates and a more robust TLS cipher suite. ◇ We upgraded and improved the security for the website.

slide-53
SLIDE 53
slide-54
SLIDE 54

“

As the team responsible for running up the AWS bill, we need to ensure our infrastructure is efficient, without compromising customer experience.

slide-55
SLIDE 55
slide-56
SLIDE 56
slide-57
SLIDE 57

$2.37

April - Normalized infrastructure costs per X users per month

18.5%

Reduction in infrastructure spend

$1.93

May - Normalized infrastructure costs per X users per month

slide-58
SLIDE 58

DDTA

Do Don't Try Avoid

slide-59
SLIDE 59

Retrospect Together

◇ share retrospectives ◇ share postmortems ◇ build high-trust and empathetic relationships ◇ feed ideas from devs and ops back into the process

slide-60
SLIDE 60

What About Velocity?

slide-61
SLIDE 61

Measuring Ops in Scrum Success

◇ how do you measure engagement and alignment? ◇ subjective feedback during retrospectives ◇ morale, dev team satisfaction ◇ widening of skills, gaining proficiency ◇ did we meet the sprint goal? ◇ lead time for infrastructure changes ◇ target % of effort spent on technical debt ◇ deployment frequency, deployment success rate ◇ internal business KPIs

slide-62
SLIDE 62

DDTA

Do Don't Try Avoid

slide-63
SLIDE 63

Tinkering Required

◇ Experiment with Ops involvement in Scrum ◇ Dampen negative effects ◇ Amplify positive effects

slide-64
SLIDE 64

Just One Thing

slide-65
SLIDE 65

DDTA

Do Don't Try Avoid

slide-66
SLIDE 66

Thank You!

Please Submit Session Feedback!

jlowsley@gmail.com

slide-67
SLIDE 67
slide-68
SLIDE 68