5 Minute DevOps: What is a Production Issue?

https://www.flickr.com/photos/pulpolux/3932292651

Continuous Delivery requires an entirely different mindset from classical artisanal delivery. For example, we always prioritize operations over development. If we cannot deploy something to our production environment, then nothing else matters. Therefore, the first feature to deliver is the ability to deploy to production. We deploy a Minimum Viable Deployable “hello world” UI or service to validate we can. Then we keep adding small changes very frequently to keep validating we can and to get operational feedback on those changes.

Another mindset shift is the definition of “Production”. Our primary product on a product team should always be the pipeline. It needs to always be green and it needs to have all of the quality and compliance gates coded into it to ensure our confidence to release. Only the pipeline defines releasable. If we are not releasable, our highest priority is to become so. The implications of this are incredibly important for teams who supply products and services to product teams to understand.

All of the following should be P1 issues from the perspective of platform teams:

  • The product teams cannot deploy to production due to a production outage.
  • The product teams cannot deploy to production due to instability in the testing/staging environments we manage.
  • The product teams cannot deploy to production because our security tool is generating false positives.
  • The product teams cannot deploy to production because our CI tool is unstable.
  • I cannot deploy to production because my laptop is broken.

All of these are “production impacting issues” because if any of them are true then we cannot safely FIX production when something breaks. We do not downgrade an issue because “that’s only an issue in Staging.” We only downgrade issues that don’t prevent production delivery.

--

--

--

Developer, Value Stream Architect, and DevOps insurgent who optimizes for sleep. All opinions are my own. https://bryanfinster.com

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Blockchain Devblog #3 — How to easy Fix Error 500 on the IC

So you want to develop an IntelliJ plugin

WTF is “this”?

How to create a ASP.NET Core application and containerize with Docker

Creating a Azure API Management Instance using Bicep Lang via Azure DevOps

How we optimized a token pool on a rate limited API

Play with Play: An Introduction to Play Framework

CSS Specificity Explained By Hopelessly Shopping for New Clothes

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Bryan Finster

Bryan Finster

Developer, Value Stream Architect, and DevOps insurgent who optimizes for sleep. All opinions are my own. https://bryanfinster.com

More from Medium

Cloud Computing: Stick to Open Standards

Agile vs. DevOps vs. SRE… it’s not OR, it’s AND !

Observability and Recovery in Production

How we are improving developer experience at QuintoAndar with backstage.io