<?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: The business case 1 – myths and misunderstandings</title>
	<atom:link href="http://www.totallyoptimizedprojects.com/blog/2009/09/the-business-case-1-%e2%80%93-myths-and-misunderstandings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.totallyoptimizedprojects.com/blog/2009/09/the-business-case-1-%e2%80%93-myths-and-misunderstandings/</link>
	<description>How to deliver more projects and more value in less time and for less cost</description>
	<lastBuildDate>Mon, 21 Nov 2011 00:16:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: marc lachance</title>
		<link>http://www.totallyoptimizedprojects.com/blog/2009/09/the-business-case-1-%e2%80%93-myths-and-misunderstandings/comment-page-1/#comment-756</link>
		<dc:creator>marc lachance</dc:creator>
		<pubDate>Wed, 16 Sep 2009 20:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.valuedeliverymanagement.com/blog/?p=595#comment-756</guid>
		<description>Perhaps part of the problem is the fact that IT often does not recognize what a contract is.  I have seen many cases where IT &quot;contracts&quot; to delivery something, but there is no statement of what the client must do for success.  The success of the project is dependent on the role the business plays.  When the business case only describes one side of the contract, it&#039;s no wonder that IT thinks it has delivered, yet the business is dissatisfied.  The same thing is often true of the project plan.

I like the idea of seeing it as a strategy rather than a contract.  This would help focus it on business value rather than financials (costs).</description>
		<content:encoded><![CDATA[<p>Perhaps part of the problem is the fact that IT often does not recognize what a contract is.  I have seen many cases where IT &#8220;contracts&#8221; to delivery something, but there is no statement of what the client must do for success.  The success of the project is dependent on the role the business plays.  When the business case only describes one side of the contract, it&#8217;s no wonder that IT thinks it has delivered, yet the business is dissatisfied.  The same thing is often true of the project plan.</p>
<p>I like the idea of seeing it as a strategy rather than a contract.  This would help focus it on business value rather than financials (costs).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

