<?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 &#8211; is it something?</title>
	<atom:link href="http://socialmode.com/2008/12/22/agile-is-it-something/feed/" rel="self" type="application/rss+xml" />
	<link>http://socialmode.com/2008/12/22/agile-is-it-something/</link>
	<description>Integrated Synthesis of Media, Society and Behavior</description>
	<lastBuildDate>Fri, 06 Jan 2012 18:54:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: un1crom</title>
		<link>http://socialmode.com/2008/12/22/agile-is-it-something/#comment-786</link>
		<dc:creator><![CDATA[un1crom]]></dc:creator>
		<pubDate>Mon, 22 Dec 2008 23:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://socialmode.com/?p=688#comment-786</guid>
		<description><![CDATA[i like it.

basically, we&#039;re not pushing out all the crap and getting to what matters earlier in the process: can users USE this software.]]></description>
		<content:encoded><![CDATA[<p>i like it.</p>
<p>basically, we&#8217;re not pushing out all the crap and getting to what matters earlier in the process: can users USE this software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Montalenti</title>
		<link>http://socialmode.com/2008/12/22/agile-is-it-something/#comment-785</link>
		<dc:creator><![CDATA[Andrew Montalenti]]></dc:creator>
		<pubDate>Mon, 22 Dec 2008 23:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://socialmode.com/?p=688#comment-785</guid>
		<description><![CDATA[I&#039;ll give you my version of the Agile &quot;process&quot; in a nutshell: timeboxed iterations.  For me, timeboxed iterations with real deliverables at the end of each short cycle (I like two weeks for a small-medium size team) is the core thing that sets Agile project management apart.

You combine this with what I call &quot;Agile practices&quot;:

- focus on user stories rather than tasks, that is, trying to build things that add value for a specific user rather than just &#039;doing stuff&#039;

- including the customer in the prioritization decisions for your product development

- focus on best practices that connect the development practice with the user requirements, such as TDD, automated acceptance testing

- emphasize the psychology of the programmer and the instinct for craftsmanship; to do this, use pair programming (rather than Big Design Up-Front and &#039;throwing specs over the wall&#039;), use retrospectives at the end of iterations to reflect upon what was done well, and encourage code review and refactoring continuously.

Agile Practices + Agile Process == a happy and productive team, I think.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ll give you my version of the Agile &#8220;process&#8221; in a nutshell: timeboxed iterations.  For me, timeboxed iterations with real deliverables at the end of each short cycle (I like two weeks for a small-medium size team) is the core thing that sets Agile project management apart.</p>
<p>You combine this with what I call &#8220;Agile practices&#8221;:</p>
<p>- focus on user stories rather than tasks, that is, trying to build things that add value for a specific user rather than just &#8216;doing stuff&#8217;</p>
<p>- including the customer in the prioritization decisions for your product development</p>
<p>- focus on best practices that connect the development practice with the user requirements, such as TDD, automated acceptance testing</p>
<p>- emphasize the psychology of the programmer and the instinct for craftsmanship; to do this, use pair programming (rather than Big Design Up-Front and &#8216;throwing specs over the wall&#8217;), use retrospectives at the end of iterations to reflect upon what was done well, and encourage code review and refactoring continuously.</p>
<p>Agile Practices + Agile Process == a happy and productive team, I think.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

