<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Some Good Specification Practices, or, I Am Out of Clever Titles</title>
	<atom:link href="http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/feed/" rel="self" type="application/rss+xml" />
	<link>http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/</link>
	<description>Making good software and building good teams.</description>
	<lastBuildDate>Mon, 07 Jun 2010 15:49:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Using the Right Medium &#171; Gotta Start Somewhere</title>
		<link>http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-35</link>
		<dc:creator>Using the Right Medium &#171; Gotta Start Somewhere</dc:creator>
		<pubDate>Fri, 13 Nov 2009 15:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://catsch.wordpress.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-35</guid>
		<description>[...] Using the Right&#160;Medium    Posted November 13, 2009 Filed under: Uncategorized &#124;   This post was co-written on Google Wave with my colleague Scott C. Reynolds and is a follow up to our previous post about good specification practices. [...]</description>
		<content:encoded><![CDATA[<p>[...] Using the Right&nbsp;Medium    Posted November 13, 2009 Filed under: Uncategorized |   This post was co-written on Google Wave with my colleague Scott C. Reynolds and is a follow up to our previous post about good specification practices. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-33</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 13 Nov 2009 04:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://catsch.wordpress.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-33</guid>
		<description>&quot;MMFs are really handy on our team because our developers can work on stuff in the same areas that they are currently working on&quot;

That&#039;s an excellent point, Cat.

Back in the cold blooded old days of XP, we&#039;d call that working by theme. What goes around (that&#039;s good) comes around (and is good).</description>
		<content:encoded><![CDATA[<p>&#8220;MMFs are really handy on our team because our developers can work on stuff in the same areas that they are currently working on&#8221;</p>
<p>That&#8217;s an excellent point, Cat.</p>
<p>Back in the cold blooded old days of XP, we&#8217;d call that working by theme. What goes around (that&#8217;s good) comes around (and is good).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: catschwamm</title>
		<link>http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-32</link>
		<dc:creator>catschwamm</dc:creator>
		<pubDate>Fri, 13 Nov 2009 00:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://catsch.wordpress.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-32</guid>
		<description>While I see your point, as there are a lot of words like that in our industry, I&#039;m really not concerned about the terminology.  MMFs are really handy on our team because our developers can work on stuff in the same areas that they are currently working on; they don&#039;t have to context switch and come back later to do things related to another feature.  It gets work done faster and better, and we can see large swaths of functionality at a time instead of having to imagine what the rest will look like while we&#039;re in a demo.</description>
		<content:encoded><![CDATA[<p>While I see your point, as there are a lot of words like that in our industry, I&#8217;m really not concerned about the terminology.  MMFs are really handy on our team because our developers can work on stuff in the same areas that they are currently working on; they don&#8217;t have to context switch and come back later to do things related to another feature.  It gets work done faster and better, and we can see large swaths of functionality at a time instead of having to imagine what the rest will look like while we&#8217;re in a demo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Bellware</title>
		<link>http://catschwamm.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-31</link>
		<dc:creator>Scott Bellware</dc:creator>
		<pubDate>Thu, 12 Nov 2009 22:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://catsch.wordpress.com/2009/11/12/some-good-specification-practices-or-i-am-out-of-clever-titles/#comment-31</guid>
		<description>I think this obsession that the software community has with &quot;MMF&#039;s&quot; is going to be yet another bit of obsessive/compulsive consultant/speaker lexicon entitlement that will continue to slow down the software community&#039;s understanding of managing product development.  We can do better than being distracted by yet another orthodoxy.  I think we should know by now that this kind of thing is our pattern and our susceptibility.</description>
		<content:encoded><![CDATA[<p>I think this obsession that the software community has with &#8220;MMF&#8217;s&#8221; is going to be yet another bit of obsessive/compulsive consultant/speaker lexicon entitlement that will continue to slow down the software community&#8217;s understanding of managing product development.  We can do better than being distracted by yet another orthodoxy.  I think we should know by now that this kind of thing is our pattern and our susceptibility.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
