DevOps Without OpsByBob Aiello-May 1, 2014Over the last few months, I have had a number of opportunities to meet with technology professionals to discuss emerging DevOps best practices. Very often I meet people who tell me that they are in charge of DevOps. These discussions usually focus on scripting automated application build, package and deployment as well as building and provisioning servers using deployment frameworks such as Puppet or Chef. DevOps is taking the industry by storm and I see many firms embracing DevOps. But frankly, I am troubled by a trend that I see in which DevOps is being driven by the development professionals without sufficient representation from the operations team. Too often, this is because Ops does not have resources who possess sufficient technical expertise to really participate in the technical discussions. So when I meet with folks who say that they are in charge of DevOps then I usually ask who else is represented at the table.There are many stakeholders who should be at the table starting of course starting with development but also including operations, QA, testing and security. In future posts, I will describe how DevOps should be viewed within the context of Application Lifecycle Methodology. But for now, let me just ask the question - if you are involved with DevOps - is Ops at the table? If not, they should be. Drop me a line and tell how you are approaching including all of the essential stakeholders who should be participating in the journey to DevOps. Bob Aiello, Technical Editor CM Crossroads
