<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Thinking inside a bigger box - Latest Comments in Agile Architecture</title><link>http://thinkinginsideabiggerbox.disqus.com/</link><description></description><atom:link href="https://thinkinginsideabiggerbox.disqus.com/agile_architecture/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 27 Jun 2005 16:12:18 -0000</lastBuildDate><item><title>Re: Agile Architecture</title><link>http://johannesbrodwall.com/2005/06/24/agile-architecture/#comment-1795619</link><description>&lt;p&gt;I really like the stress on the communiction. To me the role of the architect is twofold&lt;br&gt;1) to keep and evolve the vision (gutfeeling, dream, understanding: take your pick) of the system as a technical artifact&lt;br&gt;2) to communicate the vision to everybody - developers, testers, users, PLs, board, investors ... whoever&lt;/p&gt;&lt;p&gt;ps Welcome back Johannes, we (the world) have been missing your blogentries&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dan Johnsson</dc:creator><pubDate>Mon, 27 Jun 2005 16:12:18 -0000</pubDate></item></channel></rss>