Skip to content

Instantly share code, notes, and snippets.

@emaldonadot

emaldonadot/Devops Leading Change.md

Last active October 2, 2019 19:15
Show Gist options
  • Save emaldonadot/2c546c3eed0e199e2dfa4d0490e18079 to your computer and use it in GitHub Desktop.
Save emaldonadot/2c546c3eed0e199e2dfa4d0490e18079 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Devops Leading Change.md

Culture

  • Culture eats Transformation for lunch
  • Safety First Culture

Focus on:

  • Developers: Add, Update or Remove code quicly in response to business needs
  • Testes: Perpetual testing using automated tests to get confidence in what is being released.
  • Operations: Deploy and Support multiple versions of the same application
  • Business Team: Specify requiremments in a manner that supports incremental delivery and provdes ra[pid turnaround times to development teams and indicate whether the functionality which was been delivered meets their requiremnts (or not).

Issues are expected

  • Focus on whay rather than who. Put automated solutions to prevent recurrance

Create a DevOps Manifiesto

  • Optimized: We optimize end to end. No local-only optimization.
  • Inner Source: All of our code is Inner Source. Our work is visible.
  • Scientific: We formulate hypotheses; validate them with experience and data, continuously testing.
  • APIs: Resources are controlled by APIs. Everything as code (version control, peer reviewed, automatically tested).
  • Pipelines: All our changes go through our continuous delivery pipelines: application, compute, storage, DB, network, OS. No alternative.
  • Teams: Integrated, empowered, self organizing teams.
  • Trust: We value trust and responsibility. But we verify – through the CI/CD pipeline.

Another good example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment