<?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: Agile 2009 submission: Functional Testing Flex</title>
	<atom:link href="http://blog.code-adept.com/2009/01/27/functional-testing-in-flex-agile-2009-submission/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.code-adept.com/2009/01/27/functional-testing-in-flex-agile-2009-submission/</link>
	<description>Random thoughts on Agile development and other things geeky.</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:00:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Karina</title>
		<link>http://blog.code-adept.com/2009/01/27/functional-testing-in-flex-agile-2009-submission/#comment-1169</link>
		<dc:creator><![CDATA[Karina]]></dc:creator>
		<pubDate>Wed, 08 Feb 2012 23:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.code-adept.com/?p=119#comment-1169</guid>
		<description><![CDATA[One thing I also do as a tesetr is to help the team control scope. Most newbie agile teams over-commit, and they work on stories that are too big. Find ways to divide the work into small chunks or threads. Make sure testing estimates are included in story estimates. Sometimes features take longer to test than to code! When you see a story that looks too big, ask if it can be divided up. Sometimes the smaller piece may not deliver much business value, but the team needs to focus on getting one small story done at a time, including all the testing activities.]]></description>
		<content:encoded><![CDATA[<p>One thing I also do as a tesetr is to help the team control scope. Most newbie agile teams over-commit, and they work on stories that are too big. Find ways to divide the work into small chunks or threads. Make sure testing estimates are included in story estimates. Sometimes features take longer to test than to code! When you see a story that looks too big, ask if it can be divided up. Sometimes the smaller piece may not deliver much business value, but the team needs to focus on getting one small story done at a time, including all the testing activities.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

