<?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 msiinnovation.com - Where Innovation Happens!</title>
	<atom:link href="http://msiinnovation.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://msiinnovation.com</link>
	<description>Home of TEA - The True Enterprise Architecture Solution</description>
	<lastBuildDate>Fri, 16 Aug 2013 22:33:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>Comment on Enterprise Architecture by MSI</title>
		<link>http://msiinnovation.com/?page_id=6#comment-4</link>
		<dc:creator><![CDATA[MSI]]></dc:creator>
		<pubDate>Fri, 16 Aug 2013 22:33:06 +0000</pubDate>
		<guid isPermaLink="false">http://msiinnovation.com/?page_id=6#comment-4</guid>
		<description><![CDATA[Hi Karl,

I think HR is a great department to serve EA from however I believe they should be empowered to do so. I’m not sure an HR resource possesses the skills needed to capture, design and describe an EA without training. …and they may need more resource depending on the scope. Perhaps the best way to make a determination is to beta the execution of EA with beta principles and see how it goes. If it is something they think and demonstrate they could do well – opposed to just doing it – then I say go for it. Just make sure they aren’t the ones determining if they do it well. Get a small beta governance group together of diverse backgrounds throughout your organization and let them make final decision.

Matt]]></description>
		<content:encoded><![CDATA[<p>Hi Karl,</p>
<p>I think HR is a great department to serve EA from however I believe they should be empowered to do so. I’m not sure an HR resource possesses the skills needed to capture, design and describe an EA without training. …and they may need more resource depending on the scope. Perhaps the best way to make a determination is to beta the execution of EA with beta principles and see how it goes. If it is something they think and demonstrate they could do well – opposed to just doing it – then I say go for it. Just make sure they aren’t the ones determining if they do it well. Get a small beta governance group together of diverse backgrounds throughout your organization and let them make final decision.</p>
<p>Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Architecture by Karl Flagg</title>
		<link>http://msiinnovation.com/?page_id=6#comment-2</link>
		<dc:creator><![CDATA[Karl Flagg]]></dc:creator>
		<pubDate>Fri, 16 Aug 2013 21:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://msiinnovation.com/?page_id=6#comment-2</guid>
		<description><![CDATA[Do you think EA can be successfully done from HR? They seem to also have a big picture understanding of a company. We want to do EA and this is pretty much in tune with what our sponsors want, however the sponsors and funding of the project is HR and they would own it. We it MIS do want to own it ourselves and share with everyone. What are your thoughts?]]></description>
		<content:encoded><![CDATA[<p>Do you think EA can be successfully done from HR? They seem to also have a big picture understanding of a company. We want to do EA and this is pretty much in tune with what our sponsors want, however the sponsors and funding of the project is HR and they would own it. We it MIS do want to own it ourselves and share with everyone. What are your thoughts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
