<?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 on: Managing Complexity with EA</title>
	<atom:link href="http://leodesousa.ca/2008/05/managing-complexity-with-ea/feed/" rel="self" type="application/rss+xml" />
	<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=managing-complexity-with-ea</link>
	<description>a practical approach by Leo de Sousa</description>
	<lastBuildDate>Tue, 31 Jan 2012 18:22:34 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Felix</title>
		<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/comment-page-1/#comment-81</link>
		<dc:creator>Felix</dc:creator>
		<pubDate>Fri, 23 May 2008 15:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://leodesousa.ca/?p=42#comment-81</guid>
		<description>You are right Leo I was only addressing what is written above.  So my view was limited to that context only
Felix.</description>
		<content:encoded><![CDATA[<p>You are right Leo I was only addressing what is written above.  So my view was limited to that context only<br />
Felix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Wu</title>
		<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/comment-page-1/#comment-79</link>
		<dc:creator>John Wu</dc:creator>
		<pubDate>Tue, 20 May 2008 12:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://leodesousa.ca/?p=42#comment-79</guid>
		<description>Hi ! 
&lt;a href=&quot;www.liteEA.com&quot; rel=&quot;nofollow&quot;&gt; LiteEA &lt;/a&gt;  believe EA is both wide and deep.  EA is a discipline see the forest but also eye on the tree to look for reuse and consolidation.  We look at big picture to see the forest and eye on the depth to find the commonality and enable agility.  My &lt;a href=&quot;http://blogs.ittoolbox.com/cio/lea/archives/ea-from-the-big-bang-to-business-centric-and-transition-to-incremental-24722&quot; rel=&quot;nofollow&quot;&gt;recent article on &lt;/a&gt;  illustrates the EA evolution from the big bang approach, the business centric approach and the incremental approach. On the illustration, you can see the wide branch high level planning and detail branch of the reuse and consolidation. EA has evolved in the two direction of business centric EA and the incremental EA.  It is not for us to say who is right or wrong,  only time can tell.  However, the business centric approach has been a continuous struggle from the fortune tellers in the early days to the industry engineering, enterprise engineering. Hopefully, EA do not become the same struggle.</description>
		<content:encoded><![CDATA[<p>Hi !<br />
<a href="www.liteEA.com" rel="nofollow"> LiteEA </a>  believe EA is both wide and deep.  EA is a discipline see the forest but also eye on the tree to look for reuse and consolidation.  We look at big picture to see the forest and eye on the depth to find the commonality and enable agility.  My <a href="http://blogs.ittoolbox.com/cio/lea/archives/ea-from-the-big-bang-to-business-centric-and-transition-to-incremental-24722" rel="nofollow">recent article on </a>  illustrates the EA evolution from the big bang approach, the business centric approach and the incremental approach. On the illustration, you can see the wide branch high level planning and detail branch of the reuse and consolidation. EA has evolved in the two direction of business centric EA and the incremental EA.  It is not for us to say who is right or wrong,  only time can tell.  However, the business centric approach has been a continuous struggle from the fortune tellers in the early days to the industry engineering, enterprise engineering. Hopefully, EA do not become the same struggle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LeodeSousa</title>
		<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/comment-page-1/#comment-78</link>
		<dc:creator>LeodeSousa</dc:creator>
		<pubDate>Mon, 19 May 2008 05:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://leodesousa.ca/?p=42#comment-78</guid>
		<description>Felix, Thanks for the comment ... a bit harsh but I am good with the feedback so that I can improve on the work I do.  

First, I disagree with your comment that what I posted in this blog entry &quot;totally different from what EA really is&quot;.  I suggest that if you want to know how we have built our EA practice, you need to go deeper than reviewing one of my blog posts about complexity and condemning me with &quot;misleads people into thinking it is all about technology&quot;.  

Our EA practice is guided by the following:
- &quot;Do the Right Things&quot; - this is Governance with EA
- &quot;Do Things Right&quot; - this is EA with other methodologies like PM and ITIL

The post above was about &quot;Do Things Right&quot; ... 

Regards, Leo</description>
		<content:encoded><![CDATA[<p>Felix, Thanks for the comment &#8230; a bit harsh but I am good with the feedback so that I can improve on the work I do.  </p>
<p>First, I disagree with your comment that what I posted in this blog entry &#8220;totally different from what EA really is&#8221;.  I suggest that if you want to know how we have built our EA practice, you need to go deeper than reviewing one of my blog posts about complexity and condemning me with &#8220;misleads people into thinking it is all about technology&#8221;.  </p>
<p>Our EA practice is guided by the following:<br />
- &#8220;Do the Right Things&#8221; &#8211; this is Governance with EA<br />
- &#8220;Do Things Right&#8221; &#8211; this is EA with other methodologies like PM and ITIL</p>
<p>The post above was about &#8220;Do Things Right&#8221; &#8230; </p>
<p>Regards, Leo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FEAC</title>
		<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/comment-page-1/#comment-77</link>
		<dc:creator>FEAC</dc:creator>
		<pubDate>Sun, 18 May 2008 18:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://leodesousa.ca/?p=42#comment-77</guid>
		<description>Calling what your are describing Enterprise Architecture is totally different from what EA really is.  EA is a discipline that allows us to get our arms around complexity in the 21st century.  Yes you can apply that discipline to the technical problems you talk about but it is much larger than that. It is an all encompassing holistic discipline that gets you from strategic planning all the way to instantiations and better more real time 21st century decision making.  Using it in the context you describe misleads people into thinking it is all about technology.  Just the opposite is true, its about the business first and then how technology can help make the business more agile and more profitable.</description>
		<content:encoded><![CDATA[<p>Calling what your are describing Enterprise Architecture is totally different from what EA really is.  EA is a discipline that allows us to get our arms around complexity in the 21st century.  Yes you can apply that discipline to the technical problems you talk about but it is much larger than that. It is an all encompassing holistic discipline that gets you from strategic planning all the way to instantiations and better more real time 21st century decision making.  Using it in the context you describe misleads people into thinking it is all about technology.  Just the opposite is true, its about the business first and then how technology can help make the business more agile and more profitable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T-Enterprise</title>
		<link>http://leodesousa.ca/2008/05/managing-complexity-with-ea/comment-page-1/#comment-76</link>
		<dc:creator>T-Enterprise</dc:creator>
		<pubDate>Sat, 17 May 2008 13:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://leodesousa.ca/?p=42#comment-76</guid>
		<description>Excellent article - we use something similair to your app portfolio however not as structured nor as many delivery platforms - will get there!</description>
		<content:encoded><![CDATA[<p>Excellent article &#8211; we use something similair to your app portfolio however not as structured nor as many delivery platforms &#8211; will get there!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

