<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Enterprise architects are town planners not architects</title>
	<atom:link href="http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/feed/" rel="self" type="application/rss+xml" />
	<link>http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/</link>
	<description>...is a blog by Tom Scott a place where I ramble about my thoughts and observations on the open web, linked data, URIs and generally how technology and design can create great things for people to use.</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:20:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Innovation Labs in search of creativity &#171; Derivadow.com</title>
		<link>http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1996</link>
		<dc:creator><![CDATA[Innovation Labs in search of creativity &#171; Derivadow.com]]></dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1996</guid>
		<description><![CDATA[[...] constraints, objectives and tangible deliverables. Spending too long conceptualising your idea can leave you short of Oxygen, you need to get down from the abstract and deal with the actual. Doing so helps your idea to grow [...]]]></description>
		<content:encoded><![CDATA[<p>[...] constraints, objectives and tangible deliverables. Spending too long conceptualising your idea can leave you short of Oxygen, you need to get down from the abstract and deal with the actual. Doing so helps your idea to grow [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Scott</title>
		<link>http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1821</link>
		<dc:creator><![CDATA[Tom Scott]]></dc:creator>
		<pubDate>Sun, 30 Dec 2007 23:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1821</guid>
		<description><![CDATA[Ingine,

I&#039;m not suggesting that Adobe contributes very much to any enterprises bottom line - rather that Adobe is a very successful company in its own right because, according to Christopher Baus, they focusing on doing not talking.

Nor am I suggesting that there should be no coordination. In the same way I don&#039;t think towns should grow without coordination. But what I am suggesting is that this coordination role should be limited to those issues that concern interoperability this, I think, is analogous to the role of a town planner. When &#039;Enterprise Architects&#039; stray outside this role and start dictating implementation issues we get in trouble - in the same way that we would be in trouble if a central planner tried to plan out how every building would be built, what materials it would use, what the design should be. 

One of the reasons we get in trouble is because to deal with a problem that large (architecting an entire town) requires such massive level of abstraction that they run out of oxygen. Let Town Planners and &#039;Enterprise Architects&#039; (if you must call them that) worry about the central issue of interoperability and; Architects and System Architects + Software Engineers etc. worry about how to build a solution to someone&#039;s problem.]]></description>
		<content:encoded><![CDATA[<p>Ingine,</p>
<p>I&#8217;m not suggesting that Adobe contributes very much to any enterprises bottom line &#8211; rather that Adobe is a very successful company in its own right because, according to Christopher Baus, they focusing on doing not talking.</p>
<p>Nor am I suggesting that there should be no coordination. In the same way I don&#8217;t think towns should grow without coordination. But what I am suggesting is that this coordination role should be limited to those issues that concern interoperability this, I think, is analogous to the role of a town planner. When &#8216;Enterprise Architects&#8217; stray outside this role and start dictating implementation issues we get in trouble &#8211; in the same way that we would be in trouble if a central planner tried to plan out how every building would be built, what materials it would use, what the design should be. </p>
<p>One of the reasons we get in trouble is because to deal with a problem that large (architecting an entire town) requires such massive level of abstraction that they run out of oxygen. Let Town Planners and &#8216;Enterprise Architects&#8217; (if you must call them that) worry about the central issue of interoperability and; Architects and System Architects + Software Engineers etc. worry about how to build a solution to someone&#8217;s problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ingine</title>
		<link>http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1819</link>
		<dc:creator><![CDATA[ingine]]></dc:creator>
		<pubDate>Sun, 30 Dec 2007 15:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1819</guid>
		<description><![CDATA[This is a good read to know the angst of a thinker from the bottom-up level. Dear Sir! What will you do when the OZONE layer depletes. Who is thinking about it. Yes, those who don&#039;t have much oxygen to live on. But these guys do for they have genuine concern. This is tip of the ice berg. It is nice to learn how one has contributed to Adobe&#039;s growth. But is Adobe alone good enough for an enterprise. In fact in terms of ROI, how much percentage does &#039;Adobe&#039; alone contribute to a large enterprise. What fraction? Barely enough. And, &#039;Adobe&#039; alone within a larger enterprise context will be dysfunctional in lack of a bigger picture that helps in achieving a co-ordinated functionality achieved from a matrix of application software portfolio/s.

About the &#039;talkers&#039; and &#039;doers&#039;. IBM took the &#039;talker&#039; Rational and has got much better as a &#039;doer&#039; - walking the talk I guess.

Thanks
srinidhi]]></description>
		<content:encoded><![CDATA[<p>This is a good read to know the angst of a thinker from the bottom-up level. Dear Sir! What will you do when the OZONE layer depletes. Who is thinking about it. Yes, those who don&#8217;t have much oxygen to live on. But these guys do for they have genuine concern. This is tip of the ice berg. It is nice to learn how one has contributed to Adobe&#8217;s growth. But is Adobe alone good enough for an enterprise. In fact in terms of ROI, how much percentage does &#8216;Adobe&#8217; alone contribute to a large enterprise. What fraction? Barely enough. And, &#8216;Adobe&#8217; alone within a larger enterprise context will be dysfunctional in lack of a bigger picture that helps in achieving a co-ordinated functionality achieved from a matrix of application software portfolio/s.</p>
<p>About the &#8216;talkers&#8217; and &#8216;doers&#8217;. IBM took the &#8216;talker&#8217; Rational and has got much better as a &#8216;doer&#8217; &#8211; walking the talk I guess.</p>
<p>Thanks<br />
srinidhi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal Migurski</title>
		<link>http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1805</link>
		<dc:creator><![CDATA[Michal Migurski]]></dc:creator>
		<pubDate>Fri, 28 Dec 2007 21:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/2007/12/20/enterprise-architects-are-town-planners-not-architects/#comment-1805</guid>
		<description><![CDATA[Sadly, if you read some of the new architecture bloggers out there like Geoff Manaugh, it seems that architects themselves fancy themselves town planners.]]></description>
		<content:encoded><![CDATA[<p>Sadly, if you read some of the new architecture bloggers out there like Geoff Manaugh, it seems that architects themselves fancy themselves town planners.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

