<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Frank Carver&#039;s Punch Barrel &#187; acceptance</title>
	<atom:link href="http://blog.punchbarrel.com/tag/acceptance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.punchbarrel.com</link>
	<description>Frank Carver&#039;s musings about software and life</description>
	<lastBuildDate>Thu, 08 Dec 2011 22:58:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<copyright>Copyright &#xA9; Frank Carver&#039;s Punch Barrel 2010 </copyright>
	<managingEditor>frank.carver@googlemail.com (Frank Carver&#039;s Punch Barrel)</managingEditor>
	<webMaster>frank.carver@googlemail.com (Frank Carver&#039;s Punch Barrel)</webMaster>
	<ttl>1440</ttl>
	<image>
		<url>http://punchbarrel.com/images/punchbarrel-144.jpg</url>
		<title>Frank Carver&#039;s Punch Barrel</title>
		<link>http://blog.punchbarrel.com</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>Frank Carver&#039;s musings about software and life</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Frank Carver&#039;s Punch Barrel</itunes:author>
	<itunes:owner>
		<itunes:name>Frank Carver&#039;s Punch Barrel</itunes:name>
		<itunes:email>frank.carver@googlemail.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://punchbarrel.com/images/punchbarrel-144.jpg" />
		<item>
		<title>Agile: When is a story done?</title>
		<link>http://blog.punchbarrel.com/2009/01/17/agile-when-is-a-story-done/</link>
		<comments>http://blog.punchbarrel.com/2009/01/17/agile-when-is-a-story-done/#comments</comments>
		<pubDate>Sat, 17 Jan 2009 20:45:57 +0000</pubDate>
		<dc:creator>Frank</dc:creator>
				<category><![CDATA[Information]]></category>
		<category><![CDATA[acceptance]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[done]]></category>
		<category><![CDATA[estimation]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[story]]></category>

		<guid isPermaLink="false">http://blog.punchbarrel.com/?p=1027</guid>
		<description><![CDATA[Anyone who has worked with me in the past will probably recognize my standard response to vague or unclear requirements &#8211; &#8220;how will I know when I&#8217;m done?&#8221;. I use it so much becuase the simple trick of changing viewpoint to view work in terms of acceptance criteria is key to enabling sensible discussion, estimation, [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone who has worked with me in the past will probably recognize my standard response to vague or unclear requirements &#8211; &#8220;how will I know when I&#8217;m done?&#8221;. I use it so much becuase the simple trick of changing viewpoint to view work in terms of acceptance criteria is key to enabling sensible discussion, estimation, planning and development to begin.</p>
<p>Mark Needham has been considering similar issues, but rather than using the technique to clarify requirements so a pice of work can enter the development process, he looks at how to decide when to remove it.</p>
<p><a href="http://www.markhneedham.com/blog/2009/01/04/agile-when-is-a-story-done/">Agile: When is a story done? at Mark Needham</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.punchbarrel.com/2009/01/17/agile-when-is-a-story-done/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who owns automated acceptance tests?</title>
		<link>http://blog.punchbarrel.com/2008/10/13/who-owns-automated-acceptance-tests/</link>
		<comments>http://blog.punchbarrel.com/2008/10/13/who-owns-automated-acceptance-tests/#comments</comments>
		<pubDate>Mon, 13 Oct 2008 08:29:17 +0000</pubDate>
		<dc:creator>Frank</dc:creator>
				<category><![CDATA[Information]]></category>
		<category><![CDATA[acceptance]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blog.punchbarrel.com/?p=665</guid>
		<description><![CDATA[As software testing spreads out in scope from the old notion of manual exercising of a system into areas such as developer unit tests and automated acceptance tests, the issue of ownership becomes more important. In this short and pithy post Kristan Vingrys states his opinion. Vinktank &#124; Who owns automated acceptance tests?]]></description>
			<content:encoded><![CDATA[<p>As software testing spreads out in scope from the old notion of manual exercising of a system into areas such as developer unit tests and automated acceptance tests, the issue of ownership becomes more important. In this short and pithy post Kristan Vingrys states his opinion.</p>
<p><a href="http://www.vinktank.com/test-automation/who-owns-automated-acceptance-tests/">Vinktank | Who owns automated acceptance tests?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.punchbarrel.com/2008/10/13/who-owns-automated-acceptance-tests/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automated story-based acceptance tests lead to unmaintainable systems</title>
		<link>http://blog.punchbarrel.com/2008/09/30/automated-story-based-acceptance-tests-lead-to-unmaintainable-systems/</link>
		<comments>http://blog.punchbarrel.com/2008/09/30/automated-story-based-acceptance-tests-lead-to-unmaintainable-systems/#comments</comments>
		<pubDate>Tue, 30 Sep 2008 09:28:18 +0000</pubDate>
		<dc:creator>Frank</dc:creator>
				<category><![CDATA[Information]]></category>
		<category><![CDATA[acceptance]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[stories]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blog.punchbarrel.com/?p=566</guid>
		<description><![CDATA[A fascinating counterpoint to Gojko Adzic&#8216;s writings on acceptance testing in an agile process. thekua.com@work » Automated story-based acceptance tests lead to unmaintainable systems Update: here&#8217;s some more discussion on this topic, and how it is affected by the nature of user stories User Stories are Just Schedulable Change]]></description>
			<content:encoded><![CDATA[<p>A fascinating counterpoint to <a href="http://gojko.net/">Gojko Adzic</a>&#8216;s writings on <a href="http://blog.punchbarrel.com/2008/09/18/fitting-agile-acceptance-testing-into-the-development-process/">acceptance testing in an agile process</a>.</p>
<p><a href="http://www.thekua.com/atwork/2008/09/30/automated-story-based-acceptance-tests-lead-to-unmaintainable-systems/">thekua.com@work » Automated story-based acceptance tests lead to unmaintainable systems</a></p>
<p>Update: here&#8217;s some more discussion on this topic, and how it is affected by the nature of user stories<br />
<a href="http://fragmental.tw/2008/10/01/user-stories-are-just-schedulable-change/"><br />
User Stories are Just Schedulable Change</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.punchbarrel.com/2008/09/30/automated-story-based-acceptance-tests-lead-to-unmaintainable-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.111 seconds -->

