<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Solution Architect - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Solution Architect Articles feed</description>
    <item>
      <title>Article: Going from Architect to Architecting: the Evolution of a Key Role</title>
      <link>https://www.infoq.com/articles/architecture-architecting-role/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Solution+Architect-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/architecture-architecting-role/en/headerimage/generatedHeaderImage-1670406360462.jpg"/&gt;&lt;p&gt;This article explores the cultural change of moving towards shared architecture, and the role that the architect has evolved into; from one with an air of authority and singular vision, to one in which system design issues are surfaced, which require team-wide input to resolve. Teams being coached and guided towards shared ownership might be struggling with the paradigm shift of ownership.&lt;/p&gt; &lt;i&gt;By Leigh Griffin, Chris Foley&lt;/i&gt;</description>
      <category>Solution Architect</category>
      <category>Adopting Agile</category>
      <category>Artifacts &amp; Tools</category>
      <category>Coaching and Mentoring</category>
      <category>Architecture</category>
      <category>Teamwork</category>
      <category>Coaching</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 09 Dec 2022 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/architecture-architecting-role/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Solution+Architect-articles</guid>
      <dc:creator>Leigh Griffin, Chris Foley</dc:creator>
      <dc:date>2022-12-09T09:00:00Z</dc:date>
      <dc:identifier>/articles/architecture-architecting-role/en</dc:identifier>
    </item>
  </channel>
</rss>
