<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Deployment on Romano Roth</title><link>https://romanoroth.com/en/tags/continuous-deployment/</link><description>Recent content in Continuous Deployment 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/continuous-deployment/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>App-Solutely Safe: How Banks Use Modern Software Development</title><link>https://romanoroth.com/en/blogs/app-solutely-safe-modern-banking-software/</link><pubDate>Mon, 20 May 2024 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/app-solutely-safe-modern-banking-software/</guid><description>&lt;p>Banking software must be secure, reliable, and trustworthy. But many banks still rely on traditional development methods that are slow, risky, and inefficient. In this video, I explore three modern software development practices that are fundamentally changing how banks build and deliver software: continuous deployment, test-driven development, and feature flags.&lt;/p></description></item><item><title>Introduction to Modern Development Practices in Banking: A Playbook</title><link>https://romanoroth.com/en/blogs/introduction-to-modern-development-practices-in-banking-a-playbook/</link><pubDate>Fri, 29 Mar 2024 10:47:16 +0000</pubDate><guid>https://romanoroth.com/en/blogs/introduction-to-modern-development-practices-in-banking-a-playbook/</guid><description>&lt;p>Intdiuction the the eBook Moving to Modern Development Practices in Banking: A Playbook&lt;/p>
&lt;p>&lt;figure>&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="auto"
 alt=""
 width="1629"
 height="1167"
 src="https://romanoroth.com/images/blog/introduction-to-modern-development-practices-in-banking-a-playbook-inline-1_hu_a022c954ce26637e.png"
 srcset="https://romanoroth.com/images/blog/introduction-to-modern-development-practices-in-banking-a-playbook-inline-1_hu_a022c954ce26637e.png 800w, https://romanoroth.com/images/blog/introduction-to-modern-development-practices-in-banking-a-playbook-inline-1_hu_be5f69167e93b812.png 1280w"
 sizes="(min-width: 768px) 50vw, 65vw"
 data-zoom-src="https://romanoroth.com/images/blog/introduction-to-modern-development-practices-in-banking-a-playbook-inline-1.png">&lt;/figure>
