<?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: Ideas for BI POCs</title>
	<atom:link href="http://www.dbms2.com/2009/03/02/ideas-for-bi-pocs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2009/03/02/ideas-for-bi-pocs/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Wed, 08 Feb 2012 22:51:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Kevin Spurway</title>
		<link>http://www.dbms2.com/2009/03/02/ideas-for-bi-pocs/#comment-111951</link>
		<dc:creator>Kevin Spurway</dc:creator>
		<pubDate>Tue, 03 Mar 2009 04:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=711#comment-111951</guid>
		<description>Thanks for the comments. I think we&#039;re agreed on the value of POCs.

My intent wasn&#039;t to suggest that organizations limit themselves to one day &quot;toy&quot; POCs. Ultimately, there’s no point in running a POC if the results don’t help establish that vendor’s ability to deliver on a broader project. So it’s essential that the POC not be a toy, whether it takes a day or a few weeks.

Here&#039;s what I wrote:

&quot;Operate on a timeline. At Altosoft, we typically do a one day POC. Sometimes two. Other vendors probably require more time. Ask your vendor how much time they need, negotiate this with them up front, and hold them to completing the POC in the requisite time frame!&quot;

My point is that setting some kind of a structured timeline is important. If a vendor can&#039;t deliver a POC in the time they promise, then, in my opinion, that should be a big red flag for a full scale project.

That being said, we take a lot of pride in the productivity of our solutions compared to other options out there, and that obviously came through in my post. I don’t think any company that has experienced a one or two day POC with Altosoft would consider the results to be trivial. Of course, some customers want to do even more, and naturally we are happy to accommodate that as well.</description>
		<content:encoded><![CDATA[<p>Thanks for the comments. I think we&#8217;re agreed on the value of POCs.</p>
<p>My intent wasn&#8217;t to suggest that organizations limit themselves to one day &#8220;toy&#8221; POCs. Ultimately, there’s no point in running a POC if the results don’t help establish that vendor’s ability to deliver on a broader project. So it’s essential that the POC not be a toy, whether it takes a day or a few weeks.</p>
<p>Here&#8217;s what I wrote:</p>
<p>&#8220;Operate on a timeline. At Altosoft, we typically do a one day POC. Sometimes two. Other vendors probably require more time. Ask your vendor how much time they need, negotiate this with them up front, and hold them to completing the POC in the requisite time frame!&#8221;</p>
<p>My point is that setting some kind of a structured timeline is important. If a vendor can&#8217;t deliver a POC in the time they promise, then, in my opinion, that should be a big red flag for a full scale project.</p>
<p>That being said, we take a lot of pride in the productivity of our solutions compared to other options out there, and that obviously came through in my post. I don’t think any company that has experienced a one or two day POC with Altosoft would consider the results to be trivial. Of course, some customers want to do even more, and naturally we are happy to accommodate that as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

