<?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: Change is good</title>
	<atom:link href="http://www.refactor.co.za/2010/02/03/change-is-good/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.refactor.co.za/2010/02/03/change-is-good/</link>
	<description>It&#039;s all about improvement</description>
	<lastBuildDate>Mon, 19 Jul 2010 10:58:54 +0200</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Rick Tonoli</title>
		<link>http://www.refactor.co.za/2010/02/03/change-is-good/comment-page-1/#comment-50</link>
		<dc:creator>Rick Tonoli</dc:creator>
		<pubDate>Thu, 11 Feb 2010 20:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.refactor.co.za/?p=157#comment-50</guid>
		<description>Enforced teamwork is kind of like pushing a string, fun, but not useful. The team decided paired programming was something we wanted to try, two of them ran with it for a sprint and gave critical feedback at the end (both good and bad). Oh, and to make things more interesting we added TDD in as well :)

We found some interesting benefits coming out of it (besides the ones we expected), like the fact that people find it difficult to &quot;interrupt&quot; two people working, so fewer interrupts and more focus; guys actually had fun collaborating on solving a problem, even doing boring stuff; the combined momentum of the pair was (I thought) greater than the sum of the individuals. Add to that the obvious things like automatic review of code, improved quality and constant refactoring for improvement and I think it&#039;s a winning recipe.

In the end though I think it has to be something the team decides to do, not something dictated to. It&#039;s a mind-shift of note to get used to and unless your heart is in it, there&#039;s no real hope it will succeed.</description>
		<content:encoded><![CDATA[<p>Enforced teamwork is kind of like pushing a string, fun, but not useful. The team decided paired programming was something we wanted to try, two of them ran with it for a sprint and gave critical feedback at the end (both good and bad). Oh, and to make things more interesting we added TDD in as well <img src='http://www.refactor.co.za/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>We found some interesting benefits coming out of it (besides the ones we expected), like the fact that people find it difficult to &#8220;interrupt&#8221; two people working, so fewer interrupts and more focus; guys actually had fun collaborating on solving a problem, even doing boring stuff; the combined momentum of the pair was (I thought) greater than the sum of the individuals. Add to that the obvious things like automatic review of code, improved quality and constant refactoring for improvement and I think it&#8217;s a winning recipe.</p>
<p>In the end though I think it has to be something the team decides to do, not something dictated to. It&#8217;s a mind-shift of note to get used to and unless your heart is in it, there&#8217;s no real hope it will succeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Willemse</title>
		<link>http://www.refactor.co.za/2010/02/03/change-is-good/comment-page-1/#comment-41</link>
		<dc:creator>Nic Willemse</dc:creator>
		<pubDate>Fri, 05 Feb 2010 13:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.refactor.co.za/?p=157#comment-41</guid>
		<description>Rick please talk more about how you have started experimenting with paired programming, have you enforced it ? If so how ? per task ? or have you just paired individuals together ? 

We have paired development happening, funny thing is that it just sort of happened. To me this shows some good team work, the team self organised the development work, and when found the need teamed up together to tackle a task!</description>
		<content:encoded><![CDATA[<p>Rick please talk more about how you have started experimenting with paired programming, have you enforced it ? If so how ? per task ? or have you just paired individuals together ? </p>
<p>We have paired development happening, funny thing is that it just sort of happened. To me this shows some good team work, the team self organised the development work, and when found the need teamed up together to tackle a task!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
