<?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: What does the spec say again?</title>
	<atom:link href="http://www.kalyr.co.uk/weblog/computing/testing/what-does-the-spec-say-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalyr.co.uk/weblog/computing/testing/what-does-the-spec-say-again/</link>
	<description>The blogs of Tim Hall</description>
	<lastBuildDate>Fri, 14 Apr 2017 23:35:42 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.7.41</generator>
	<item>
		<title>By: Abi Sutherland</title>
		<link>http://www.kalyr.co.uk/weblog/computing/testing/what-does-the-spec-say-again/comment-page-1/#comment-37363</link>
		<dc:creator><![CDATA[Abi Sutherland]]></dc:creator>
		<pubDate>Wed, 29 Jan 2014 23:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalyr.co.uk/weblog/?p=9768#comment-37363</guid>
		<description><![CDATA[I&#039;ve certainly worked on projects like your pear-shaped deathmarch, particularly in relatively high-risk environments like financial services.  I&#039;m now in much more agile contexts, and I have to say, I do appreciate the flexibility that we get from frequent communication and empowered system owners.

Having said that, I&#039;m not convinced that it&#039;s &lt;em&gt;not&lt;/em&gt; the developer&#039;s job to query unclear specifications if they notice them.  It&#039;s no more difficult, and much less expensive, to poke at them before coding than it is to drop the job on the tester at the end of the lifecycle.  I don&#039;t want to blame devs for struggling with dysfunctional working environments, but passing the hairball down the line just makes it worse for everybody on the project.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve certainly worked on projects like your pear-shaped deathmarch, particularly in relatively high-risk environments like financial services.  I&#8217;m now in much more agile contexts, and I have to say, I do appreciate the flexibility that we get from frequent communication and empowered system owners.</p>
<p>Having said that, I&#8217;m not convinced that it&#8217;s <em>not</em> the developer&#8217;s job to query unclear specifications if they notice them.  It&#8217;s no more difficult, and much less expensive, to poke at them before coding than it is to drop the job on the tester at the end of the lifecycle.  I don&#8217;t want to blame devs for struggling with dysfunctional working environments, but passing the hairball down the line just makes it worse for everybody on the project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
