<?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; Viktor Grgic</title>
	<atom:link href="http://blog.xebia.com/author/vgrgic/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>ESB as a political thing</title>
		<link>http://blog.xebia.com/2009/10/05/esb-political-thing/</link>
		<comments>http://blog.xebia.com/2009/10/05/esb-political-thing/#comments</comments>
		<pubDate>Mon, 05 Oct 2009 15:11:35 +0000</pubDate>
		<dc:creator>Viktor Grgic</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[Middleware]]></category>
		<category><![CDATA[SOA]]></category>
		<category><![CDATA[esb]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=3222</guid>
		<description><![CDATA[Many have assumption that IT / software architecture is a thing of logic. So, there are many discussions about ESB and that we should not have those. The fact is that in large companies, we do not often do architecture - we do politecture. The politics drive the architecture. It's not the way it should [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/10/05/esb-political-thing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Top 10 SOA Pitfalls: #2 &#8211; Unclear ownership / Project based funding</title>
		<link>http://blog.xebia.com/2008/06/16/top-10-soa-pitfalls-2-unclear-ownership-project-based-funding/</link>
		<comments>http://blog.xebia.com/2008/06/16/top-10-soa-pitfalls-2-unclear-ownership-project-based-funding/#comments</comments>
		<pubDate>Mon, 16 Jun 2008 15:55:06 +0000</pubDate>
		<dc:creator>Viktor Grgic</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[Project Management]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=590</guid>
		<description><![CDATA[Last week Viktor Grgic explained the Missing skills en this week we’ll continue with #2 - Unclear ownership / Project based funding
In the world of standalone applications, there is typically a clear sponsorship and ownership of an application. There is also a single project with one project manager. The systems could be small or big, [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/06/16/top-10-soa-pitfalls-2-unclear-ownership-project-based-funding/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Top 10 SOA Pitfalls: #3 &#8211; Missing skills</title>
		<link>http://blog.xebia.com/2008/06/09/top-10-soa-pitfalls-3-missing-skills/</link>
		<comments>http://blog.xebia.com/2008/06/09/top-10-soa-pitfalls-3-missing-skills/#comments</comments>
		<pubDate>Mon, 09 Jun 2008 06:59:46 +0000</pubDate>
		<dc:creator>Viktor Grgic</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[Agile]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=586</guid>
		<description><![CDATA[Last week Gero Vermaas explained the Incorrectly Applied CDM en this week we’ll continue with #3 - Missing skills
Just like any other paradigm, a level of new knowledge and experience is required. Unfortunately, SOA requires lots of new knowledge and experience. It requires a different way of thinking of more or less everyone involved. People [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/06/09/top-10-soa-pitfalls-3-missing-skills/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Top 10 SOA Pitfalls: #8 &#8211; Security</title>
		<link>http://blog.xebia.com/2008/05/05/top-10-soa-pitfalls-8-security/</link>
		<comments>http://blog.xebia.com/2008/05/05/top-10-soa-pitfalls-8-security/#comments</comments>
		<pubDate>Mon, 05 May 2008 16:07:28 +0000</pubDate>
		<dc:creator>Viktor Grgic</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[SOA]]></category>
		<category><![CDATA[Security]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=514</guid>
		<description><![CDATA[Last week Rik de Groot published the #9: Versioning. This week it's time for #8.
SOA security is like having a well-protected Middle Ages city, but at the same time asking citizens to permit many more people from inside and outside the city into their homes. They would really have hard time properly securing their belongings.
Introduction [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/05/05/top-10-soa-pitfalls-8-security/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Your SOA product choices should be based on the QUINT model</title>
		<link>http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/</link>
		<comments>http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 12:47:01 +0000</pubDate>
		<dc:creator>Viktor Grgic</dc:creator>
				<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<category>quint</category>
	<category>distilled</category>
	<category>stupid</category>
	<category>requirements</category>
	<category>strategy</category>
	<category>model</category>
	<category>supported</category>
	<category>defined</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/</guid>
		<description><![CDATA[It is always about well-defined requirements stupid.   Building or choosing out-of-the-box software products like an ESB within the company's SOA strategy can be very well supported by a number of requirements distilled from the QUINT2 ISO model:
Functionality: Suitability, Interoperability, Compliance, Security, Traceability
Usability: Operability, Customisability
Efficiency: Time Behaviour
Maintainability: Testability, Manageability, Reusability
Portability: Adaptability, Replaceability
This is the [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Conversation about an Agile Architect</title>
		<link>http://blog.xebia.com/2008/01/04/conversation-about-an-agile-architect/</link>
		<comments>http://blog.xebia.com/2008/01/04/conversation-about-an-agile-architect/#comments</comments>
		<pubDate>Fri, 04 Jan 2008 14:21:58 +0000</pubDate>
		<dc:creator>Viktor Grgic</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Architecture]]></category>

	<!-- AutoMeta Start -->
	<category>architect</category>
	<category>strategy</category>
	<category>architecture</category>
	<category>spends</category>
	<category>emerges</category>
	<category>conversation</category>
	<category>aspects</category>
	<category>term</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2008/01/04/conversation-about-an-agile-architect/</guid>
		<description><![CDATA[This is a short and sharp conversation over ICQ between two Xebians about what an Agile Architect is or does. The conclusion is that an Agile Architect has, in addition to Agile manifesto, a number of principles:
- Just-in-time and just-enough architecture
- An architect is a "waste" and has no direct business value.
- An architect should [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2008/01/04/conversation-about-an-agile-architect/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Top 10 recommendations when defining B2B services</title>
		<link>http://blog.xebia.com/2007/04/05/top-10-recommendations-when-defining-b2b-services/</link>
		<comments>http://blog.xebia.com/2007/04/05/top-10-recommendations-when-defining-b2b-services/#comments</comments>
		<pubDate>Wed, 04 Apr 2007 22:06:33 +0000</pubDate>
		<dc:creator>Viktor Grgic</dc:creator>
				<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[SOA]]></category>

	<!-- AutoMeta Start -->
	<category>consumers</category>
	<category>consumers</category>
	<category>acknowledgment</category>
	<category>ubiquitous</category>
	<category>details</category>
	<category>details</category>
	<category>template</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2007/04/05/top-10-recommendations-when-defining-b2b-services/</guid>
		<description><![CDATA[Requirements engineering and design of services that your company need to provide to other companies is quite different from reqs. engineering for an interactive website, or other systems where an actor is a real person. In case of B2B services, the actor is always another system. Mostly you also know who your actors / other [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2007/04/05/top-10-recommendations-when-defining-b2b-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dispose of problem instead of solving</title>
		<link>http://blog.xebia.com/2006/07/14/dispose-of-problem-instead-of-solving/</link>
		<comments>http://blog.xebia.com/2006/07/14/dispose-of-problem-instead-of-solving/#comments</comments>
		<pubDate>Fri, 14 Jul 2006 14:32:00 +0000</pubDate>
		<dc:creator>Viktor Grgic</dc:creator>
				<category><![CDATA[General]]></category>

	<!-- AutoMeta Start -->
	<category>money</category>
	<category>involved</category>
	<category>experts</category>
	<category>technical</category>
	<category>experienced</category>
	<category>problems</category>
	<category>address</category>
	<category>courage</category>
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/2006/07/14/dispose-of-problem-instead-of-solving/</guid>
		<description><![CDATA[Technical experts are often hired to fix some problem which hasn't been solved after spending huge amounts of time and money. An example could be trying to integrate legacy code with an object-oriented environment. The expert will typically try to address all mentioned problems. He uses his knowledge and experience to approach the problem in [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2006/07/14/dispose-of-problem-instead-of-solving/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
