DevOps Enterprise Summit

On June 30th and July 1st, the first EU DevOps Enterprise Summit was held in London. The agenda was fully packed with a lot of presentations on implementations of DevOps in all kinds of companies in different industries.
Around 500 persons in the DevOps community gathered these days to share experiences and learn from each other.
So a really vibrant environment that was filled with great ideas. To give you a small glimpse in what was happening I will give you a brief overview of the topics that I thought were the most important ones. I realize that I will miss a lot of important information in this blog. So next time just be there! Or if you were there, feel free to add anything in the comments.

DevOps is maturing

It might have been a buzz-word for a long time. But if anything became apparent this Summit, it is that DevOps is being picked up by all kinds of companies. From Disney to Barclays and from HMRC Tax services to Ticketmaster. And although their starting point and issues to solve may have been very different. They all had great results with DevOps in terms of Cycle Time.

DevOps is about people

Really, it is about the people. Did I mention it is about the people?
This definitely was the most heard phrase during these two days. Everyone that has even made the smallest steps into DevOps realizes that it is about the people. It is a way of working. And it is a way of leading change and your organization as a whole. I have seen a lot of great leaders that not only empower their employees to do great things but also enable them.

Conways Law

A close second in the number of mentions was Conways Law.

“Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.”
— M. Conway

If you apply this to DevOps, the conclusion will be that implementing DevOps will mean changing your organizational structure. You can not overcome the problems that were the result of the organizational structure if you do not change it. Product teams or feature teams are not just virtual layers on the organization. They should be the organization.

It can be done in every organization in every industry

As I mentioned before, a lot of different companies presented their DevOps journey. And although everyone mentioned that their is room for improvement, they also showed great results from the steps already taken.
Baclays went from a test duration of eight days to twenty minutes. Form seven to seventy releases per month. – With no production incidents. HMRC Tax Services tripled their load, quadrupled their releases and decreased the incidents with 80% (getting P1 and P2 totally out of the way).
And the journey takes time. This is not done in a year. It is an ongoing process. Their is not a runbook to implement DevOps. It will be different per organization. And it will be about changing the mindset to keep on improving.

“It will be about changing the mindset to keep on improving.”

How to involve suppliers

And because it is an ongoing journey we realized that we are not done. One of the biggest issues that we all felt at this moment is the way we involve suppliers. Formal contracts are often hard to work with if you want to optimize the complete chain. And a good practice to involve 3rd parties seems to be missing.

So any good ideas on that are more than welcome. Let’s try to tackle this one as a DevOps community as well!

Other relevant DevOps content

devoteam