<?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 for Propero Solutions</title>
	<atom:link href="http://properosolutions.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://properosolutions.com</link>
	<description>Helping organizations succeed with agile software development</description>
	<lastBuildDate>Wed, 01 Feb 2012 02:47:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Dynamic Team Estimation in Action by Dan Neumann</title>
		<link>http://properosolutions.com/2010/05/dynamic-team-estimation-in-action/comment-page-1/#comment-4279</link>
		<dc:creator>Dan Neumann</dc:creator>
		<pubDate>Wed, 01 Feb 2012 02:47:16 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=478#comment-4279</guid>
		<description>Very nice description. It certainly helped clarify your Agile 2012 conference submission. I may give this technique a try with teams I coach.</description>
		<content:encoded><![CDATA[<p>Very nice description. It certainly helped clarify your Agile 2012 conference submission. I may give this technique a try with teams I coach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by Great Blog Post Summarizing Lisa Crispin’s “Secrets of Successful Test Automation” &#124; The Agile Radar</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-3426</link>
		<dc:creator>Great Blog Post Summarizing Lisa Crispin’s “Secrets of Successful Test Automation” &#124; The Agile Radar</dc:creator>
		<pubDate>Mon, 12 Dec 2011 15:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-3426</guid>
		<description>[...] http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/" rel="nofollow">http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by A Smattering of Selenium #70 &#171; Official Selenium Blog</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-3117</link>
		<dc:creator>A Smattering of Selenium #70 &#171; Official Selenium Blog</dc:creator>
		<pubDate>Wed, 23 Nov 2011 15:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-3117</guid>
		<description>[...] The Secrets of Successful Test Automation is a summary of a talk Lisa Crispin did recently. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Secrets of Successful Test Automation is a summary of a talk Lisa Crispin did recently. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resources by Dynamic Team Estimation in Action</title>
		<link>http://properosolutions.com/resources/comment-page-1/#comment-3054</link>
		<dc:creator>Dynamic Team Estimation in Action</dc:creator>
		<pubDate>Mon, 14 Nov 2011 14:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://accelerateagile.com/?page_id=195#comment-3054</guid>
		<description>[...] Resources [...]</description>
		<content:encoded><![CDATA[<p>[...] Resources [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metrics for agile projects by Propero Solutions &#8211; Potential Dysfunctions of Sprint Commitments</title>
		<link>http://properosolutions.com/2009/07/metrics-for-agile-projects/comment-page-1/#comment-3053</link>
		<dc:creator>Propero Solutions &#8211; Potential Dysfunctions of Sprint Commitments</dc:creator>
		<pubDate>Mon, 14 Nov 2011 14:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://accelerateagile.com/2009/07/metrics-for-agile-projects/#comment-3053</guid>
		<description>[...] be sure to have good quality metrics as compensating measures for your velocity metrics. While velocity metrics give an incentive for the team to go faster, they [...]</description>
		<content:encoded><![CDATA[<p>[...] be sure to have good quality metrics as compensating measures for your velocity metrics. While velocity metrics give an incentive for the team to go faster, they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by James Moseley</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-3007</link>
		<dc:creator>James Moseley</dc:creator>
		<pubDate>Tue, 01 Nov 2011 20:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-3007</guid>
		<description>Thanks for sharing this information Brad.  If it wasn&#039;t against company policy, I&#039;d demonstrate my passion and commitment to these secrets with an honorary tattoo  of 1-11 :)</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this information Brad.  If it wasn&#8217;t against company policy, I&#8217;d demonstrate my passion and commitment to these secrets with an honorary tattoo  of 1-11 <img src='http://properosolutions.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by Рубрика «Полезное чтиво». Выпуск 8 &#171; XP Injection</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-3004</link>
		<dc:creator>Рубрика «Полезное чтиво». Выпуск 8 &#171; XP Injection</dc:creator>
		<pubDate>Tue, 01 Nov 2011 10:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-3004</guid>
		<description>[...] The Secrets of Successful Test Automation &#8211; советы по организации успешного процесса автоматизации тестирования [...]</description>
		<content:encoded><![CDATA[<p>[...] The Secrets of Successful Test Automation &#8211; советы по организации успешного процесса автоматизации тестирования [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by Jonny Reber</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-2981</link>
		<dc:creator>Jonny Reber</dc:creator>
		<pubDate>Thu, 27 Oct 2011 10:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-2981</guid>
		<description>Excellent post and summary! I think I&#039;ll print and stick up around our agile boards. We have spent the last year trying to implement numbers 1-11 at a huge UK media company. On the whole we have been successful but the biggest factor in making the above happen is captured in the lines:
- passionate people
- strong teamwork and collaboration

To which I would add &#039;discipline - discipline - discipline&#039;</description>
		<content:encoded><![CDATA[<p>Excellent post and summary! I think I&#8217;ll print and stick up around our agile boards. We have spent the last year trying to implement numbers 1-11 at a huge UK media company. On the whole we have been successful but the biggest factor in making the above happen is captured in the lines:<br />
- passionate people<br />
- strong teamwork and collaboration</p>
<p>To which I would add &#8216;discipline &#8211; discipline &#8211; discipline&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by Mikalai Alimenkou</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-2979</link>
		<dc:creator>Mikalai Alimenkou</dc:creator>
		<pubDate>Thu, 27 Oct 2011 09:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-2979</guid>
		<description>Thanks a lot for sharing these notes. Many useful points. I want to add one important for fixing failed test. It must be responsibility of the team member who broke the test. Instead many teams delegate this responsibility to testers themselves. And as a result testers start continuous loop of fixing broken tests. While they try to fix one test somebody may break another one. Especially this issue is visible when development team is unbalanced (for example 5 developers and 1 tester). Fixing test by developer who broke it also helps to archive common responsibility for product quality.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for sharing these notes. Many useful points. I want to add one important for fixing failed test. It must be responsibility of the team member who broke the test. Instead many teams delegate this responsibility to testers themselves. And as a result testers start continuous loop of fixing broken tests. While they try to fix one test somebody may break another one. Especially this issue is visible when development team is unbalanced (for example 5 developers and 1 tester). Fixing test by developer who broke it also helps to archive common responsibility for product quality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Secrets of Successful Test Automation by Brad</title>
		<link>http://properosolutions.com/2011/10/the-secrets-of-successful-test-automation/comment-page-1/#comment-2978</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Thu, 27 Oct 2011 01:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://properosolutions.com/?p=568#comment-2978</guid>
		<description>&quot;Stop the line&quot; means whenever a test is failing, the team&#039;s top priority is to fix it, even if other work must be delayed. It requires management commitment to support this practice and not to undermine it. It requires team discipline to stop the line when it may be tempting to just ignore the failing test - &quot;we&#039;ll fix it later&quot;. We all no that &quot;later&quot; often means &quot;never&quot;. 
HTH.</description>
		<content:encoded><![CDATA[<p>&#8220;Stop the line&#8221; means whenever a test is failing, the team&#8217;s top priority is to fix it, even if other work must be delayed. It requires management commitment to support this practice and not to undermine it. It requires team discipline to stop the line when it may be tempting to just ignore the failing test &#8211; &#8220;we&#8217;ll fix it later&#8221;. We all no that &#8220;later&#8221; often means &#8220;never&#8221;.<br />
HTH.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

