Measure is the step of the SAFe for DevOps Health Radar where everything comes together. After deploying to production and stabilizing, we now collect qualitative and quantitative information about our epics and features. The goal is to validate our hypotheses and make informed strategic decisions. In this video, I walk through what the Measure step involves and why it is essential for building the right thing.
After we release a new feature to our users, we need to make sure everything runs smoothly. Stabilize is the SAFe DevOps Health Radar activity that focuses on maintaining a high level of business continuity so we can continuously deliver value to our customers. In this video, I walk through what Stabilize involves and why it is essential for a stable, resilient production environment.
Release is one of the final steps in the SAFe for DevOps Health Radar. At this point, the new functionality is already deployed to production and verified. Now it is time to make the new functionality available to a small group of users or to all users. In this video, I walk through what the Release step involves and why it is a crucial business decision.
Together with my colleague Nadine, I presented an updated version of our participatory budgeting approach. We had already shared the first version at a previous event, but since then we made significant changes that we wanted to share. A quick disclaimer: we did not invent participatory budgeting. We built on the materials from the SAFe (Scaled Agile Framework), so you will find the copyright on the relevant slides. If you want to introduce participatory budgeting in your own organization, we are happy to share our experience and always reference the original SAFe materials.
On February 1, 2002, I started my journey at Zühlke as a junior software engineer. Twenty years later, I am still here. In this post, I want to share what those 20 years looked like, what kept me going, and why I plan to stay for at least another 20.
In this article, I explain what Continuous Deployment is within the SAFe® DevOps Health Radar and why it is essential for delivering value quickly and safely. Please note that everything discussed here is under the license of Scaled Agile, and that the Scaled Agile Framework is a framework to be used as a toolbox. Take out of this toolbox what fits your needs and what solves your problems.
How do you proactively detect and fix production issues before they cause a business disruption? Respond is the SAFe DevOps Health Radar activity that answers exactly this question. In this video, I walk through what Respond involves and why it is essential for maintaining a stable production environment.
Value stream mapping is a lean management method for improving the flow of value from idea to production. It offers insight into the efficiency of an organisation and can help to identify bottlenecks and improve value flow. The primary goal is to eliminate any waste.
A year ago I called DevSecOps, continuous delivery, cloud and AIOps as the trends for 2021. Most of those landed. For 2022 the picture gets more interesting because DevOps is no longer a single wave — different parts of the market are at very different stages of adoption. To make sense of that, I map the 2022 trends onto the technology adoption lifecycle: late majority, early majority and early adopters.
Once our features are deployed and verified in production, we need to keep a close eye on how they perform. Monitor is the SAFe DevOps Health Radar activity that focuses on tracking system performance, end-user behavior, incidents, and business value. In this video, I walk through what monitoring involves and why it is essential for making the right decisions about your features.
In this article, we will explore what exactly SAFe® DevOps is for health radar and what can you use it for.
Verify is a critical step in the SAFe for DevOps Health Radar. After deploying our package into the production environment, we need to confirm that the new functionality works correctly and does not negatively affect the integrity or robustness of the existing system. Only after this verification is complete can we confidently release the new features to end-users. In this video, I walk through what the Verify step involves and how it fits into the overall continuous delivery pipeline.
