<?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/"
		>
<channel>
	<title>Comments for Angry Architect</title>
	<atom:link href="http://www.angryarchitect.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.angryarchitect.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Sep 2011 01:42:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Four Rules of Engagement by The Spook</title>
		<link>http://www.angryarchitect.com/?p=444&#038;cpage=1#comment-186</link>
		<dc:creator>The Spook</dc:creator>
		<pubDate>Mon, 19 Sep 2011 01:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=444#comment-186</guid>
		<description><![CDATA[This is a wonderful site]]></description>
		<content:encoded><![CDATA[<p>This is a wonderful site</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Four Rules of Engagement by Angry Architect’s Rules Of Engagement « Enterprise Systems Engineering</title>
		<link>http://www.angryarchitect.com/?p=444&#038;cpage=1#comment-100</link>
		<dc:creator>Angry Architect’s Rules Of Engagement « Enterprise Systems Engineering</dc:creator>
		<pubDate>Wed, 31 Aug 2011 20:02:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=444#comment-100</guid>
		<description><![CDATA[[...] fellow blogger Angry Architect wrote a brief post about his rules of engagement. I suspect there&#8217;s a typo in the first one, which should have been meant to read like [...]]]></description>
		<content:encoded><![CDATA[<p>[...] fellow blogger Angry Architect wrote a brief post about his rules of engagement. I suspect there&#8217;s a typo in the first one, which should have been meant to read like [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture at Work by http://www.sebastianashear.com/bring-the-fresh/bring-the-fresh-review/</title>
		<link>http://www.angryarchitect.com/?p=74&#038;cpage=1#comment-99</link>
		<dc:creator>http://www.sebastianashear.com/bring-the-fresh/bring-the-fresh-review/</dc:creator>
		<pubDate>Mon, 29 Aug 2011 06:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=74#comment-99</guid>
		<description><![CDATA[&lt;strong&gt;bring the fresh review...&lt;/strong&gt;

Enterprise Architecture at Work &#124; Angry Architect...]]></description>
		<content:encoded><![CDATA[<p><strong>bring the fresh review&#8230;</strong></p>
<p>Enterprise Architecture at Work | Angry Architect&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture for Integration by John</title>
		<link>http://www.angryarchitect.com/?p=412&#038;cpage=1#comment-83</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 23 Mar 2011 09:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=412#comment-83</guid>
		<description><![CDATA[I think this book Enterprise Architecture Integration is awesome!!!Definitely i want to read this book atleast once.I guess it has all the topic related to enterprise architecture.There is another site named mexia.com.au ,where you can get more information about Enterprise Integration Architecture.]]></description>
		<content:encoded><![CDATA[<p>I think this book Enterprise Architecture Integration is awesome!!!Definitely i want to read this book atleast once.I guess it has all the topic related to enterprise architecture.There is another site named mexia.com.au ,where you can get more information about Enterprise Integration Architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dynamic Enterprise Architecture by racunovodski servis</title>
		<link>http://www.angryarchitect.com/?p=118&#038;cpage=1#comment-79</link>
		<dc:creator>racunovodski servis</dc:creator>
		<pubDate>Fri, 28 Jan 2011 22:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=118#comment-79</guid>
		<description><![CDATA[I have to admit that i generally get bored to learn the whole thing but i believe you can add some value. Bravo !]]></description>
		<content:encoded><![CDATA[<p>I have to admit that i generally get bored to learn the whole thing but i believe you can add some value. Bravo !</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear Angry by Imhotep</title>
		<link>http://www.angryarchitect.com/?page_id=330&#038;cpage=1#comment-72</link>
		<dc:creator>Imhotep</dc:creator>
		<pubDate>Sat, 08 Jan 2011 02:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?page_id=330#comment-72</guid>
		<description><![CDATA[We&#039;re delighted!]]></description>
		<content:encoded><![CDATA[<p>We&#8217;re delighted!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear Angry by John Gøtze</title>
		<link>http://www.angryarchitect.com/?page_id=330&#038;cpage=1#comment-71</link>
		<dc:creator>John Gøtze</dc:creator>
		<pubDate>Wed, 05 Jan 2011 03:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?page_id=330#comment-71</guid>
		<description><![CDATA[I&#039;ve included your blog feed on http://eablogs.gotze.eu. Hope that&#039;s OK.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve included your blog feed on <a href="http://eablogs.gotze.eu" rel="nofollow">http://eablogs.gotze.eu</a>. Hope that&#8217;s OK.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Flippin&#8217; the Black Swan Burger by Decamerone</title>
		<link>http://www.angryarchitect.com/?p=402&#038;cpage=1#comment-69</link>
		<dc:creator>Decamerone</dc:creator>
		<pubDate>Wed, 01 Dec 2010 01:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=402#comment-69</guid>
		<description><![CDATA[Wouldn&#039;t it be nice if we could hold this certain bank up as an isolated example in the corporate world of &quot;how things should not be done&quot; - an anti-pattern perhaps - but I fear it is all to common and organisations that value their employee&#039;s are the exception.]]></description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t it be nice if we could hold this certain bank up as an isolated example in the corporate world of &#8220;how things should not be done&#8221; &#8211; an anti-pattern perhaps &#8211; but I fear it is all to common and organisations that value their employee&#8217;s are the exception.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just and All the Anti-Pattern of Architecture by Decamerone</title>
		<link>http://www.angryarchitect.com/?p=389&#038;cpage=1#comment-68</link>
		<dc:creator>Decamerone</dc:creator>
		<pubDate>Tue, 23 Nov 2010 23:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?p=389#comment-68</guid>
		<description><![CDATA[It can also been seen (possibly) as a sign the architecture team has not communicated well enough the progress/activity that is happening that this stakeholder, or more importantly sponsor, is aware of.  The statement could be a sign of frustration that nothing, too little, or completely irrelevant things are happening from their perspective.

So, while I totally agree with the premise of this post that accepting what follows &quot;We just need to...&quot; is likely to be a road to ruin, at the same time it needs to be highlighted that statements like this are probably symptoms of other communication problems.]]></description>
		<content:encoded><![CDATA[<p>It can also been seen (possibly) as a sign the architecture team has not communicated well enough the progress/activity that is happening that this stakeholder, or more importantly sponsor, is aware of.  The statement could be a sign of frustration that nothing, too little, or completely irrelevant things are happening from their perspective.</p>
<p>So, while I totally agree with the premise of this post that accepting what follows &#8220;We just need to&#8230;&#8221; is likely to be a road to ruin, at the same time it needs to be highlighted that statements like this are probably symptoms of other communication problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear Angry by Imhotep</title>
		<link>http://www.angryarchitect.com/?page_id=330&#038;cpage=1#comment-63</link>
		<dc:creator>Imhotep</dc:creator>
		<pubDate>Sun, 22 Aug 2010 02:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.angryarchitect.com/?page_id=330#comment-63</guid>
		<description><![CDATA[Mridul,

As is often the case with EA, the answer is it depends. But, like all good architects I&#039;ll start by stating my assumptions. 

1) By IT Architecture you mean predominately solution architecture, which you are already comfortable with. 

2) By EA consulting you intended to cover the full gambit of architecture. 

With these in mind I&#039;d suggest the following. 

Enterprise Architecture Planning by Spewak and Hill.
Enterprise Architecture as Strategy Ross, Weil and Robertson.

These should position you for planning EA. 

Then a little closer to the metal I&#039;d suggest
An Introduction to Enterprise Architecture by Scott Bernard and Dynamic Enterprise Architecture by Wagter et. al to help with project governance.

Finally ORourke, Fishman and Selkow&#039;s book Enterprise Architecture, Using the Zachman Framework, because  solution architects typically don&#039;t get EA.]]></description>
		<content:encoded><![CDATA[<p>Mridul,</p>
<p>As is often the case with EA, the answer is it depends. But, like all good architects I&#8217;ll start by stating my assumptions. </p>
<p>1) By IT Architecture you mean predominately solution architecture, which you are already comfortable with. </p>
<p>2) By EA consulting you intended to cover the full gambit of architecture. </p>
<p>With these in mind I&#8217;d suggest the following. </p>
<p>Enterprise Architecture Planning by Spewak and Hill.<br />
Enterprise Architecture as Strategy Ross, Weil and Robertson.</p>
<p>These should position you for planning EA. </p>
<p>Then a little closer to the metal I&#8217;d suggest<br />
An Introduction to Enterprise Architecture by Scott Bernard and Dynamic Enterprise Architecture by Wagter et. al to help with project governance.</p>
<p>Finally ORourke, Fishman and Selkow&#8217;s book Enterprise Architecture, Using the Zachman Framework, because  solution architects typically don&#8217;t get EA.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
