<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:ent="http://www.purl.org/NET/ENT/1.0/">
  <channel>
    <title>Curiouser and Curiouser! on prediction-markets</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic prediction-markets</description>
    <copyright>Copyright 2008 Matt Mower. Some rights reserved.</copyright>
    <generator>Squib/0.5.0.382</generator>
    <managingEditor>self@mattmower.com</managingEditor>
    <webMaster>self@mattmower.com</webMaster>
    <language>en-gb</language>
    <item>
      <title>Prediction markets in software evolution</title>
      <link>http://matt.blogs.it/entries/00002777.html</link>
      <pubDate>Thu, 17 Jan 2008 10:21:34 +0000</pubDate>
      <description>&lt;p&gt;While &lt;a href="http://matt.blogs.it/entries/00002774.html"&gt;chatting with Stowe and Andy&lt;/a&gt; the other night I mentioned an idea that had come to me while I was reading &lt;a href="http://www.nytimes.com/2008/01/07/technology/07link.html?ex=1357448400&amp;amp;en=9c759d229dc5b88f&amp;amp;ei=5088&amp;amp;partner=rssnyt&amp;amp;emc=rss"&gt;an article about Google and prediction markets&lt;/a&gt; that &lt;a href="http://feeds.feedburner.com/~r/typepad/CfUv/~3/212575103/prediction-mark.html"&gt;Euan Semple linked to&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;In short what I was thinking about was using prediction markets to determine the course of a product or how it should be supported. You give, for example, beta testers and support customers the ability to "buy" tickets for features or bugs and drive your effort in the direction that they predict will have the most important effect for them. &lt;/p&gt;

&lt;p&gt;I haven't quite thought through the feedback mechanism that changes the prices or how the economics of the market should work.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002777.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
  </channel>
</rss>
