Inspiring approaches to Continuous Delivery & DevOps
The Continuous Delivery and DevOps Conference took place in Stockholm for the third time. It brought together scientists, thought leaders, and practitioners to share their experiences and thoughts on CoDe and DevOps.
At Praqma, we believe in community and knowledge sharing. We take pride in it! So, we were really excited to host our annual Continuous Delivery and DevOps (CoDe) conference in the Venice of Scandinavia, Stockholm! The theme of this year’s talks concerned DevOps data and metrics, quality and stability, culture adaptation, and the importance of people and professional development.
After a light breakfast and a good supply of coffee, Jenny Björneberg and Lars Kruse welcomed the audience and showcased the Praqma vision. They described the ongoing commitment to bringing the software community together through CoDe Alliance. They also touched on CoDe Academy, Praqma’s free training program for university students on the latest industry approaches to CoDe.
The first speaker was Nicole Forsgren from DevOps Research and Assessment (DORA). After checking the early morning coffee levels in the audience (were some a little sleepy from the previous evening’s meet-up?), Nicole inspired everyone with a host of metrics and statistics showing the impact DevOps makes on businesses. These metrics were scientifically studied by DORA and published in their 2017 State of DevOps Report where they measured commercial and noncommercial metrics.
The results show that DevOps practices drive dramatic improvements in organizational performance. For example, high performing DevOps teams are more agile (with 46x more frequent deployments) and more stable (with 96x faster time to recover from a downtime). “Continuous Delivery increases software delivery performance leading to increased profitability and also makes our work feel better by decreasing deployment pain and burnout.”
Nicole ended her keynote by emphasizing the importance of workplace culture. By incentivizing and rewarding innovation, businesses can create an environment where their employees can really see their ideas coming to life.
Next on the stage was Henk Kolk who shared his experience of leading the transformation to DevOps at ING, a huge project which involved several reorganizations to increase speed and agility. Henk highlighted how ING moved to an engineer-centric control framework and reduced manual work and wait times. However, Henk concluded that this move also created a need for more staff training and human development.
After a short break the conference split into two parallel sessions. Anders Lundsgaard talked about Scania’s connected services evolution from spaghetti code to monolith applications before adopting microservices. As part of this evolution they had to find a way to “walk through the walls” between the Dev and Ops teams. So, they got their feature teams and support teams to share responsibilities which removed bottlenecks and waiting times.
Next on the stage was Mieke Deenen from the Dutch public employment service (UWV). Mieke described the journey of UWV’s transformation from being a process-oriented organization to an agile one. The process was far from smooth. When the first attempts failed and UWV suffered a major outage the UWV team’s confidence in agile dropped. To overcome this, Mieke and her team had to find the balance between the old world and the new DevOps world to gradually rebuild confidence. She concluded her experience by saying: “If you want to start with DevOps, start with creating a team of motivated individuals… be persistent, build bridges, create trust and keep learning and improving.”
Ryan Sheldrake from Sonatype took the stage to warn that there is a single security expert for every 100 developers out there. In the DevOps landscape open source tools and libraries are particularly popular. However, as Ryan demonstrated, open source software comes with lots of components which we don’t have any control over. “We use open source software to be able to deploy faster and faster and faster. That brings in all the vulnerabilities.” He concluded: “[for secure development] Empower the developers from the start [by informing them about vulnerabilities and best components version], make access to precise quality information easy, keep a complete list of what you use in your application and make security testing fun.”
The third keynote of the day was delivered by James Grenning, founder of Wingman Software and signator of the Agile Manifesto. He argued that technical excellence is badly needed today and that agile teams need to employ engineering practices that support the tight iterative cycles of Agile and Scrum. Further, he added that we need to continuously learn and develop our technical practices to avoid having the “Expert Beginner” developers. James concluded his keynote by reiterating the importance of people as the “third half” of Agile in addition to technical excellence and iterative planning.
The last session gave the audience an opportunity to put questions to a panel consisting of all the speakers who had spoken during the day. One attendee raised the question of whether you can influence an organization’s culture if you are not in a management role. The panel agreed that anyone can definitely influence your organization’s culture regardless of your role, for better and worse, and referred to some examples including the recent incident of the Google employee’s memo about gender inequality.
Another question was about the impact DevOps is having on HR and the way engineers are recruited. The panel agreed that it is no longer important to test a person’s abilities in specific languages/tools! Rather, it is more important to test their ability and willingness to learn. This did not come as a surprise after many of the speakers called for “continuous learning” in their talks.
As the conference came to an end, the clear takeaway was that people matter. Organizations need to empower them by adapting innovative work cultures and supporting them to learn and unlearn continuously.
You can find more information about the conference and the speakers’ slides on the conference website.
What testing steps should you include in your Continuous Delivery pipeline? Don’t just string together existing manual processes - use simple, collaborative tools to design something better!
Pipeline - The Game that Delivers!
A new card game to design Continuous Delivery pipelines
In the Accelerate book, researchers explain several metrics which they have shown will measure the performance of a DevOps organization, and crucially, drive performance of the organization as a whole. I will explain why this is important, using an analogy with your risk of a heart attack.
Winning with DevOps and Reducing Your Risk of a Heart Attack
Clinical Trials and Software Process
Continuous Delivery at Kamstrup
Kamstrup partnered with Praqma on their journey to Continuous Delivery
Cloud Native DevOps at DNT
DNT partnered with Praqma to take their software development cloud native
Jenkins is one of the best adverts for open source and at Praqma we have been using it since the very beginning. We enjoy giving something back to the community by hosting Day of Jenkins, and this year’s event was packed with exciting developments. Read on!
Celebrating Jenkins and open source collaboration
Day of Jenkins [as code] - A summary
Continuous Delivery and DevOps are here to stay and not because they’re being practiced by trendsetting unicorn companies. The fact is science tells us that these approaches work and this year’s conference gave us lots of examples.
Continuous Delivery and DevOps - Not Just For Unicorns
DevOpsDays Copenhagen 2018 was a great success. Inspiring talks and a pleasant community. I had the pleasure of being the host of this event. I decided to kick off the event with a song about DevOps. See the video and lyrics here.
The DevOpsDays Copenhagen 2018 Song
A whole new (DevOps) world
Once again the contributors and major players in the Git ecosystem are gathered. Read along for news, announcements and stories from Git Merge 2018.
Report from Git Merge 2018
Blogging from the Git Merge Conference at MACBA in Barcelona
A developer that pushes their changes and goes on a celebratory walk to the water cooler is done. But, they’re not done done, their changes have yet to be thoroughly tested, added to future release notes, properly peer reviewed and more. These are pains we want to rid the software industry of, and here’s how we do it.
A Continuous Delivery storyline
How we tell the Continuous Delivery story
We strive to continuously improve, so the 8th gathering in our Continuous Delivery Alliance will feature all the good things from the 7th meeting in a slightly evolved format.
CoDe Alliance goes code camp
Continuously improving our format
We had our 7th gathering in the CoDe Alliance a few months ago and have worked to distill and evolve many of the good ideas that came out of our sessions. Our aim is to turn our interesting discussions into tangible projects and running code.
The 7th gathering
What’s next for the CoDe Alliance?
Immutable infrastructure as code reduces inconsistency and makes deployments faster and easier. We can provision immutable infrastructure with Packer & Terraform. Let’s use them to provision Jenkins Windows build slaves.
How to provision Jenkins Windows build slaves using Packer and Terraform
An immutable infrastructure approach
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps