<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Xebia Blog &#187; Rik de Groot</title>
	<atom:link href="http://blog.xebia.com/author/rdegroot/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com</link>
	<description></description>
	<lastBuildDate>Wed, 10 Mar 2010 08:24:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Top 10 SOA Pitfalls: #1 &#8211; Ignoring culture when introducing SOA</title>
		<link>http://blog.xebia.com/2008/06/23/top-10-soa-pitfalls-1-ignoring-culture-when-introducing-soa/</link>
		<comments>http://blog.xebia.com/2008/06/23/top-10-soa-pitfalls-1-ignoring-culture-when-introducing-soa/#comments</comments>
		<pubDate>Mon, 23 Jun 2008 11:17:57 +0000</pubDate>
		<dc:creator>Rik de Groot</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=610</guid>
		<description><![CDATA[Last week Viktor Grgic explained Unclear ownership / Project based funding. This week we’ll continue with #1 - Ignoring culture when introducing SOA.
SOA is an approach. The culture aspect of introducing a SOA is important, but it seems that companies want to invest in tools and not in people. In order of making this SOA [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/06/23/top-10-soa-pitfalls-1-ignoring-culture-when-introducing-soa/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Top 10 SOA Pitfalls: #6 &#8211; SOA does not solve complexity automatically</title>
		<link>http://blog.xebia.com/2008/05/19/top-10-soa-pitfalls-6-soa-does-not-solve-complexity-automatically/</link>
		<comments>http://blog.xebia.com/2008/05/19/top-10-soa-pitfalls-6-soa-does-not-solve-complexity-automatically/#comments</comments>
		<pubDate>Mon, 19 May 2008 21:52:35 +0000</pubDate>
		<dc:creator>Rik de Groot</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=564</guid>
		<description><![CDATA[After discussing #7: Incorrect granularity of services , let's move on to #6.
In organizations data and functionality/processes are often fragmented, but are needed centrally. What are the causes of this fragmentation. Does a SOA solve this complexity automatically? Most companies start with a SOA and are confronted with this complexity during the implementation of the [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/05/19/top-10-soa-pitfalls-6-soa-does-not-solve-complexity-automatically/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Top 10 SOA Pitfalls: #9 – Versioning</title>
		<link>http://blog.xebia.com/2008/04/29/top-10-soa-pitfalls-9-%e2%80%93-versioning/</link>
		<comments>http://blog.xebia.com/2008/04/29/top-10-soa-pitfalls-9-%e2%80%93-versioning/#comments</comments>
		<pubDate>Tue, 29 Apr 2008 09:28:12 +0000</pubDate>
		<dc:creator>Rik de Groot</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=512</guid>
		<description><![CDATA[Last week we started the Top 10 SOA Pitfalls countdown with #10: NIH syndrome. This week it's time for #9.
Version mismatch is one of the growing pains of a SOA. A SOA starts simple, but after a while new versions of services will appear and the complexity will grow. Good life cycle management and supporting [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/04/29/top-10-soa-pitfalls-9-%e2%80%93-versioning/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Does a personality type matter?</title>
		<link>http://blog.xebia.com/2007/12/12/does-a-personality-type-matter/</link>
		<comments>http://blog.xebia.com/2007/12/12/does-a-personality-type-matter/#comments</comments>
		<pubDate>Wed, 12 Dec 2007 21:40:13 +0000</pubDate>
		<dc:creator>Rik de Groot</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[General]]></category>

	<!-- AutoMeta Start -->
	<category>personality</category>
	<category>comfortable</category>
	<category>knowing</category>
	<category>preferences</category>
	<category>tick</category>
	<category>complement</category>
	<category>entrance</category>
	<category>energy</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2007/12/12/does-a-personality-type-matter/</guid>
		<description><![CDATA[A good team can make or break the success of a project. Where does this success come from? Is it the way of cooperation or is it the mixture of the right personality types in a team? Do you pick the right personalities and make them work together or does it happen naturally?  
Different [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2007/12/12/does-a-personality-type-matter/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>EssUP, the practice centric software development process</title>
		<link>http://blog.xebia.com/2007/04/26/essup-the-practice-centric-software-development-process/</link>
		<comments>http://blog.xebia.com/2007/04/26/essup-the-practice-centric-software-development-process/#comments</comments>
		<pubDate>Thu, 26 Apr 2007 18:24:35 +0000</pubDate>
		<dc:creator>Rik de Groot</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[General]]></category>

	<!-- AutoMeta Start -->
	<category>essup</category>
	<category>ivar</category>
	<category>esswork</category>
	<category>generations</category>
	<category>unified</category>
	<category>practices</category>
	<category>lightweight</category>
	<category>scrum</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2007/04/26/essup-the-practice-centric-software-development-process/</guid>
		<description><![CDATA[We don't like RUP, let's do practices. Last week Ivar Jacobson (the father of the Use Cases and the Unified Process) was in the Netherlands spreading the word of the Essential Unified Process (EssUp). EssUp (http://www.ivarjacobson.com/essup.cfm) provides a fresh approach to software process improvement and claims to be a new “Practice” centric software development process.

Practices
Ivar [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2007/04/26/essup-the-practice-centric-software-development-process/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
