<?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: A health warning to followers of the Knight News Challenge</title>
	<atom:link href="http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/feed/" rel="self" type="application/rss+xml" />
	<link>http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/</link>
	<description>Mostly about the management of software development</description>
	<lastBuildDate>Fri, 25 Jun 2010 13:41:57 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nik</title>
		<link>http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/comment-page-1/#comment-33974</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Tue, 15 Sep 2009 08:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=565#comment-33974</guid>
		<description>Hi Ryan. Thanks for the further insight. I do realise it&#039;s impossible to condense all the subtleties down into a few soundbites. But then it&#039;s also always fascinating to hear many of the details of the kind you outline above, especially when it&#039;s on a project which has become public, because then an observer can compare their assumptions with the reality.</description>
		<content:encoded><![CDATA[<p>Hi Ryan. Thanks for the further insight. I do realise it&#8217;s impossible to condense all the subtleties down into a few soundbites. But then it&#8217;s also always fascinating to hear many of the details of the kind you outline above, especially when it&#8217;s on a project which has become public, because then an observer can compare their assumptions with the reality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Sholin</title>
		<link>http://niksilver.com/2009/09/14/a-health-warning-to-followers-of-the-knight-news-challenge/comment-page-1/#comment-33973</link>
		<dc:creator>Ryan Sholin</dc:creator>
		<pubDate>Tue, 15 Sep 2009 01:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=565#comment-33973</guid>
		<description>Hi Nik -- Thanks for the feedback! I&#039;m glad someone stopped and actually read the post instead of just retweeting it. A lot of that going around.

First of all, as in all things on the Web, your mileage may vary. But yes, my list at the Knight News Challenge blog was definitely geared toward entrants into that particular blender of funding and ideas.

In my case, I had some experience working with developers and some experience doing very lightweight development myself. I&#039;m an edge case. But I&#039;ve noticed that a few of my fellow News Challenge winners tend to be edge cases themselves. So that&#039;s the audience I was preaching to in that particular post.

To your points:

1. If you&#039;re on a larger team, congratulations. You either know what you&#039;re doing already, or you have enough padding in your grant to make a few mistakes. That&#039;s good! Fail fast, and move on to the next iteration.

2. You&#039;re absolutely right. In the case of the second version of ReportingOn, I spent somewhere in the neighborhood of 8 hours (over the course of a few meetings) in a room with my development duo, with one of them standing in front of a whiteboard guiding the discussion, figuring out what I had in mind, and all of us having some very vivid conversations about the details. I&#039;ve boiled that down to &quot;telling them what you want&quot; because if you&#039;re not willing to put in the time to make your vision clear to your team, you&#039;re not going to get anything out of the exercise that resembles what you imagined.

But by all means, don&#039;t mistake what I&#039;ve learned from experience as a general prescription! If your mileage doesn&#039;t vary in one way or another, then something&#039;s gone horribly wrong here.</description>
		<content:encoded><![CDATA[<p>Hi Nik &#8212; Thanks for the feedback! I&#8217;m glad someone stopped and actually read the post instead of just retweeting it. A lot of that going around.</p>
<p>First of all, as in all things on the Web, your mileage may vary. But yes, my list at the Knight News Challenge blog was definitely geared toward entrants into that particular blender of funding and ideas.</p>
<p>In my case, I had some experience working with developers and some experience doing very lightweight development myself. I&#8217;m an edge case. But I&#8217;ve noticed that a few of my fellow News Challenge winners tend to be edge cases themselves. So that&#8217;s the audience I was preaching to in that particular post.</p>
<p>To your points:</p>
<p>1. If you&#8217;re on a larger team, congratulations. You either know what you&#8217;re doing already, or you have enough padding in your grant to make a few mistakes. That&#8217;s good! Fail fast, and move on to the next iteration.</p>
<p>2. You&#8217;re absolutely right. In the case of the second version of ReportingOn, I spent somewhere in the neighborhood of 8 hours (over the course of a few meetings) in a room with my development duo, with one of them standing in front of a whiteboard guiding the discussion, figuring out what I had in mind, and all of us having some very vivid conversations about the details. I&#8217;ve boiled that down to &#8220;telling them what you want&#8221; because if you&#8217;re not willing to put in the time to make your vision clear to your team, you&#8217;re not going to get anything out of the exercise that resembles what you imagined.</p>
<p>But by all means, don&#8217;t mistake what I&#8217;ve learned from experience as a general prescription! If your mileage doesn&#8217;t vary in one way or another, then something&#8217;s gone horribly wrong here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
