<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Books on Romano Roth</title><link>https://romanoroth.com/en/books/</link><description>Recent content in Books on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/books/index.xml" rel="self" type="application/rss+xml"/><item><title>Lean Enterprise Architecture</title><link>https://romanoroth.com/en/books/lean-enterprise-architecture/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/lean-enterprise-architecture/</guid><description>&lt;p&gt;There is a pattern to how enterprise architecture fails. The models get more detailed, the governance gets heavier, and the people who make the real decisions stop showing up. The architecture is correct and nobody uses it.&lt;/p&gt;</description></item><item><title>The Cybernetic Enterprise</title><link>https://romanoroth.com/en/books/the-cybernetic-enterprise/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/the-cybernetic-enterprise/</guid><description>&lt;p&gt;Most organizations still run on an operating system built for stability. Plan the year, cascade the plan, report back up. That holds as long as the ground does.&lt;/p&gt;&#10;&lt;p&gt;The Cybernetic Enterprise describes what takes its place: an organization that senses what is happening, decides close to the work, and adapts continuously. Feedback loops are the load-bearing structure. AI sits inside those loops instead of being bolted onto the side of the org chart.&lt;/p&gt;</description></item><item><title>Foundations of The Cybernetic Enterprise</title><link>https://romanoroth.com/en/books/foundations-of-the-cybernetic-enterprise/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/foundations-of-the-cybernetic-enterprise/</guid><description>&lt;p&gt;A reference volume rather than a narrative. The Cybernetic Enterprise stands on eight fields: cybernetics, systems thinking, lean and flow, agile, architecture, product and innovation, AI, and DevOps. Each has decades of practice behind it, each has its own literature, and each answers only part of the question.&lt;/p&gt;</description></item><item><title>The Cybernetic Enterprise Assessment</title><link>https://romanoroth.com/en/books/the-cybernetic-enterprise-assessment/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/the-cybernetic-enterprise-assessment/</guid><description>&lt;p&gt;A model that cannot be measured stays an opinion. The Assessment turns the Cybernetic Enterprise into a structured maturity check across four dimensions: people, process, technology and data.&lt;/p&gt;&#10;&lt;p&gt;It is built to be run. Questions per dimension, levels that describe observable behavior instead of intent, and a result you can put next to the same unit six months later.&lt;/p&gt;</description></item><item><title>The Cybernetic Enterprise CTO Playbook</title><link>https://romanoroth.com/en/books/the-cybernetic-enterprise-cto-playbook/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/the-cybernetic-enterprise-cto-playbook/</guid><description>&lt;p&gt;The CTO&amp;rsquo;s copy of the model. Same idea, seen from the technology organization: architect for simplicity, give teams enough autonomy to be accountable, scale platform engineering so that autonomy does not turn into forty snowflakes, and embed AI with governance that people can follow without asking permission twice a day.&lt;/p&gt;</description></item><item><title>How to Survive Game of Thrones</title><link>https://romanoroth.com/en/books/how-to-survive-game-of-thrones/</link><pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/how-to-survive-game-of-thrones/</guid><description>&lt;p&gt;Written with Nadine Broghammer.&lt;/p&gt;&#10;&lt;p&gt;Next to the org chart every organization runs a second structure: who has influence, who owes whom, which disagreement is about the work and which one is about position. Most people learn to read it the slow way, by losing a few rounds first.&lt;/p&gt;</description></item><item><title>Flip the Switch on Modern Software Development with Feature Flags</title><link>https://romanoroth.com/en/books/flip-the-switch-feature-flags/</link><pubDate>Wed, 27 Nov 2024 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/flip-the-switch-feature-flags/</guid><description>&lt;p&gt;Flagsmith&amp;rsquo;s eBook on feature flags at enterprise scale. I wrote the introduction.&lt;/p&gt;&#10;&lt;p&gt;The argument in it: feature flags separate deployment from release, and that separation is what makes deployment frequency, one of the four DORA metrics, movable at all. Without it, a team can only deploy as often as it dares to release. With it, small changes go out several times a day and the blast radius of each one stays small.&lt;/p&gt;</description></item><item><title>Modern Development Practices in Banking: A Playbook</title><link>https://romanoroth.com/en/books/modern-development-practices-in-banking/</link><pubDate>Fri, 29 Mar 2024 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/modern-development-practices-in-banking/</guid><description>&lt;p&gt;Flagsmith&amp;rsquo;s playbook for banks that want to modernize how they build software without trading away the controls a regulator expects. I wrote the introduction.&lt;/p&gt;&#10;&lt;p&gt;Banking is where the tension between speed and safety is sharpest, and where the usual answer has been to pick safety and live with the release cycle. The playbook works through the alternative: continuous delivery, feature flags, platform engineering, and the audit and access controls that make all three acceptable in a regulated environment.&lt;/p&gt;</description></item><item><title>Machines, Code, People</title><link>https://romanoroth.com/en/books/machines-code-people/</link><pubDate>Tue, 18 Jun 2019 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/books/machines-code-people/</guid><description>&lt;p&gt;An anthology from Zühlke: 50 short pieces, one per engineer, on whatever that person cares most about.&lt;/p&gt;&#10;&lt;p&gt;Mine is called &lt;em&gt;CYA: Cover your ass&lt;/em&gt;, and it is about documenting architecture decisions. Not the 200-page document nobody reads. The short record of what was decided, what the alternatives were, and why one of them won, written at the moment the decision is made and cheap enough that people actually write it.&lt;/p&gt;</description></item></channel></rss>