<?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 Unladen swallow - Olivier Wulveryck</title>
    <link>https://blog.owulveryck.info/tags/team-topologies.html</link>
    <description>Recent content in Team-Topologies on Unladen swallow - Olivier Wulveryck</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Olivier Wulveryck</copyright>
    <lastBuildDate>Mon, 22 Jun 2026 11:13:15 +0200</lastBuildDate>
    <atom:link href="https://blog.owulveryck.info/tags/team-topologies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Who Does What? Team Topologies for the Agentic Platform</title>
      <link>https://blog.owulveryck.info/2026/06/22/who-does-what-team-topologies-for-the-agentic-platform.html</link>
      <pubDate>Mon, 22 Jun 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.owulveryck.info/2026/06/22/who-does-what-team-topologies-for-the-agentic-platform.html</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;em&gt;The agentic platform defines what needs to be provided. Team Topologies defines who provides it, and how teams interact to make it happen.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://blog.owulveryck.info/2026/06/19/vibe-coding-at-scale-engineering-strikes-back.html&#34;&gt;the first article of this series&lt;/a&gt;, we asked the &lt;strong&gt;what&lt;/strong&gt;: which systemic capabilities (context, guardrails, tooling) are needed to produce reliable applications at scale. The answer was the agentic platform, and at its core, the &lt;em&gt;agentic factory&lt;/em&gt;: the mechanism where agents plan, code, test, and ship.&lt;/p&gt;&#xA;&lt;p&gt;But a platform does not build itself, and more importantly, it is not consumed the same way it is built. A fundamental question remains: &lt;strong&gt;who does what?&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
