<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team Topologies on DevOps Noldus</title><link>https://blog.antnsn.dev/tags/team-topologies/</link><description>Recent content in Team Topologies on DevOps Noldus</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Apr 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://blog.antnsn.dev/tags/team-topologies/index.xml" rel="self" type="application/rss+xml"/><item><title>Platform teams aren't DevOps teams with a rebrand</title><link>https://blog.antnsn.dev/2026-p2-platform-teams-rebrand/</link><pubDate>Wed, 15 Apr 2026 10:00:00 +0100</pubDate><guid>https://blog.antnsn.dev/2026-p2-platform-teams-rebrand/</guid><description>&lt;p&gt;Most orgs rename their DevOps team to &amp;ldquo;Platform Engineering&amp;rdquo; and call it a strategy. It isn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;The Confluence page gets updated. A roadmap appears with &amp;ldquo;IDP&amp;rdquo; somewhere in Q3. The team lead gets a new title. Six months later, developers are still filing tickets to get an environment, and the &amp;ldquo;platform team&amp;rdquo; is still the bottleneck for every deployment. Nothing changed except the branding.&lt;/p&gt;
&lt;p&gt;This is the rebrand problem. And it&amp;rsquo;s widespread enough that it&amp;rsquo;s worth being direct about what actually separates a platform team from a DevOps team that got a new name.&lt;/p&gt;</description></item></channel></rss>