<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dora-Metrics on F. Latini - IT Engineer</title><link>https://latini.dev/tags/dora-metrics/</link><description>Recent content in Dora-Metrics on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Jun 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/dora-metrics/index.xml" rel="self" type="application/rss+xml"/><item><title>DORA Metrics Without the Dashboard Theatre</title><link>https://latini.dev/posts/dora-metrics-without-the-dashboard-theatre/</link><pubDate>Fri, 26 Jun 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/dora-metrics-without-the-dashboard-theatre/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - The four &lt;a href="https://dora.dev/"&gt;DORA metrics&lt;/a&gt; are good. What most teams do with them is theatre: a dashboard that trends up and to the right while nothing about how software actually ships changes. The metrics are a thermometer, not a treatment. Measuring deployment frequency doesn&amp;rsquo;t make you deploy more often any more than weighing yourself makes you thinner. This post is the four metrics read honestly, the four ways teams quietly game them, and the single question that separates a real DORA practice from a screenshot in the quarterly review: &lt;em&gt;what did this number cause us to change?&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>