Many software organizations spend too much effort building and maintaining features that create little real value. This talk shows how to reduce cost not by slowing down delivery, but by improving effectiveness and efficiency at the same time.
In today’s world, everybody wants to do DevOps. But why? What problems are we trying to solve?
Taking a Step Back # Together, we will take a step back and look at the bigger picture. Instead of jumping straight into tools and practices, we examine the systems and value streams that underpin modern software delivery.
DevOps is far more than automation or tooling: it is the interplay of people, processes, and technology to develop products faster, more reliably, and more customer-focused.
What This Talk Covers # This talk shows why companies must shift from project-oriented thinking to product-centric working, how a Continuous Delivery Pipeline works as the backbone of modern product development, and why quality, testing, and operability must be considered from the start.
This is the English-language version of our talk on participatory budgeting at Zühlke. Nadine Broghammer and I describe how we coached a portfolio team through a participatory budgeting (PB) event based on SAFe, and how the value stream leads collectively allocated the budget for the second half of the year. A separate post covers the German version of the same talk.
How can innovation and development budgets be distributed faster, more transparently, and more effectively? Participatory Budgeting offers a collaborative approach to steering investments not project-by-project, but along value streams and strategic priorities.
A value stream is the path that value takes from the first idea all the way into production. It is the sum of every step, handover, and wait in between. In this video, I walk through a simple seven-step approach for identifying a value stream, measuring how it really performs, designing a target state, and then improving it step by step. The numbers in the example are simplified on purpose, so the method shines through more clearly than any single result.
