<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Experimentation on Romano Roth</title><link>https://romanoroth.com/en/tags/experimentation/</link><description>Recent content in Experimentation on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 27 Nov 2024 09:46:13 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/experimentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to Flip the Switch on Modern Software Development with Feature Flags</title><link>https://romanoroth.com/en/blogs/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags/</link><pubDate>Wed, 27 Nov 2024 09:46:13 +0000</pubDate><guid>https://romanoroth.com/en/blogs/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags/</guid><description>&lt;p>&lt;figure>&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="auto"
 alt=""
 width="1428"
 height="1824"
 src="https://romanoroth.com/images/blog/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags-inline-1_hu_eac29252f51e72e7.png"
 srcset="https://romanoroth.com/images/blog/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags-inline-1_hu_eac29252f51e72e7.png 800w, https://romanoroth.com/images/blog/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags-inline-1_hu_c199c8f3f76ee837.png 1280w"
 sizes="(min-width: 768px) 50vw, 65vw"
 data-zoom-src="https://romanoroth.com/images/blog/introduction-to-flip-the-switch-on-modern-software-development-with-feature-flags-inline-1.png">&lt;/figure>
&lt;/p>
&lt;p>In my two decades of experience leading DevOps, Digital, and Agile transformations, I’ve observed that the path to modernisation is rarely a straight line. Organisations, particularly those in data-sensitive sectors, like banking, government, and healthcare, often find themselves at a crossroads. They need to innovate faster while maintaining rigorous security and reliability. This tension between speed and safety has traditionally forced companies to choose one over the other. But it doesn’t have to be this way.&lt;/p></description></item><item><title>What Is the Third Way of DevOps? Continuous Learning and a Culture of Trust</title><link>https://romanoroth.com/en/blogs/what-is-the-third-way-of-devops/</link><pubDate>Thu, 20 Aug 2020 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-the-third-way-of-devops/</guid><description>&lt;p>The third way to introduce DevOps is to create a culture of trust that supports experimentation and risk-taking. This is the Third Way in Gene Kim&amp;rsquo;s Three Ways framework — and it is what puts the team on a learning curve steep enough to outpace the competition.&lt;/p></description></item></channel></rss>