A devops Engineer is…..

devops is a popular term now a days. Businesses are trying to figure out what it is. Marketers are trying to figure out how to sell it.

there are some real experts out there Nicole Forsgren, Jez Humble, Gene Kim. 

I’ve spent the past year reading all I can get my hands on

Phoenix Project

Devops Handbook

Leading the transformation ( applying Agile and DevOPs principles at scale

Googles SRE book read the free version at this link

Effective DevOPs

Continuous Delivery:Reliable Software Releases through Build, Test, and Deployment Automation

and the list goes on, Still reading these and others.

The organization I work for is no different we’re trying to figure out the new shiny ,like everyone else. Management is being led down the fairy path by vendors and consultants and everyone else hoping to make a buck off devops. I try to contribute and when I’m passionate about something it’s easy to get carried away.  I felt like I needed to give my management my 2 cents.

here they are just a quick executive summary

From: Drew Burt
Sent: Monday, March 27, 2017 11:35 AM
To: Director
Cc: Scrum master
Subject: What does a devops engineer look like?
Importance: High




A Devops engineer does….


  • Understands and uses Agile
    • Principles
      • LEAN
    • Practices
      • SCRUM
      • Kanban
      • XP
    • Methods
    • Philosophies
  • Uses automation to….
    • Reduce Waste
    • Manage WIP
    • Increase efficiency
    • Create consistency
    • (…)
  • Works closely with development partners to…
    • Decrese “Shadow IT”
    • Increase velocity
    • Co-build the release pipeline
    • Create a collaborative rather than adversarial relationship
  • Toolsets
    • Code repositories
      • Git
      • VSTS
    • Scripting languages
      • PowerShell
      • Ruby
      • Python
    • Domain specific languages (DSL)
      • JSON
      • XML HTML
      • Markdown


    •  Continuous Integration (CI) \ Continuous Delivery (CD) Pipeline components
      • Build
      • Configuration Mgmt.
      • Deployment
      • Orchestration
      • (…)
  • Understand that there is no real definition of “Devops Engineer” but there are great examples

A devops engineer uses  code to solve operational problems. High reliance on Automation to increase efficiency and reduce human error.


Time spent should be 50/50  at first Dev / Ops, with that ratio increasing over time to more dev.



  • Better MTTR
  • Relationship between development / operations groups as they come to understand each others prime directives
    • Code Product Release Dev prime directive
    • Stable systems Operations prime directive
  • Better Service level objective (SLO) effective rate.
  • (…)


Devops culture embraces Agile promises


More to come(…)






I’ll leave it here for now

More to come (….)