point
Menu
Browse by year:

THE DEVOPS CULTURE CHANGE GOES WAY BEYOND IT

Raman Sapra, Executive Director and Global Head, Digital Business Services, Dell
Tuesday, August 30, 2016
Raman Sapra, Executive Director and Global Head, Digital Business Services, Dell
DevOps got its name from its inclusion of IT Operations participants on application development teams.

That's unfortunate, because Dev + Ops is not only what's least interesting about DevOps, it's also its most transient characteristic: Companies like Pivotal, RedHat and Chef are providing so much automation for provisioning, integration, isolation, and deployment, that Operations' role in DevOps is shrinking on a daily basis.

What the name does hint at is that at its core DevOps is not about processes, techniques, or tools. Talk to anyone who has been through the DevOps transformation and you will hear the same thing: Before it is anything else, DevOps is a change in culture.

For those who have been through it, this change in culture is often so permeating that articulating just what it means can be difficult.

Start with a definition. While anthropologists have several definitions of culture, and consultants use the term in several different ways, in the end culture means, "how we do things around here." It is the shared set of hidden assumptions, unwritten rules, and attitude about things that gives the word "we" some bite.


Share on Twitter
Share on LinkedIn
Share on facebook