<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Roles (new threads)</title>
		<link>http://agileea.wikidot.com/forum/c-3960/roles</link>
		<description>Threads in the forum category &quot;Roles&quot; - Discussion on the roles for an EA Practice.</description>
				<copyright></copyright>
		<lastBuildDate>Sun, 19 Apr 2026 09:27:33 +0000</lastBuildDate>
		
					<item>
				<guid>http://agileea.wikidot.com/forum/t-3908</guid>
				<title>Enterprise Architect versus Solution Architect</title>
				<link>http://agileea.wikidot.com/forum/t-3908/enterprise-architect-versus-solution-architect</link>
				<description></description>
				<pubDate>Thu, 01 Feb 2007 09:35:38 +0000</pubDate>
				<wikidot:authorName>AgileEA</wikidot:authorName>				<wikidot:authorUserId>8054</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>This kind of thing really gets me going:</p> <div class="wiki-note"> <div style="text-align: left;"> <p>Industry: IT<br /> Type: Contract/Permanent<br /> Position: <strong>Enterprise Architect</strong><br /> Skills: Excellent opportunity in Baltimore for an experienced<br /> <em>Enterprise Architect</em>. This is a temp to perm position. You will be<br /> required to design architecture and develop enterprise applications<br /> using J2EE, JBoss, ANT and Oracle PL/SQL. Must have ability to write<br /> system and integrated test cases and Datamodelling. Ability to provide<br /> technical oversight to one or more Java/J2EE Programmers. Manage<br /> large-scale projects to coordinate cross functional groups and project<br /> plans. You will lead the effort to&#8230;<br /> Location: Baltimore, MD</p> </div> </div> <p>They obviously want a <strong>Solutions Architect</strong> <em>in the Enterprise context.</em></p> <p>It would be really nice if we could get our own definitions is order so that the rest of the industry could use them. It leads to all sorts of misunderstandings and mis-alignments of concepts. I personally think this is one of the reasons for establishing Process webs, so that the terminology starts becoming more standard.</p> <p>Does anyone else have any strong feelings about this type of thing?</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>