<?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 on: Why Does SOA Need Strong Program Management Capability?</title>
	<atom:link href="http://www.ryoungman.net/?feed=rss2&#038;p=9" rel="self" type="application/rss+xml" />
	<link>http://www.ryoungman.net/?p=9</link>
	<description>The Evolution of IT in creating Business Value</description>
	<lastBuildDate>Wed, 28 Jul 2010 11:45:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IT Service Management vs. IT Product Management &#171; IT Organization Circa 2017</title>
		<link>http://www.ryoungman.net/?p=9&#038;cpage=1#comment-27</link>
		<dc:creator>IT Service Management vs. IT Product Management &#171; IT Organization Circa 2017</dc:creator>
		<pubDate>Mon, 21 Jan 2008 11:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryoungman.net/?p=9#comment-27</guid>
		<description>[...] and to business-IT maturity.  This thread is inspired in part by my colleague Roy Youngman&#8217;s post on Program Management and SOA and also addressed an issue that comes up from time-to-time in my client [...]</description>
		<content:encoded><![CDATA[<p>[...] and to business-IT maturity.  This thread is inspired in part by my colleague Roy Youngman&#8217;s post on Program Management and SOA and also addressed an issue that comes up from time-to-time in my client [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brittain</title>
		<link>http://www.ryoungman.net/?p=9&#038;cpage=1#comment-26</link>
		<dc:creator>Brittain</dc:creator>
		<pubDate>Tue, 08 Jan 2008 16:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryoungman.net/?p=9#comment-26</guid>
		<description>Good post Roy.&#160; For enterprises I completely agree with your core argument.&#160; On the topic of service design, I&#039;ve a couple thoughts drawn from recent experience and what I&#039;ve been seeing with Web 2.0:We&#039;re seeing a resurgance in web services built to &quot;be conservative in what you do and liberal in what you accept from others&quot;.&#160; This age old principle is the core of the modern mashup.REST-based architectures and syndication protocols (RSS, Atom, etc)&#160;emphasize &quot;data creating&quot; services over the &quot;action performing&quot; services we saw with SOAP or RPC-style architectures.
Taken together these two trends make it easier for the service designer to &quot;accidentally&quot; achieve reuse.&#160; By being forgiving (#1) and returning data streams (#2) we allow easier recombination under unanticipated scenarios.&#160; 
In contrast, service design previously emphasized tight contracts and atomic actions.&#160; This forced the service designer to&#160;anticipate future usages and subsequently&#160;broaden or extend the service API footprint&#160;correspondingly.&#160;&#160;This eliminates accidental reuse.&#160;&#160;&#160;
&#160;
This conversation continues at &lt;a href=&quot;http://www.bsgalliance.com/convs/show/2143&quot; rel=&quot;nofollow&quot;&gt;BSG Alliance&lt;/a&gt;
&#160;
Brittain
&lt;a href=&quot;http://www.bsgalliance.com/account/profile/11&quot; rel=&quot;nofollow&quot;&gt;View My Profile&lt;/a&gt;
Managing Director, Applications Team
BSG Alliance</description>
		<content:encoded><![CDATA[<p>Good post Roy.&nbsp; For enterprises I completely agree with your core argument.&nbsp; On the topic of service design, I&#8217;ve a couple thoughts drawn from recent experience and what I&#8217;ve been seeing with Web 2.0:We&#8217;re seeing a resurgance in web services built to &quot;be conservative in what you do and liberal in what you accept from others&quot;.&nbsp; This age old principle is the core of the modern mashup.REST-based architectures and syndication protocols (RSS, Atom, etc)&nbsp;emphasize &quot;data creating&quot; services over the &quot;action performing&quot; services we saw with SOAP or RPC-style architectures.<br />
Taken together these two trends make it easier for the service designer to &quot;accidentally&quot; achieve reuse.&nbsp; By being forgiving (#1) and returning data streams (#2) we allow easier recombination under unanticipated scenarios.&nbsp;<br />
In contrast, service design previously emphasized tight contracts and atomic actions.&nbsp; This forced the service designer to&nbsp;anticipate future usages and subsequently&nbsp;broaden or extend the service API footprint&nbsp;correspondingly.&nbsp;&nbsp;This eliminates accidental reuse.&nbsp;&nbsp;&nbsp;<br />
&nbsp;<br />
This conversation continues at <a href="http://www.bsgalliance.com/convs/show/2143" rel="nofollow">BSG Alliance</a><br />
&nbsp;<br />
Brittain<br />
<a href="http://www.bsgalliance.com/account/profile/11" rel="nofollow">View My Profile</a><br />
Managing Director, Applications Team<br />
BSG Alliance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaughan Merlyn</title>
		<link>http://www.ryoungman.net/?p=9&#038;cpage=1#comment-25</link>
		<dc:creator>Vaughan Merlyn</dc:creator>
		<pubDate>Tue, 08 Jan 2008 15:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryoungman.net/?p=9#comment-25</guid>
		<description>Excellent points - thanks for clarifying the connection between SOA and Program Management.  I think that implied in your points are also connections to Service Management (which is inherent in Service Oriented Anything) and Product Management which is a discipline I&#039;ve long felt is needed by IT organizations, but that few seem to understand or invest in.</description>
		<content:encoded><![CDATA[<p>Excellent points &#8211; thanks for clarifying the connection between SOA and Program Management.  I think that implied in your points are also connections to Service Management (which is inherent in Service Oriented Anything) and Product Management which is a discipline I&#8217;ve long felt is needed by IT organizations, but that few seem to understand or invest in.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
