<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Enterprise Architect vs Solution Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx</link><description>What exactly is an Enterprise Architect versus a Solution Architect? I'd like to chat about the difference because I'm not confident everyone understands this well. It's actually quite simple. I propose that a Solution Architect is a project team role</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Enterprise Architect vs Solution Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#4707626</link><pubDate>Sun, 02 Sep 2007 20:19:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4707626</guid><dc:creator>MSDN Blog Postings  » Enterprise Architect vs Solution Architect</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/09/02/enterprise-architect-vs-solution-architect/"&gt;http://msdnrss.thecoderblogs.com/2007/09/02/enterprise-architect-vs-solution-architect/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The non-overlapping responsibility set: Solution Architect and Enterprise Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#8563538</link><pubDate>Fri, 30 May 2008 19:02:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8563538</guid><dc:creator>Inside Architecture </dc:creator><description>&lt;p&gt;Recently, Mike Walker posted a blog entry on the difference between Enterprise Architect and Solution&lt;/p&gt;
</description></item><item><title>re: Enterprise Architect vs Solution Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#8716535</link><pubDate>Thu, 10 Jul 2008 14:39:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8716535</guid><dc:creator>Steve</dc:creator><description>&lt;P&gt;Enterprise Architecture does not only involve IT architecture - it cover IS arhitecture and Business architecture also i.e. Enteprise architecture is a strategic role that plans the end state of the entire enterprise and the roadmpa for attaining this across: Business Architecture (Value Chain, Revenue model, Service Delivery model, operating model, enterprise process model, information model), Information Systems Architecture (Data model, Application model, interop/integration and services models) and technology architecture (infrastructure - SW, HW, connectivity and security). A solution architect drives the delivery of a particualr piece of this in the form of a project - seeing it is about business solutions the solutions architect must be able to work in both information, process and IS and IT areas.&lt;/P&gt;</description></item><item><title>re: Enterprise Architect vs Solution Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#8750790</link><pubDate>Fri, 18 Jul 2008 21:51:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8750790</guid><dc:creator>Raj Chanian</dc:creator><description>&lt;P&gt;Solution(s) Architects are responsible for delivering the right solution. Enterprise Architects enforce governance across the Enterprise Solutions Landscape and ensure that the solutions are done right.&lt;/P&gt;
&lt;P&gt;For my recent solution, I had a Service Architect to report to me for the ITIL solution, and the Technical Architect report to me for the Infrastructure solution, Business Architect to report to me for the functional solution and the Applications Architects report to me for their respective Applications solutions. I had overall responsible for the full solution lifecycle as a solution architect.&lt;/P&gt;
&lt;P&gt;This can be taken further whereby Solution Architects are accountable to the Enterprise Architect who ensures that the solutions dovetail into the strategic roadmap/policy...&lt;/P&gt;</description></item><item><title>Enterprise Solution Architects and Leadership</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#9336724</link><pubDate>Sun, 18 Jan 2009 02:18:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9336724</guid><dc:creator>Gabriel Morgan</dc:creator><description>&lt;p&gt;I strongly believe that Leadership is a critical competency for successful Enterprise Solution Architects&lt;/p&gt;
</description></item><item><title>re: Enterprise Architect vs Solution Architect</title><link>http://blogs.msdn.com/gabriel_morgan/archive/2007/09/02/enterprise-architect-vs-solution-architect.aspx#9918678</link><pubDate>Fri, 06 Nov 2009 17:14:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9918678</guid><dc:creator>Ellis Benjamin</dc:creator><description>&lt;P&gt;EA is a change agent who who identifies and baselines the 'as is' and formulates the strategies and high-level change projects to position the where we want 'to be'.&lt;/P&gt;
&lt;P&gt;The SA designs the solution architecture to host the 'to be' state.&lt;/P&gt;</description></item></channel></rss>