There are generous resources for DevOps — online periodicals, trade show, and opinions galore. In November of this twelvemonth in Florida, one more was added to the list — the DevOps East conference. However, the show proved to me that put the label DevOps on something says rattling little. What matters is what people are actually perform in the growing environment.

DevOps Eastis component of a mix of events put on by TechWell. It combines the Agile Development Conference, DevOps East, and the Better Software Conference into one larger event. It had a registration of around 600 folks, most of which come from Agile and quality self-confidence background.

The DevOps aspect of the show resulted largely in an independent track of courses, and an overarching theme. But quality assurance undercurrent dominated all conversations. I was surprised by a few elements of the show that did not fit the typical DevOps event.

First and foremost, I try the word Docker formerly (and it was when I said it). At an average DevOps event, 60 % or more of conversations are about Containers and Docker. And none of the seller in the Expo Hall be vendors you would find at the larger DevOps specific events. This was an gratifying change, because several tools (like a alteration management tool) could have a positive impingement in a DevOps ecosystem of tools where the only thing that subject is release.

For the typical attendee, the DevOps concepts around culture and principles are annoying and/or non-existent. That someone ’ s definition of DevOps is tactical. It is the thing that IT team members do and usually involves some form of automated instrumentation with tools like Puppet and Chef. This neglects the broader (and in my opinion) more important definition of DevOps, which describes the movement. The movement includes citizenry, processes, and tools — not only tools. It is not something that you do, or complete. It is a journey and a driving principle.

This is so hard to accept, in constituent, because principles are not easy to mensurate or action. As shortly as you start dealing with people, things get messy. At the case, I regularly heard from those who were enthusiastic about DevOps and just want to cognize how to get started — and how to convince their squad of its meritoriousness.

The event held a session titled & quot;Creating Culture of Quality & quot;, which included a give-and-take evangelizing the importance of quality — not exactly on the application, but also efficiency. And & quot;Benefiting from Conflict: Building Antifragile Relationships and Teams& quot; make the case that teams can ’ t be afraid of conflict. If change is needed or wait, then conflict should be anticipate.

In my own session, I cover the nuances of Continuous Integration (CI), and explained that it is a must on the path to DevOps. I suggest at the fact that environments that have not yet adopted CI can leverage it as a quick win, and make a “ Code Cafe ” to encourage best quislingism and communication.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Another sessionthat truly caught my ear was a keynote on the matter of culture and changes in team dynamics by Elisabeth Hendrickson from Pivotal software. She focused on the tale of transitioning her squad to faster, smaller iterations. A few great one-liners she had:

“ If you are talking about what is going easily in standups, you are waste time. ”

“ QA is about diplomacy. ”

“ Test rooms are not still — they feature to be curated. ”

All of her points were potent. The last point is something I have seen often, where test suites are allowed to go dusty. In some respects I see this as a quantification of technical debt. However, her first two points included the cultural elements of DevOps in a powerful way.

She had one trick up her arm that I really liked, and that was a game where she demo, via sticky notes with a completed set of didactics, what happens to releases when teams are sequester and not allowed to talk, and then what happens when they are.

I feature a problem with the over-simplification of culture and hierarchy modification needed to modernize teams. It isn ’ t as easygoing as playing a game for some organization. And ofttimes it ’ s “ above pay course ” for those who want the change. No matter how much you see the benefit, there is an deduction you may have to take on some uncomfortable challenge, like approaching your boss & # x27; s boss with a new enterprisingness and its welfare. I ’ ve found that some organizations, afford their current culture, are simply not ready for DevOps, and may ne'er be. For individuals ready for alteration in an establishment that won ’ t, I suggest finding a new job.

The display was a good one — but I believe in terms of DevOps, it lacked some of the more in-depth and matured effectuation that you would find in the more entrenched DevOps case.

The current QA direction is strong. It ’ s one of the most important constituent to hold a modern delivery concatenation together. But this mindset, along with the implied animosity among developers and IT, give the job in many agency.

If you can, I would suggest see the show next year, but not for DevOps. Attend to learn about how modern Agile shops are taking the succeeding step in improving communication, and on-boarding even best automation techniques.

Chris Riley is a technologist who has expend 12 years helping organizations transition from traditional development practices to a mod set of culture, processes and tooling. In addition to be a research analyst, he is an O ’ Reilly author, regular speaker, and subject topic expert in the areas of DevOps strategy and culture. Chris believes the biggest challenges faced in the tech marketplace are not tools, but rather citizenry and planning.

Products

Global instrument

Set up and mix

Resources

Company