5 Ways to Tell if Your DevOps Relationship is Failing You

By Derek Neighbors on September 19, 2012

Here are five smells seen in organizations that are not fully cross functional and are trying to simulate cross functionality with some variation of “DevOps”.

  1. The development team doesn’t have a fully local development stack on their machines/pairing stations.
  2. Someone other than the development team deploys the software. (The exception being an automated continuous deployment created/owned by the development team)
  3. Someone other than the development team owns the build/continuous integration process (or you don’t have one at all)
  4. The development team can’t create/deploy a simulated production environment for any version of the software with data in under 60 minutes.
  5. The deployment process is not fully automated with the ability to automatically rollback.

The above definition of “development team” is the team writing the application.

Further Reading

Cover of The Phoenix Project

The Phoenix Project

by Gene Kim, Kevin Behr, and George Spafford

A novel about IT, DevOps, and helping your business win by illustrating the patterns of successful DevOps transformat...

Cover of Continuous Delivery

Continuous Delivery

by Jez Humble and David Farley

Reliable software releases through build, test, and deployment automation - a foundational text on implementing effec...

Cover of The DevOps Handbook

The DevOps Handbook

by Gene Kim, Jez Humble, Patrick Debois, and John Willis

How to create world-class agility, reliability, and security in technology organizations through proven technical pra...

Cover of Accelerate

Accelerate

by Nicole Forsgren, Jez Humble, and Gene Kim

The science behind DevOps: building and scaling high-performing technology organizations with research-backed practices.

Cover of Site Reliability Engineering

Site Reliability Engineering

by Betsy Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy

How Google runs production systems, with principles that support effective DevOps collaboration and automation.