What does it take to bring about a DevOpsian culture? Business and IT leaders now say they are practicing DevOps, in which the talents and output of their development teams are coordinated to meet the ever-increasing cadence of software updates. Recent surveys show that while a majority of organizations[1] say they are now practicing DevOps, most haven't fully implemented DevOps because they haven't figured out a way to bring it all together.[2] Only about one in five have merged their teams for managing infrastructure, operations and development.
DevOps means transformation across enterprises, versus deploying some shiny new tools or technologies. Sacha Labourey[3], founder and CEO of CloudBees and Jenkins[4] proponent, says larger enterprises are having a difficult time with making DevOps work as expected. Within larger organizations, "it's just harder -- size is in itself is a factor of inertia," he says. "Silos are much stronger.. so even if there a mandate from the top down to changes, it just takes a lot of energy and time to fight all of those headwinds."
I recently had the opportunity to sit down with Labourey at CloudBees' recent JenkinsWorld[5] conference in San Francisco., where he shared his views on DevOps and the movement toward software automation. DevOps proponents need to "think about how they can standardize, normalize, empower, how they can onboard more users onto their strategy," he says. "You have multiple waves of adoption -- learning how to do DevOps, how to get started, and how to make your projects more successful. Another is to offer DevOps as a service. It's a journey, not a switch you can turn on to enable things. There's much more to