DevOps – A gentle introduction – The value stream



DevOps – A gentle introduction – The value stream

0 0


deveops-presentation

A revealjs based presentation on DevOps

On Github aulme / deveops-presentation

DevOps

A gentle introduction

Agenda

  • What is DevOps?
  • Problems
  • Solutions

What is DevOps NOT

  • It's not a person
  • It's not a team
  • It's not a technology

So what is it?

  • A culture
  • Devs, Ops, BAs... working together
  • Because we're all on the same side.

Two big problems

  • Long waits
  • Unreliability

The value stream

Here's one for software

Given
wait for analysis: 3 weeks
analysis: 1 week

wait for development: 4 weeks
development: 2 weeks

wait for deployment: 4 weeks
deployment: 1 day

Then
Total Cycle Time= 14w 1d
Process Cycle efficiency = 3w + 1d / 14w 1d = 22%

78% time is spent waiting

Reliability

  • Losses
  • Low trust
  • Fire fighting -> longer queues

The tension

More change -> more instability Less change -> longer queues

Essentials

  • Break down silos
  • Be responsible for delivery
  • Be responsible for stability
  • Be responsible for business success

Our tactics

Maximise flow Create Repeatability Improve Reliability

Maximise flow

  • Reduce waste
  • Minimise Work In Progress
  • Use smaller batches

Create repeatability

  • Systematize tribal knowledge
  • Automate repetitive tasks
  • Infrastructure as code

Infrastructure as code

aka use sane development methods for infrastructure

  • Readability
  • Testing
  • Refactoring

Improve Reliability

  • Test infra on localhost
  • No surprises in PROD
  • Don't rely on humans

The Phoenix Project

A Novel about IT, DevOps, and Helping Your Business Win

Questions?

DevOps A gentle introduction