<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Defining Proof of Concepts</title>
	<link>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/</link>
	<description>...learning a8out the wor1d 0f di9ital learning.</description>
	<pubDate>Wed, 19 Nov 2008 13:06:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Tom Cotton&#8217;s 8109 &#187; Redefining PoC</title>
		<link>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-12072</link>
		<pubDate>Wed, 07 Nov 2007 03:34:10 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-12072</guid>
					<description>[...] Defining PoCs [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Defining PoCs [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom Cotton</title>
		<link>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8841</link>
		<pubDate>Mon, 08 Oct 2007 06:19:33 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8841</guid>
					<description>I think you have highlighted the problem: not many people understand that a PoC is a precursor a full blown project.

It directly informs a proper project's analysis, business case and scoping aspects.

Classic project management has to be safe because of to 85%-15% concept.  In this framework you can't take risks. In a PoC you can.

As you have correctly identified, a PoC looks at the concept.  This dramatically reduces the big project risk of developing the wrong 'concept' - way before committing traditional serious project resources.

I liked your "Someone might want to buy a PoC..." comment because it's made me think that a PoC outcome should be "someone might want to &lt;em&gt;back &lt;/em&gt;this PoC - by funding it as a true project"</description>
		<content:encoded><![CDATA[<p>I think you have highlighted the problem: not many people understand that a PoC is a precursor a full blown project.</p>
<p>It directly informs a proper project&#8217;s analysis, business case and scoping aspects.</p>
<p>Classic project management has to be safe because of to 85%-15% concept.  In this framework you can&#8217;t take risks. In a PoC you can.</p>
<p>As you have correctly identified, a PoC looks at the concept.  This dramatically reduces the big project risk of developing the wrong &#8216;concept&#8217; - way before committing traditional serious project resources.</p>
<p>I liked your &#8220;Someone might want to buy a PoC&#8230;&#8221; comment because it&#8217;s made me think that a PoC outcome should be &#8220;someone might want to <em>back </em>this PoC - by funding it as a true project&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jen</title>
		<link>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8840</link>
		<pubDate>Mon, 08 Oct 2007 05:54:39 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8840</guid>
					<description>The 3 people 3 months $30k has its appeal - but it doesn't work that way. My guess that in your edna PoC you've used the input, thoughts and ideas of 30+ people that are being funded by other organisations or projects for the time they participate in or contribute to the thinking about or implementation of the PoC. Collaboration provides richness, some input into the hive mind, a better more realistic result perhaps - but it can also be more expensive to do. 
I think the PoC approach can be problematic, because as we know the 85/15 rule where the 15% takes 85% of the time. With proof of concept you've often worked out most of the 85% - the conceptual stuff. The 15% is the hard implementing stuff - when firewalls, accessibility, metadata compliance, internet speed etc etc all comes into play. Someone might want to buy a proof of concept, but it'd be pretty risky to sell it ;-)</description>
		<content:encoded><![CDATA[<p>The 3 people 3 months $30k has its appeal - but it doesn&#8217;t work that way. My guess that in your edna PoC you&#8217;ve used the input, thoughts and ideas of 30+ people that are being funded by other organisations or projects for the time they participate in or contribute to the thinking about or implementation of the PoC. Collaboration provides richness, some input into the hive mind, a better more realistic result perhaps - but it can also be more expensive to do.<br />
I think the PoC approach can be problematic, because as we know the 85/15 rule where the 15% takes 85% of the time. With proof of concept you&#8217;ve often worked out most of the 85% - the conceptual stuff. The 15% is the hard implementing stuff - when firewalls, accessibility, metadata compliance, internet speed etc etc all comes into play. Someone might want to buy a proof of concept, but it&#8217;d be pretty risky to sell it ;-)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Seyfang</title>
		<link>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8766</link>
		<pubDate>Mon, 08 Oct 2007 03:21:52 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/tcotton/2007/10/08/defining-proof-of-concepts/#comment-8766</guid>
					<description>Tom, Andy is thinking about his too!
His thoughts over at:
http://processofinnovation.com/wordpress/?p=28

Fang</description>
		<content:encoded><![CDATA[<p>Tom, Andy is thinking about his too!<br />
His thoughts over at:<br />
<a href='http://processofinnovation.com/wordpress/?p=28' rel='nofollow'>http://processofinnovation.com/wordpress/?p=28</a></p>
<p>Fang
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
