<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Software Architecture on Agile Congruence</title>
    <link>https://agilecongruence.com/tags/software-architecture/</link>
    <description>Recent content in Software Architecture on Agile Congruence</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Apr 2025 18:40:27 +0000</lastBuildDate>
    <atom:link href="https://agilecongruence.com/tags/software-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Conway’s Law and Agile Congruence</title>
      <link>https://agilecongruence.com/posts/conways-law-and-agile-congruence/</link>
      <pubDate>Mon, 07 Apr 2025 18:40:27 +0000</pubDate>
      <guid>https://agilecongruence.com/posts/conways-law-and-agile-congruence/</guid>
      <description>&lt;p&gt;In a recent discussion with a fellow Software Engineer about Agile Congruence, he stated that the model did not consider software architecture. More directly he said, “I can be effective at agile software development and delivering in small batches of changes but if my architecture sucks it still might not let me be agile enough.”&lt;/p&gt;
&lt;p&gt;While I definitely agree with this statement, it got me thinking about how Agile Congruence and Software Architecture are related. Ultimately I realized that this comes down to one of the most famous principles in enterprise software architecture, Conway’s Law.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
