In my career, DevOps was never a separate organization. It was a role assumed by the code owners. SRE (is it up, is the hardware working, is the network working?) was separate, and had different metrics.
Having separate teams makes it adversarial because both orgs end up reporting into separate hierarchies with independent goals.
Think about the metrics each team is measured on. Who resolves conflicts between them? How high up the org chart is it necessary to go to resolve the conflict? Can one team make different tradeoffs on code quality vs speed from another, or is it company-wide?
It’s not about just a manifesto, at the startup I worked for before getting into consulting 6 years ago - cloud + app dev - it was much more affective for the team who did the work, to create their own IAC based on a standard.
What’s the difference between a “DevOps team” in 2026 than “operations” in 2001?
In my career, DevOps was never a separate organization. It was a role assumed by the code owners. SRE (is it up, is the hardware working, is the network working?) was separate, and had different metrics.
Having separate teams makes it adversarial because both orgs end up reporting into separate hierarchies with independent goals.
Think about the metrics each team is measured on. Who resolves conflicts between them? How high up the org chart is it necessary to go to resolve the conflict? Can one team make different tradeoffs on code quality vs speed from another, or is it company-wide?
If you have a “DevOps team” - they are operations and you aren’t getting any of the benefits of a DevOps mindset
Meh, real life is a bit more complicated than a manifesto.
It’s not about just a manifesto, at the startup I worked for before getting into consulting 6 years ago - cloud + app dev - it was much more affective for the team who did the work, to create their own IAC based on a standard.
What’s the difference between a “DevOps team” in 2026 than “operations” in 2001?
3 replies →