&lt;/p>
&lt;p>Welcome to the “Modern Banking eBook”, a comprehensive guide for banking institutions embarking on the crucial journey of modernising their software development processes. I’m Romano Roth, and it’s my privilege to walk you through the transformative steps that can reshape the way banks operate in the digital age.&lt;/p></description></item><item><title>Moving to Modern Software Development and Continuous Integration for Banks: Insights from Romano</title><link>https://romanoroth.com/en/blogs/moving-to-modern-software-development-and-continuous-integration-for-banks-insights-from-romano/</link><pubDate>Wed, 02 Aug 2023 14:28:56 +0000</pubDate><guid>https://romanoroth.com/en/blogs/moving-to-modern-software-development-and-continuous-integration-for-banks-insights-from-romano/</guid><description>&lt;p>By &lt;a href="https://www.linkedin.com/in/anna-redbond-580a0511a/" target="_blank" rel="noreferrer">Anna Redbond&lt;/a> and Romano Roth on August 2, 2023&lt;/p>
&lt;p>A lot of banks are moving to modern software development despite the traditional industry hurdles like compliance, regulations, and legacy architecture. The shared goal: becoming more adaptable to meet customers’ changing demands.&lt;/p></description></item><item><title>GitHub DevSecOps Part 1: What Is GitHub and Why Shift Security Left?</title><link>https://romanoroth.com/en/blogs/github-devsecops-introduction/</link><pubDate>Tue, 03 Jan 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-introduction/</guid><description>&lt;p>After we finished the GitLab DevSecOps series, Patrick changed jobs — and his new team is on GitHub. The problem is the same: no security checks during development. The platform is different. In Part 1 of our GitHub DevSecOps series, we cover what GitHub is, the CI/CD vocabulary you have to share before any pipeline conversation works, and the shape of the DevSecOps pipeline we will build over the next sessions.&lt;/p></description></item><item><title>High-Quality Work in Software Engineering and Building Great Developer Experience</title><link>https://romanoroth.com/en/blogs/high-quality-work-in-software-engineering/</link><pubDate>Fri, 09 Dec 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/high-quality-work-in-software-engineering/</guid><description>&lt;p>What defines high-quality work in software engineering? Is it Scrum? Clean Code? TDD? Functional programming? In this Expert Talks session, my colleague Milan and I present two complementary perspectives. Milan covers the pillars of high-quality engineering work, from team building and customer centricity to clean code and engineering culture. I then show how DevOps and continuous delivery help build great products by moving from a project mindset to a product mindset.&lt;/p></description></item><item><title>GitLab DevSecOps Part 1: What Is GitLab and Why Shift Security Left?</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-introduction/</link><pubDate>Wed, 10 Aug 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-introduction/</guid><description>&lt;p>Why does security still get bolted on at the end of the development process, and how do we move it earlier without slowing teams down? In Part 1 of our GitLab DevSecOps series, Patrick Steger and I set the stage: what GitLab is, what shifting security left really means, and which CI/CD concepts you have to understand before you can build a DevSecOps pipeline that actually works.&lt;/p></description></item><item><title>Tour Around the SAFe DevOps Health Radar: All 16 Stages with Videos</title><link>https://romanoroth.com/en/blogs/devops-health-radar-tour/</link><pubDate>Wed, 15 Jun 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/devops-health-radar-tour/</guid><description>&lt;p>Over the past few years I have published a deep-dive on every single activity in the SAFe DevOps Health Radar. This post is the round-the-radar tour: a single page that walks you through all four aspects and all sixteen stages, with the original video for each and a link to the full article. Use it as a map — to find your starting point, to share with your team, or to assess where you are today and where you want to go next.&lt;/p></description></item><item><title>Feature Toggles: What, Why, How?</title><link>https://romanoroth.com/en/blogs/feature-toggles-what-why-how/</link><pubDate>Wed, 30 Mar 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/feature-toggles-what-why-how/</guid><description>&lt;p>Feature toggles are one of those concepts that sound simple on the surface but unlock enormous power in practice. In this DevOps Meetup Zurich session, I team up with Ben Rometsch, founder of Flagsmith, to explain the what, why, and how of feature toggles. We cover the foundational concepts of CI/CD that make feature toggles necessary, the difference between deployment and release, and how modern feature flagging platforms enable progressive rollouts, user segmentation, and A/B testing.&lt;/p></description></item><item><title>What is Continuous Deployment? | SAFe® DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-continuous-deployment-safe-devops-health-radar/</link><pubDate>Sun, 23 Jan 2022 09:49:57 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-continuous-deployment-safe-devops-health-radar/</guid><description>&lt;p>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.&lt;/p></description></item><item><title>What is Verify? | SAFe DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-verify-safe-devops-health-radar/</link><pubDate>Mon, 06 Dec 2021 20:02:30 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-verify-safe-devops-health-radar/</guid><description>&lt;p>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.&lt;/p></description></item><item><title>What is Deploy? | SAFe DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-deploy-safe-devops-health-radar/</link><pubDate>Sun, 21 Nov 2021 20:46:47 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-deploy-safe-devops-health-radar/</guid><description>&lt;p>Deploy is a critical step in the SAFe for DevOps Health Radar. After we have built a deployable package and tested it in a staging environment, we now want to continuously deploy our changes into the production environment. The goal is to deploy with high frequency and low risk. In this video, I explain how we achieve this and what practices enable continuous deployment.&lt;/p></description></item><item><title>What Is Continuous Deployment (CD)?</title><link>https://romanoroth.com/en/blogs/what-is-continuous-deployment/</link><pubDate>Thu, 06 Aug 2020 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-continuous-deployment/</guid><description>&lt;p>Continuous Deployment is the final, most aggressive step in the CI/CD progression. CI proves the code builds and the unit tests pass. Continuous Delivery proves the artifact works in a production-like environment. Continuous Deployment removes the last manual checkpoint: if every test along the way is green, the change goes straight to production. No &amp;ldquo;deploy&amp;rdquo; button, no Friday-afternoon release window, no human in the loop for the final step.&lt;/p></description></item><item><title>What is CI/CD?</title><link>https://romanoroth.com/en/blogs/what-is-ci-cd/</link><pubDate>Tue, 04 Aug 2020 18:49:47 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-ci-cd/</guid><description>&lt;p>In traditional software development, software is merged and tested by all developers in one big single integration step that usually takes weeks or even months. Since this only happens every few months, this step is very time-consuming.&lt;/p></description></item><item><title>How to Improve Value Streams: A Seven-Step Approach</title><link>https://romanoroth.com/en/blogs/how-to-improve-value-streams/</link><pubDate>Mon, 03 Aug 2020 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/how-to-improve-value-streams/</guid><description>&lt;p>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.&lt;/p></description></item></channel></rss>