<?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: How do we get business and IT to play on the same team?</title>
	<atom:link href="http://blog.ivarjacobson.com/how-do-we-get-business-and-it-to-play-on-the-same-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ivarjacobson.com/how-do-we-get-business-and-it-to-play-on-the-same-team/</link>
	<description>The Smart Blog</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:21:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Chris Gerrard</title>
		<link>http://blog.ivarjacobson.com/how-do-we-get-business-and-it-to-play-on-the-same-team/comment-page-1/#comment-340</link>
		<dc:creator>Chris Gerrard</dc:creator>
		<pubDate>Tue, 16 Mar 2010 20:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ivarjacobson.com/?p=209#comment-340</guid>
		<description>I quite like the analogy, and the extrapolations. Particularly the framing of software development as a commodity activity best undertaken by the lowest-cost factors of production. History clearly shows that saving money by using the lowest-cost developers simply lowers the cost of failure - an organization that has this view of development -will- fail, but it&#039;ll spend less money doing so.

There&#039;s another facet that comes into play. The rewards and promotions tend to go to those who can promise shiny baubles and declare success in the face of failure. This character trait is fundamentally opposed to the nature of someone who is actually good at software development, which requires a dedicated pursuit of the good, useful, and valuable. Organizations that reward self-promoters over accomplished professionals, particularly those effective collaborators whose contributions magnify those of their colleagues, end up with team captains and coaches who drive the team towards the bottom. But, unlike real sports teams, there is no objective measure of success or failure - wins and losses - to assess the team&#039;s real effectiveness.</description>
		<content:encoded><![CDATA[<p>I quite like the analogy, and the extrapolations. Particularly the framing of software development as a commodity activity best undertaken by the lowest-cost factors of production. History clearly shows that saving money by using the lowest-cost developers simply lowers the cost of failure &#8211; an organization that has this view of development -will- fail, but it&#8217;ll spend less money doing so.</p>
<p>There&#8217;s another facet that comes into play. The rewards and promotions tend to go to those who can promise shiny baubles and declare success in the face of failure. This character trait is fundamentally opposed to the nature of someone who is actually good at software development, which requires a dedicated pursuit of the good, useful, and valuable. Organizations that reward self-promoters over accomplished professionals, particularly those effective collaborators whose contributions magnify those of their colleagues, end up with team captains and coaches who drive the team towards the bottom. But, unlike real sports teams, there is no objective measure of success or failure &#8211; wins and losses &#8211; to assess the team&#8217;s real effectiveness.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

