<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Collaborative SOA Lessons Learned</title>
	<link>http://www4.sungard.com/blogs/darrenWesemann/2006/09/04/collaborative-soa-lessons-learned/</link>
	<description>Darren Wesemann on SunGard Technology</description>
	<pubDate>Thu, 18 Mar 2010 06:44:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: &#187; Blog Archive &#187; SOA Patience</title>
		<link>http://www4.sungard.com/blogs/darrenWesemann/2006/09/04/collaborative-soa-lessons-learned/#comment-15</link>
		<pubDate>Tue, 13 Feb 2007 22:50:46 +0000</pubDate>
		<guid>http://www4.sungard.com/blogs/darrenWesemann/2006/09/04/collaborative-soa-lessons-learned/#comment-15</guid>
					<description>[...] As I mentioned in my blog on SOA governance SOA efforts (especially at large banks) are monumental tasks, requiring a very different paradigm (one of collaboration) to be engrained in the social infrastructure. This takes time. The technologies that enable SOA’s are available (granted, they have to be adopted, integrated, which also takes time and patience), but don’t underestimate the time it takes for a federated and collaborative process to be adopted.Regarding the technology, the expectation needs to be set (or reset as the case may be) that the changes technically are more likely a three to seven year evolution. Some of the confusion on SOA timing expectation likely came from the traditional notion of installing something “and you’re done”. You don’t “install” an SOA, rather you evolve your architecture and governance process towards it. As I’ve preached before starting small, and taking baby steps is a key to SOA success, and I see a lot of enterprises doing exactly that, which of course is slow, but progressive. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As I mentioned in my blog on SOA governance SOA efforts (especially at large banks) are monumental tasks, requiring a very different paradigm (one of collaboration) to be engrained in the social infrastructure. This takes time. The technologies that enable SOA’s are available (granted, they have to be adopted, integrated, which also takes time and patience), but don’t underestimate the time it takes for a federated and collaborative process to be adopted.Regarding the technology, the expectation needs to be set (or reset as the case may be) that the changes technically are more likely a three to seven year evolution. Some of the confusion on SOA timing expectation likely came from the traditional notion of installing something “and you’re done”. You don’t “install” an SOA, rather you evolve your architecture and governance process towards it. As I’ve preached before starting small, and taking baby steps is a key to SOA success, and I see a lot of enterprises doing exactly that, which of course is slow, but progressive. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
