Group items tagged

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

In a fit of rage caused by reading yet another email in which one of our customers proposed creating a "devops team" so as to "implement" devops, I tweeted that "THERE IS NO SUCH THING AS A DEVOPS TEAM." Like all slogans, there's plenty of heat to go with the light, so here's the scoop [...]

The DevOps team is "a growing group of people practicing a new way of combining development and system administration for more speed, quality, revenues and fun."

A recent study of Dev and Ops professionals in large enterprises found that those with the least mature DevOps implementations were seeing the most success. While that sounds like a paradox, it's the approach the teams took that matters.

This months talk from DevOps.Net's James Betteley, gives us an experience report on how easy it is to get it wrong when key individuals don't get "on message". What's interesting is the differences in the behaviour and the language used by the teams who don't get it compared to the teams that do.

An excellent piece on leadership, mentoring and the soft skills required to help build a high functioning devops team.

Job titles are important because they describe what we do, which shapes our identity and guides our activity. It's important that job titles are rational and make sense. If they don't, it causes confusion and stress for individuals, teams and organizations. This is why I have a problem with using the term "DevOps" in job titles. This is becoming more and more prevalent in our industry, mainly for self- promotional and recruiting reasons. DevOps is hot… and therefore marketable.

DevOps Days has celebrated 5 years since the initial conference in Ghent in 2009. With events in Helsinki, Vancouver and Tel Aviv just in the month of November, the DevOps Days series has taken place across multiple cities all over the world in these 5 years. InfoQ talked to Patrick Debois and Kris Buytaert, part of the team that organized the first event 5 years ago.

Arrested DevOps is hosted by Matt Stratton, Trevor Hess, and Bridget Kromhout. ADO is the podcast that helps you achieve understanding, develop good practices, and operate your team and business for maximum DevOps awesomeness.