Every DevOps enthusiast faces the same challenge at some point: you know DevOps works, your team knows it works, but the decision makers want proof. They want a business case. In this talk at ContainerDays 2019, I break down a practical framework for convincing CIOs and managers to fund your DevOps transformation.
You want to do DevOps. Your team wants to do DevOps. Even your CIO wants to do DevOps. But then comes the inevitable question: “What is the business case?” In this five-minute Ignite Talk at DevOpsDays, I share a simple but powerful tool to convince decision makers that DevOps is worth the investment.
Many companies are suffering from a lack of alignment between business and IT, silo thinking, and inefficiencies in product development, while time to market is becoming increasingly important.
The Problem # These companies try to adopt DevOps in their organizations, but unfortunately, sometimes the DevOps approach is misunderstood, wrongly implemented, and it does not scale as expected.
I had the honor of being interviewed by 📈 Matt Warcholinski 💾 from Brainhub in his 𝐏𝐨𝐝𝐜𝐚𝐬𝐭🎙️ on 𝐁𝐞𝐭𝐭𝐞𝐫 𝐓𝐞𝐜𝐡 𝐋𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩.
At The DEVOPS Conference, I presented on a topic that has been at the heart of my work for over two decades: how to architect for continuous delivery. This talk covers the broken value stream I see in most companies, why product thinking matters more than project thinking, the science behind software delivery performance, and how platform engineering enables organizations to scale DevOps through digital factories.
At the State of DevOps in Switzerland 2023 event, I joined Adrian Kosmaczewski from VSHN to present the latest findings on DevOps adoption in the Swiss market. Adrian shared four years of survey data, while I focused on how to successfully scale DevOps through platform engineering and the concept of the digital factory. This event brought together DevOps professionals both on-site and virtually for presentations and a lively panel discussion.
After eleven sessions building a full DevSecOps pipeline with GitHub — covering Software Composition Analysis, License Compliance, SAST, Container Scanning, Secret Detection, DAST, Pull Requests, Scheduled Pipelines, and Vulnerability Management — Patrick Steger and I close the series with our recommendations. What works on GitHub, where the gaps are, and what we would tell anyone setting out to build the same pipeline.
Across ten sessions we wired security checks into a GitHub Actions pipeline that fires on every commit and every Pull Request. That covers code we are actively changing. It does not cover the code that is already running in production while researchers keep finding new CVEs in the libraries it uses. In Part 11 of the GitHub DevSecOps series, Patrick Steger and I add a scheduled workflow that re-scans the production branch — and we run straight into a GitHub limitation worth knowing about up front.
In the previous nine sessions Patrick Steger and I built a GitHub DevSecOps pipeline with build, SCA, License Compliance, SAST, Container Scanning, Secret Detection and DAST. All useful — but only if it actually runs before code lands in main, and only if the merge is blocked when something serious shows up. In Part 10 we wire that gate together with Pull Requests and Branch Protection rules.
We have spent the previous eight sessions adding scanners to our GitHub DevSecOps pipeline — SCA, SAST, container scanning, secret detection, DAST. The scanners now produce a steady stream of findings, and the question is: where do we manage them? In Part 9, Patrick Steger and I look at GitHub’s built-in Vulnerability Management — the Security Tab — and call out what it does well and what is still missing.
Join Eveline Oehrlich and Romano Roth, to discuss whether DevOps is Dead.
After seven sessions of static analysis — SCA, license compliance, SAST, container scanning, secret detection — Patrick Steger and I move into the dynamic side of the pipeline. In Part 8 we add Dynamic Application Security Testing to our GitHub Actions pipeline. DAST runs the application and then attacks it. GitHub does not ship this out of the box, so we wire in a community action built on OWASP ZAP — and we are honest about where that approach falls short for enterprise use.
