<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2015/04/split-code-bases-and-team-ownership/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2015/04/split-code-bases-and-team-ownership/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>Split code bases and team ownership</title>
        <link>https://elezea.com/2015/04/split-code-bases-and-team-ownership/</link>
        <pubDate>Wed, 15 Apr 2015 06:54:47 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=5302</guid>
        <description>
          <![CDATA[Marty Cagan continues his excellent product autonomy series by discussing what happens when teams get large enough to split up their code bases. In Autonomy vs. Ownership he describes his preferred way of dealing with the situation where a team needs a change in a different codebase to get one of their features implemented: The [&#8230;]]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Marty Cagan continues his excellent product autonomy series by discussing what happens when teams get large enough to split up their code bases. In <em><a href="http://www.svpg.com/autonomy-vs-ownership/">Autonomy vs. Ownership</a></em> he describes his preferred way of dealing with the situation where a team needs a change in a different codebase to get one of their features implemented:</p>
<blockquote>
<p>The alternative model is informally known as the “open source” model although to be clear this is not about open sourcing your code, it’s just called that because this is how much of the open source community operates.  In this model, if the <em>drivers</em> team needs a change to the <em>riders</em> team’s code, then they could either wait for the <em>riders</em> team to do it, or they can actually make the change themselves, and then request that the <em>riders</em> team review the change, and include it if they’re okay with it (known as a “pull request”).  This means that you are telling the software management system that you’ve made a change to the software, but the owner of that software needs to review the changes before they are actually approved and incorporated.</p>
</blockquote>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>