<?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: One Million Dollars or One Year</title>
	<atom:link href="http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year/feed" rel="self" type="application/rss+xml" />
	<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Thu, 06 Nov 2014 02:53:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.41</generator>
	<item>
		<title>By: Kris Kelso</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-499</link>
		<dc:creator><![CDATA[Kris Kelso]]></dc:creator>
		<pubDate>Thu, 25 Feb 2010 15:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-499</guid>
		<description><![CDATA[Chris - I&#039;ve just stumbled across your blog, and this is a great review and sounds like a great book.  I think that too many people are in search of the &quot;perfect&quot; answer to common problems such as PPM, organizational structure, process improvement, and service delivery.  These are all areas where there is no &quot;destination&quot; - just a journey of continuous improvement and adaptation.  No goal is an end goal - every goal is a milestone on the journey.

I will definitely add this one to my reading list.  Thanks.]]></description>
		<content:encoded><![CDATA[<p>Chris &#8211; I&#8217;ve just stumbled across your blog, and this is a great review and sounds like a great book.  I think that too many people are in search of the &#8220;perfect&#8221; answer to common problems such as PPM, organizational structure, process improvement, and service delivery.  These are all areas where there is no &#8220;destination&#8221; &#8211; just a journey of continuous improvement and adaptation.  No goal is an end goal &#8211; every goal is a milestone on the journey.</p>
<p>I will definitely add this one to my reading list.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Kelso</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-503</link>
		<dc:creator><![CDATA[Kris Kelso]]></dc:creator>
		<pubDate>Thu, 25 Feb 2010 15:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-503</guid>
		<description><![CDATA[Chris - I&#039;ve just stumbled across your blog, and this is a great review and sounds like a great book.  I think that too many people are in search of the &quot;perfect&quot; answer to common problems such as PPM, organizational structure, process improvement, and service delivery.  These are all areas where there is no &quot;destination&quot; - just a journey of continuous improvement and adaptation.  No goal is an end goal - every goal is a milestone on the journey.

I will definitely add this one to my reading list.  Thanks.]]></description>
		<content:encoded><![CDATA[<p>Chris &#8211; I&#8217;ve just stumbled across your blog, and this is a great review and sounds like a great book.  I think that too many people are in search of the &#8220;perfect&#8221; answer to common problems such as PPM, organizational structure, process improvement, and service delivery.  These are all areas where there is no &#8220;destination&#8221; &#8211; just a journey of continuous improvement and adaptation.  No goal is an end goal &#8211; every goal is a milestone on the journey.</p>
<p>I will definitely add this one to my reading list.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joanne</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-498</link>
		<dc:creator><![CDATA[joanne]]></dc:creator>
		<pubDate>Thu, 07 Jan 2010 01:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-498</guid>
		<description><![CDATA[So you can disqualify my comments if you like, I&#039;m a vendor, but what I have seen is that just giving a CIO visibility into where resources are, how much things are costing and giving him the ability to make smart choices when under pressure or resources are constrained is 50% of the battle.  Of course you will see through me right away and know I&#039;m trying to position Clarity PPM for IT, but the point is Clarity or whatever, seeing what&#039;s going on is so incredibly important to informed decision making and any governance process, it would surprise me if they don&#039;t have such a tool or contemplating one.  But money is tight and PPM costs bucks and its a luxury right now, not a must have.  Here I say, nope...PPM has incredible tangible benefits.  Let me tell you a quick story:  Pharma CIO in LA was called up by his CEO and told, cut 20M out of the budget now.  CIO was completely freaked out because he had just let hundreds of people go and was down to the bone.  So he pulled up his brand new Clarity dashboard, figured out what was absolutely essential and what wasn&#039;t, killed 6 projects and found the 20M.  Now does that sound like a nice to have luxury tool.  Absolutely not.  In fact our studies from MIT have shown that proper ITG in general have dramatic impacts on the overall profitability of a company.  Failed projects are the worst.  I used to be in IT, and I can tell you, everyone from IT to business hated that feeling.  Anyway, that&#039;s my story.  Visibility is empowerment and gives the CIO&#039;s the decision support they need.  Hope that wasn&#039;t too &quot;salesy&quot;, but I&#039;m pretty passionate about helping customers.  And this one in particular was very gratifying.  Joanne]]></description>
		<content:encoded><![CDATA[<p>So you can disqualify my comments if you like, I&#8217;m a vendor, but what I have seen is that just giving a CIO visibility into where resources are, how much things are costing and giving him the ability to make smart choices when under pressure or resources are constrained is 50% of the battle.  Of course you will see through me right away and know I&#8217;m trying to position Clarity PPM for IT, but the point is Clarity or whatever, seeing what&#8217;s going on is so incredibly important to informed decision making and any governance process, it would surprise me if they don&#8217;t have such a tool or contemplating one.  But money is tight and PPM costs bucks and its a luxury right now, not a must have.  Here I say, nope&#8230;PPM has incredible tangible benefits.  Let me tell you a quick story:  Pharma CIO in LA was called up by his CEO and told, cut 20M out of the budget now.  CIO was completely freaked out because he had just let hundreds of people go and was down to the bone.  So he pulled up his brand new Clarity dashboard, figured out what was absolutely essential and what wasn&#8217;t, killed 6 projects and found the 20M.  Now does that sound like a nice to have luxury tool.  Absolutely not.  In fact our studies from MIT have shown that proper ITG in general have dramatic impacts on the overall profitability of a company.  Failed projects are the worst.  I used to be in IT, and I can tell you, everyone from IT to business hated that feeling.  Anyway, that&#8217;s my story.  Visibility is empowerment and gives the CIO&#8217;s the decision support they need.  Hope that wasn&#8217;t too &#8220;salesy&#8221;, but I&#8217;m pretty passionate about helping customers.  And this one in particular was very gratifying.  Joanne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joanne</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-502</link>
		<dc:creator><![CDATA[joanne]]></dc:creator>
		<pubDate>Thu, 07 Jan 2010 01:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-502</guid>
		<description><![CDATA[So you can disqualify my comments if you like, I&#039;m a vendor, but what I have seen is that just giving a CIO visibility into where resources are, how much things are costing and giving him the ability to make smart choices when under pressure or resources are constrained is 50% of the battle.  Of course you will see through me right away and know I&#039;m trying to position Clarity PPM for IT, but the point is Clarity or whatever, seeing what&#039;s going on is so incredibly important to informed decision making and any governance process, it would surprise me if they don&#039;t have such a tool or contemplating one.  But money is tight and PPM costs bucks and its a luxury right now, not a must have.  Here I say, nope...PPM has incredible tangible benefits.  Let me tell you a quick story:  Pharma CIO in LA was called up by his CEO and told, cut 20M out of the budget now.  CIO was completely freaked out because he had just let hundreds of people go and was down to the bone.  So he pulled up his brand new Clarity dashboard, figured out what was absolutely essential and what wasn&#039;t, killed 6 projects and found the 20M.  Now does that sound like a nice to have luxury tool.  Absolutely not.  In fact our studies from MIT have shown that proper ITG in general have dramatic impacts on the overall profitability of a company.  Failed projects are the worst.  I used to be in IT, and I can tell you, everyone from IT to business hated that feeling.  Anyway, that&#039;s my story.  Visibility is empowerment and gives the CIO&#039;s the decision support they need.  Hope that wasn&#039;t too &quot;salesy&quot;, but I&#039;m pretty passionate about helping customers.  And this one in particular was very gratifying.  Joanne]]></description>
		<content:encoded><![CDATA[<p>So you can disqualify my comments if you like, I&#8217;m a vendor, but what I have seen is that just giving a CIO visibility into where resources are, how much things are costing and giving him the ability to make smart choices when under pressure or resources are constrained is 50% of the battle.  Of course you will see through me right away and know I&#8217;m trying to position Clarity PPM for IT, but the point is Clarity or whatever, seeing what&#8217;s going on is so incredibly important to informed decision making and any governance process, it would surprise me if they don&#8217;t have such a tool or contemplating one.  But money is tight and PPM costs bucks and its a luxury right now, not a must have.  Here I say, nope&#8230;PPM has incredible tangible benefits.  Let me tell you a quick story:  Pharma CIO in LA was called up by his CEO and told, cut 20M out of the budget now.  CIO was completely freaked out because he had just let hundreds of people go and was down to the bone.  So he pulled up his brand new Clarity dashboard, figured out what was absolutely essential and what wasn&#8217;t, killed 6 projects and found the 20M.  Now does that sound like a nice to have luxury tool.  Absolutely not.  In fact our studies from MIT have shown that proper ITG in general have dramatic impacts on the overall profitability of a company.  Failed projects are the worst.  I used to be in IT, and I can tell you, everyone from IT to business hated that feeling.  Anyway, that&#8217;s my story.  Visibility is empowerment and gives the CIO&#8217;s the decision support they need.  Hope that wasn&#8217;t too &#8220;salesy&#8221;, but I&#8217;m pretty passionate about helping customers.  And this one in particular was very gratifying.  Joanne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike McClure</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-497</link>
		<dc:creator><![CDATA[Mike McClure]]></dc:creator>
		<pubDate>Wed, 09 Dec 2009 22:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-497</guid>
		<description><![CDATA[My experience with the inner workings of IT departments in large organisations is, sadly, well in line with your excerpts from this book.

Part of the problem is project governance. Don&#039;t get me wrong, I am a very vocal supporter of formal governance - it&#039;s just that there are not usually *appropriate* levels of governance around IT in large organisations.
What I have observed are the startup costs (forming committees, lobbying for executive approval, and other such formalities) combined with delivery costs (arm&#039;s length handover to the outsourcer, user training, and sufficient documentation) mean that no project of significance can be completed in under 6 months. In terms of time, the actual build phase is often under 25% of the total project duration when you consider the time from idea inception to production deployment.

Another part of this problem is on the cash side of the equation. Each organisation has what I call a &quot;terminal velocity&quot; for project expenditure. No matter how things are scaled up, the amount of change that can be implemented flatlines after a certain expenditure. Increasing the project size beyond the terminal velocity doesn&#039;t actually net any extra speed.

I have found that organisations are often aware of the inadequacies of their project governance arrangements but are unable to see how they can change them (&quot;too hard&quot;) or are unwilling to challenge them (&quot;it&#039;s always been done this way&quot;).
I have not found many organisations who are aware of their terminal velocity, despite having a lot of evidence from previous projects.

However when I point out that, historically, projects over a certain size tend to be considered failures within the organisation, people are often amazed that they had not noticed that trend before and are now open to new ideas.
The root causes of this terminal velocity are often hard to change but armed with the awareness, projects can be kept under this danger threshold.]]></description>
		<content:encoded><![CDATA[<p>My experience with the inner workings of IT departments in large organisations is, sadly, well in line with your excerpts from this book.</p>
<p>Part of the problem is project governance. Don&#8217;t get me wrong, I am a very vocal supporter of formal governance &#8211; it&#8217;s just that there are not usually *appropriate* levels of governance around IT in large organisations.<br />
What I have observed are the startup costs (forming committees, lobbying for executive approval, and other such formalities) combined with delivery costs (arm&#8217;s length handover to the outsourcer, user training, and sufficient documentation) mean that no project of significance can be completed in under 6 months. In terms of time, the actual build phase is often under 25% of the total project duration when you consider the time from idea inception to production deployment.</p>
<p>Another part of this problem is on the cash side of the equation. Each organisation has what I call a &#8220;terminal velocity&#8221; for project expenditure. No matter how things are scaled up, the amount of change that can be implemented flatlines after a certain expenditure. Increasing the project size beyond the terminal velocity doesn&#8217;t actually net any extra speed.</p>
<p>I have found that organisations are often aware of the inadequacies of their project governance arrangements but are unable to see how they can change them (&#8220;too hard&#8221;) or are unwilling to challenge them (&#8220;it&#8217;s always been done this way&#8221;).<br />
I have not found many organisations who are aware of their terminal velocity, despite having a lot of evidence from previous projects.</p>
<p>However when I point out that, historically, projects over a certain size tend to be considered failures within the organisation, people are often amazed that they had not noticed that trend before and are now open to new ideas.<br />
The root causes of this terminal velocity are often hard to change but armed with the awareness, projects can be kept under this danger threshold.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike McClure</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-501</link>
		<dc:creator><![CDATA[Mike McClure]]></dc:creator>
		<pubDate>Wed, 09 Dec 2009 22:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-501</guid>
		<description><![CDATA[My experience with the inner workings of IT departments in large organisations is, sadly, well in line with your excerpts from this book.

Part of the problem is project governance. Don&#039;t get me wrong, I am a very vocal supporter of formal governance - it&#039;s just that there are not usually *appropriate* levels of governance around IT in large organisations.
What I have observed are the startup costs (forming committees, lobbying for executive approval, and other such formalities) combined with delivery costs (arm&#039;s length handover to the outsourcer, user training, and sufficient documentation) mean that no project of significance can be completed in under 6 months. In terms of time, the actual build phase is often under 25% of the total project duration when you consider the time from idea inception to production deployment.

Another part of this problem is on the cash side of the equation. Each organisation has what I call a &quot;terminal velocity&quot; for project expenditure. No matter how things are scaled up, the amount of change that can be implemented flatlines after a certain expenditure. Increasing the project size beyond the terminal velocity doesn&#039;t actually net any extra speed.

I have found that organisations are often aware of the inadequacies of their project governance arrangements but are unable to see how they can change them (&quot;too hard&quot;) or are unwilling to challenge them (&quot;it&#039;s always been done this way&quot;).
I have not found many organisations who are aware of their terminal velocity, despite having a lot of evidence from previous projects.

However when I point out that, historically, projects over a certain size tend to be considered failures within the organisation, people are often amazed that they had not noticed that trend before and are now open to new ideas.
The root causes of this terminal velocity are often hard to change but armed with the awareness, projects can be kept under this danger threshold.]]></description>
		<content:encoded><![CDATA[<p>My experience with the inner workings of IT departments in large organisations is, sadly, well in line with your excerpts from this book.</p>
<p>Part of the problem is project governance. Don&#8217;t get me wrong, I am a very vocal supporter of formal governance &#8211; it&#8217;s just that there are not usually *appropriate* levels of governance around IT in large organisations.<br />
What I have observed are the startup costs (forming committees, lobbying for executive approval, and other such formalities) combined with delivery costs (arm&#8217;s length handover to the outsourcer, user training, and sufficient documentation) mean that no project of significance can be completed in under 6 months. In terms of time, the actual build phase is often under 25% of the total project duration when you consider the time from idea inception to production deployment.</p>
<p>Another part of this problem is on the cash side of the equation. Each organisation has what I call a &#8220;terminal velocity&#8221; for project expenditure. No matter how things are scaled up, the amount of change that can be implemented flatlines after a certain expenditure. Increasing the project size beyond the terminal velocity doesn&#8217;t actually net any extra speed.</p>
<p>I have found that organisations are often aware of the inadequacies of their project governance arrangements but are unable to see how they can change them (&#8220;too hard&#8221;) or are unwilling to challenge them (&#8220;it&#8217;s always been done this way&#8221;).<br />
I have not found many organisations who are aware of their terminal velocity, despite having a lot of evidence from previous projects.</p>
<p>However when I point out that, historically, projects over a certain size tend to be considered failures within the organisation, people are often amazed that they had not noticed that trend before and are now open to new ideas.<br />
The root causes of this terminal velocity are often hard to change but armed with the awareness, projects can be kept under this danger threshold.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kretzman</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-496</link>
		<dc:creator><![CDATA[Peter Kretzman]]></dc:creator>
		<pubDate>Wed, 09 Dec 2009 19:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-496</guid>
		<description><![CDATA[IT&#039;s inner workings? The recurring one, for me, has to be hearing &quot;we don&#039;t like that estimate&quot;, coming from stakeholders, senior management, etc. Depending on the mood and/or semi-intellectual rigor of the person saying it, the conversation then typically devolves into one or more of the following: a) identifying and removing any hint of contingency (which is of course seen as padding just to make life easier for IT); b) repeated discussion of &quot;what if we double the team size to get it done twice as fast&quot; etc.; c) scrutiny, one by one, of the bottom-up estimates (&quot;it won&#039;t REALLY take three days to test THAT feature&quot;); d) volunteering resources (usually less than qualified) to &quot;help&quot;; e) scheduling full-time work for all remaining weekends and holidays between now and the desired launch; f) frequent use of the phrase &quot;why don&#039;t you just ...&quot;

This is not an exaggeration.  It rests on the CIO&#039;s shoulders most of all to cut these &quot;solutions&quot; off at the pass.]]></description>
		<content:encoded><![CDATA[<p>IT&#8217;s inner workings? The recurring one, for me, has to be hearing &#8220;we don&#8217;t like that estimate&#8221;, coming from stakeholders, senior management, etc. Depending on the mood and/or semi-intellectual rigor of the person saying it, the conversation then typically devolves into one or more of the following: a) identifying and removing any hint of contingency (which is of course seen as padding just to make life easier for IT); b) repeated discussion of &#8220;what if we double the team size to get it done twice as fast&#8221; etc.; c) scrutiny, one by one, of the bottom-up estimates (&#8220;it won&#8217;t REALLY take three days to test THAT feature&#8221;); d) volunteering resources (usually less than qualified) to &#8220;help&#8221;; e) scheduling full-time work for all remaining weekends and holidays between now and the desired launch; f) frequent use of the phrase &#8220;why don&#8217;t you just &#8230;&#8221;</p>
<p>This is not an exaggeration.  It rests on the CIO&#8217;s shoulders most of all to cut these &#8220;solutions&#8221; off at the pass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kretzman</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-500</link>
		<dc:creator><![CDATA[Peter Kretzman]]></dc:creator>
		<pubDate>Wed, 09 Dec 2009 19:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-500</guid>
		<description><![CDATA[IT&#039;s inner workings? The recurring one, for me, has to be hearing &quot;we don&#039;t like that estimate&quot;, coming from stakeholders, senior management, etc. Depending on the mood and/or semi-intellectual rigor of the person saying it, the conversation then typically devolves into one or more of the following: a) identifying and removing any hint of contingency (which is of course seen as padding just to make life easier for IT); b) repeated discussion of &quot;what if we double the team size to get it done twice as fast&quot; etc.; c) scrutiny, one by one, of the bottom-up estimates (&quot;it won&#039;t REALLY take three days to test THAT feature&quot;); d) volunteering resources (usually less than qualified) to &quot;help&quot;; e) scheduling full-time work for all remaining weekends and holidays between now and the desired launch; f) frequent use of the phrase &quot;why don&#039;t you just ...&quot;

This is not an exaggeration.  It rests on the CIO&#039;s shoulders most of all to cut these &quot;solutions&quot; off at the pass.]]></description>
		<content:encoded><![CDATA[<p>IT&#8217;s inner workings? The recurring one, for me, has to be hearing &#8220;we don&#8217;t like that estimate&#8221;, coming from stakeholders, senior management, etc. Depending on the mood and/or semi-intellectual rigor of the person saying it, the conversation then typically devolves into one or more of the following: a) identifying and removing any hint of contingency (which is of course seen as padding just to make life easier for IT); b) repeated discussion of &#8220;what if we double the team size to get it done twice as fast&#8221; etc.; c) scrutiny, one by one, of the bottom-up estimates (&#8220;it won&#8217;t REALLY take three days to test THAT feature&#8221;); d) volunteering resources (usually less than qualified) to &#8220;help&#8221;; e) scheduling full-time work for all remaining weekends and holidays between now and the desired launch; f) frequent use of the phrase &#8220;why don&#8217;t you just &#8230;&#8221;</p>
<p>This is not an exaggeration.  It rests on the CIO&#8217;s shoulders most of all to cut these &#8220;solutions&#8221; off at the pass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-495</link>
		<dc:creator><![CDATA[uberVU - social comments]]></dc:creator>
		<pubDate>Thu, 03 Dec 2009 19:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-495</guid>
		<description><![CDATA[&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by cbcurran: Book Review: IT&#039;s Hidden Face by Claude Roeltgen (pls RT - free book for top comments!) #CIO http://bit.ly/5HlU4p...]]></description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by cbcurran: Book Review: IT&#8217;s Hidden Face by Claude Roeltgen (pls RT &#8211; free book for top comments!) #CIO <a href="http://bit.ly/5HlU4p" rel="nofollow">http://bit.ly/5HlU4p</a>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention CIO Book Review &#124; ITs Hidden Face &#124; Claude Roeltgen â€” CIO Dashboard -- Topsy.com</title>
		<link>http://rocketpanther.com/ciostage/book-review/one-million-dollars-or-one-year#comment-494</link>
		<dc:creator><![CDATA[Tweets that mention CIO Book Review &#124; ITs Hidden Face &#124; Claude Roeltgen â€” CIO Dashboard -- Topsy.com]]></dc:creator>
		<pubDate>Wed, 02 Dec 2009 19:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciodashboard.com/?p=1589#comment-494</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by Chris Curran, Elliot Ross. Elliot Ross said: RT @cbcurran: Book Review: IT&#039;s Hidden Face by Claude Roeltgen (pls RT - free book for top comments!) #CIO http://bit.ly/5HlU4p [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] This post was mentioned on Twitter by Chris Curran, Elliot Ross. Elliot Ross said: RT @cbcurran: Book Review: IT&#39;s Hidden Face by Claude Roeltgen (pls RT &#8211; free book for top comments!) #CIO <a href="http://bit.ly/5HlU4p" rel="nofollow">http://bit.ly/5HlU4p</a> [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
