<?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"
	>
<channel>
	<title>Comments on: How not to specify requirements</title>
	<atom:link href="http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html/feed" rel="self" type="application/rss+xml" />
	<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html</link>
	<description>Ian Stevens' weblog</description>
	<pubDate>Fri, 21 Nov 2008 21:45:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Ian Stevens</title>
		<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html#comment-2158</link>
		<dc:creator>Ian Stevens</dc:creator>
		<pubDate>Fri, 26 Jan 2007 01:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://crazedmonkey.com/blog/internet/how-not-to-specify-requirements.html#comment-2158</guid>
		<description>Martin, I understand that these guys prepared the report out of the goodness of their hearts, but this might be the only input the TTC receives and I don't want them to throw it to the wayside simply because it's difficult to follow.  The comments referenced in the spreadsheet contain data which the column headings can't describe, and to have them ignored simply because no links exist would be unfortunate.  As you can see, I've rectified the problem with &lt;a href="http://crazedmonkey.com/ttc_website_suggestions.html" rel="nofollow"&gt;my remixed document&lt;/a&gt;.  It's not perfect, but at least it requires less work from the reader.</description>
		<content:encoded><![CDATA[<p>Martin, I understand that these guys prepared the report out of the goodness of their hearts, but this might be the only input the TTC receives and I don&#8217;t want them to throw it to the wayside simply because it&#8217;s difficult to follow.  The comments referenced in the spreadsheet contain data which the column headings can&#8217;t describe, and to have them ignored simply because no links exist would be unfortunate.  As you can see, I&#8217;ve rectified the problem with <a href="http://crazedmonkey.com/ttc_website_suggestions.html"  rel="nofollow">my remixed document</a>.  It&#8217;s not perfect, but at least it requires less work from the reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reading Toronto responds to my criticism of their spreadsheet - crazed monkey</title>
		<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html#comment-2156</link>
		<dc:creator>Reading Toronto responds to my criticism of their spreadsheet - crazed monkey</dc:creator>
		<pubDate>Fri, 26 Jan 2007 01:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://crazedmonkey.com/blog/internet/how-not-to-specify-requirements.html#comment-2156</guid>
		<description>[...] Ian Stevens&#8217; weblog     &#171; How not to specify requirements [...]</description>
		<content:encoded><![CDATA[<p>[...] Ian Stevens&#8217; weblog     &laquo; How not to specify requirements [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html#comment-2148</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 25 Jan 2007 15:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://crazedmonkey.com/blog/internet/how-not-to-specify-requirements.html#comment-2148</guid>
		<description>Aren't you being a bit hard on theses guys? After all, they were trying to do a public service. I also see that the column on the left has a heading that describes what it is.</description>
		<content:encoded><![CDATA[<p>Aren&#8217;t you being a bit hard on theses guys? After all, they were trying to do a public service. I also see that the column on the left has a heading that describes what it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Ouellette</title>
		<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html#comment-2146</link>
		<dc:creator>Robert Ouellette</dc:creator>
		<pubDate>Thu, 25 Jan 2007 13:53:39 +0000</pubDate>
		<guid isPermaLink="false">http://crazedmonkey.com/blog/internet/how-not-to-specify-requirements.html#comment-2146</guid>
		<description>Hi Ian, thank you for your critiques of the spreadsheet I put together. First, my apologies for getting your URL wrong! There were so many postings to go through that, since this is not the only project I'm involved in, I had to do it during those hours I might otherwise do useful things like, say, sleep.

When I wrote "Easy to use" what I meant was that it takes a lot of information and organizes it in a graphical way - prioritizing it by the most desired recommendations to the least. According to the people who have looked at the document it succeeds in conveying that information in an "easy to understand" way.

The one anomaly was as follows: Many people offered web sites they thought were examples of how to do it right. Since they are references they were put in the first row and are highlighted by a darker border.

As to the website comments references being hard to understand, this is a function of time available. Still, everyone I showed the spreadsheet to understood the references so I did not commit any further time to making a legend. Remember, the spreadsheet was not originally meant for the greater community but when people asked for it we decided to make it accessible.

I think that the overall initiative generated some great input. I'd be happy to work with you Ian if you have the time to further enhance the document. As a volunteer effort we have all done something worthwhile that may just help make the city a little bit better.

Cheers,

Robert</description>
		<content:encoded><![CDATA[<p>Hi Ian, thank you for your critiques of the spreadsheet I put together. First, my apologies for getting your URL wrong! There were so many postings to go through that, since this is not the only project I&#8217;m involved in, I had to do it during those hours I might otherwise do useful things like, say, sleep.</p>
<p>When I wrote &#8220;Easy to use&#8221; what I meant was that it takes a lot of information and organizes it in a graphical way - prioritizing it by the most desired recommendations to the least. According to the people who have looked at the document it succeeds in conveying that information in an &#8220;easy to understand&#8221; way.</p>
<p>The one anomaly was as follows: Many people offered web sites they thought were examples of how to do it right. Since they are references they were put in the first row and are highlighted by a darker border.</p>
<p>As to the website comments references being hard to understand, this is a function of time available. Still, everyone I showed the spreadsheet to understood the references so I did not commit any further time to making a legend. Remember, the spreadsheet was not originally meant for the greater community but when people asked for it we decided to make it accessible.</p>
<p>I think that the overall initiative generated some great input. I&#8217;d be happy to work with you Ian if you have the time to further enhance the document. As a volunteer effort we have all done something worthwhile that may just help make the city a little bit better.</p>
<p>Cheers,</p>
<p>Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Topping</title>
		<link>http://crazedmonkey.com/blog/programming/how-not-to-specify-requirements.html#comment-2145</link>
		<dc:creator>David Topping</dc:creator>
		<pubDate>Thu, 25 Jan 2007 13:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://crazedmonkey.com/blog/internet/how-not-to-specify-requirements.html#comment-2145</guid>
		<description>I just forwarded a link to this article to Robert of ReadingToronto, Ian -- I hope that he can clarify a few things for you.</description>
		<content:encoded><![CDATA[<p>I just forwarded a link to this article to Robert of ReadingToronto, Ian &#8212; I hope that he can clarify a few things for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
