<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xml" href="http://www.dzone.com/links/misc/rss.xsl"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dz="http://www.developerzone.com/modules/dz/1.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>dzone.com: queued links: agile</title>
    <link>http://www.dzone.com/links/queue/tag/agile.html</link>
    <description>dzone.com: fresh links for developers</description>
    <language>en-us</language>
    <copyright>Copyright (c) 2008 DZone, Inc.</copyright>
    <pubDate>Tue, 10 Nov 2009 00:38:50 GMT</pubDate>
    <dc:creator>The dzone.com community</dc:creator>
    <dc:date>2009-11-10T00:38:50Z</dc:date>
    <dc:language>en-us</dc:language>
    <dc:rights>Copyright (c) 2008 DZone, Inc.</dc:rights>
    <dz:selfLink>http://www.dzone.com/links/feed/queue/agile/rss.xml</dz:selfLink>
    <image>
      <title>dzone.com: fresh links for developers</title>
      <url>http://www.dzone.com/images/std/dzone.com_258x55.gif</url>
      <link>http://www.dzone.com/links/</link>
    </image>
    <item>
      <title>New iMac: Great Pairing Station?</title>
      <link>http://www.dzone.com/links/rss/new_imac_great_pairing_station.html</link>
      <description>Looking at the new iMacs the 27" quad-core looks like it would make a superb pairing station for programming. I've been waiting to see what the update looked like before looking at end of year purchases. Here's how I see it:</description>
      <category>agile</category>
      <category>apple</category>
      <category>opinion</category>
      <category>tools</category>
      <pubDate>Mon, 09 Nov 2009 23:45:27 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/285429.html</guid>
      <dc:creator>Mark Menard</dc:creator>
      <dc:date>2009-11-09T23:45:27Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/new_imac_great_pairing_station.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/285429.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>Looking at the new iMacs the 27" quad-core looks like it would make a superb pairing station for programming. I've been waiting to see what the update looked like before looking at end of year purchases. Here's how I see it:<br/><br/><a href='http://www.dzone.com/links/rss/new_imac_great_pairing_station.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=285429' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>285429</dz:linkId>
      <dz:submitDate>2009-11-09T23:45:27Z</dz:submitDate>
      <dz:voteUpCount>1</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>2</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/285429.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>Vita Rara</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/218344.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Testing: Chances and Challenges in an Agile World</title>
      <link>http://www.dzone.com/links/rss/testing_chances_and_challenges_in_an_agile_world.html</link>
      <description>Thoughts about testing in an agile environment.</description>
      <category>agile</category>
      <category>methodology</category>
      <category>opinion</category>
      <pubDate>Mon, 09 Nov 2009 18:24:35 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/285271.html</guid>
      <dc:creator>jbandi</dc:creator>
      <dc:date>2009-11-09T18:24:35Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/testing_chances_and_challenges_in_an_agile_world.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/285271.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>Thoughts about testing in an agile environment.
<br/><br/><a href='http://www.dzone.com/links/rss/testing_chances_and_challenges_in_an_agile_world.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=285271' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>285271</dz:linkId>
      <dz:submitDate>2009-11-09T18:24:35Z</dz:submitDate>
      <dz:voteUpCount>1</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>2</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/285271.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>jbandi</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/300660.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Quick Tip: Running Selenium on OS X Snow Leopard</title>
      <link>http://www.dzone.com/links/rss/quick_tip_running_selenium_on_os_x_snow_leopard.html</link>
      <description>Thoughts about testing in agile projects.&#xD;
What are the effects of acceptance test driven development and behavior driven development?</description>
      <category>agile</category>
      <category>methodology</category>
      <category>trends</category>
      <pubDate>Mon, 09 Nov 2009 17:52:38 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/285245.html</guid>
      <dc:creator>jbandi</dc:creator>
      <dc:date>2009-11-09T17:52:38Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/quick_tip_running_selenium_on_os_x_snow_leopard.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/285245.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>Thoughts about testing in agile projects.
What are the effects of acceptance test driven development and behavior driven development?<br/><br/><a href='http://www.dzone.com/links/rss/quick_tip_running_selenium_on_os_x_snow_leopard.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=285245' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>285245</dz:linkId>
      <dz:submitDate>2009-11-09T17:52:38Z</dz:submitDate>
      <dz:voteUpCount>1</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>4</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/285245.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>jbandi</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/300660.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Good Agile Metrics</title>
      <link>http://www.dzone.com/links/rss/good_agile_metrics.html</link>
      <description>MeasureAgile Coaches and Consultants frequently warn their clients that traditional measures such as Earned Value, Hours Worked, Lines of Code, Code Coverage for Tests are not well suited to Agile Projects. But then our clients are left with the question what are good Agile Metrics? How would I tell a good metric from a bad one? Are there contexts where a good metric is bad?</description>
      <category>agile</category>
      <category>methodology</category>
      <pubDate>Mon, 09 Nov 2009 17:38:26 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/285221.html</guid>
      <dc:creator>Mark Levison</dc:creator>
      <dc:date>2009-11-09T17:38:26Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/good_agile_metrics.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/285221.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>MeasureAgile Coaches and Consultants frequently warn their clients that traditional measures such as Earned Value, Hours Worked, Lines of Code, Code Coverage for Tests are not well suited to Agile Projects. But then our clients are left with the question what are good Agile Metrics? How would I tell a good metric from a bad one? Are there contexts where a good metric is bad?<br/><br/><a href='http://www.dzone.com/links/rss/good_agile_metrics.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=285221' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>285221</dz:linkId>
      <dz:submitDate>2009-11-09T17:38:26Z</dz:submitDate>
      <dz:voteUpCount>1</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>6</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/285221.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mlevison</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/184893.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>There Is No End State When Transitioning to Agile</title>
      <link>http://www.dzone.com/links/rss/there_is_no_end_state_when_transitioning_to_agile.html</link>
      <description>None of the agile processes as described by their originators is perfect for your organization. Any may be a good starting point, but you will need to tailor the process to more precisely fit the unique circumstances of your organization, individuals, and industry. As Alistair Cockburn once told me, “Having a chance to change or personalize a process to fit themselves seems to be a critical success factor for a team to adopt a process. It’s the act of creation that seems to bind teams to ‘their own’ process.”</description>
      <category>agile</category>
      <category>methodology</category>
      <category>reviews</category>
      <pubDate>Mon, 09 Nov 2009 13:47:47 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/285019.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2009-11-09T13:47:47Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/there_is_no_end_state_when_transitioning_to_agile.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/285019.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>None of the agile processes as described by their originators is perfect for your organization. Any may be a good starting point, but you will need to tailor the process to more precisely fit the unique circumstances of your organization, individuals, and industry. As Alistair Cockburn once told me, “Having a chance to change or personalize a process to fit themselves seems to be a critical success factor for a team to adopt a process. It’s the act of creation that seems to bind teams to ‘their own’ process.”<br/><br/><a href='http://www.dzone.com/links/rss/there_is_no_end_state_when_transitioning_to_agile.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=285019' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>285019</dz:linkId>
      <dz:submitDate>2009-11-09T13:47:47Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>2</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/285019.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>The Failure of Do-It-Yourself Agile</title>
      <link>http://www.dzone.com/links/rss/the_failure_of_doityourself_agile.html</link>
      <description>The current problem is that hiring an agile consultant to be on-site and work with the team for a number of weeks or months is prohibitively expensive. But this is exactly what is needed to help impart Agile knowledge from person to person.</description>
      <category>agile</category>
      <category>methodology</category>
      <category>opinion</category>
      <pubDate>Mon, 09 Nov 2009 13:12:19 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/284937.html</guid>
      <dc:creator>robertdempsey</dc:creator>
      <dc:date>2009-11-09T13:12:19Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/the_failure_of_doityourself_agile.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/284937.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>The current problem is that hiring an agile consultant to be on-site and work with the team for a number of weeks or months is prohibitively expensive. But this is exactly what is needed to help impart Agile knowledge from person to person.<br/><br/><a href='http://www.dzone.com/links/rss/the_failure_of_doityourself_agile.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=284937' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>284937</dz:linkId>
      <dz:submitDate>2009-11-09T13:12:19Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>4</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/284937.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>robertdempsey</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/230109.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Ted Naleid » Mercurial DVCS DevJam Presentation</title>
      <link>http://www.dzone.com/links/rss/ted_naleid_mercurial_dvcs_devjam_presentation.html</link>
      <description>Presentation on the advantages and disadvantages of Mercurial (a distributed version control system) over centralized version control tools like subversion.&#xD;
&#xD;
Goes into some detail in the concepts of how Mercurial works and a conceptual model that will help people understand how branching/merging in mercurial works.</description>
      <category>agile</category>
      <category>java</category>
      <category>open source</category>
      <category>tools</category>
      <pubDate>Mon, 09 Nov 2009 02:44:59 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/284419.html</guid>
      <dc:creator>tednaleid</dc:creator>
      <dc:date>2009-11-09T02:44:59Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/ted_naleid_mercurial_dvcs_devjam_presentation.html'><img src='http://cdn.dzone.com/images/thumbs/120x90/284419.jpg' style='width:120;height:90;float:left;vertical-align:top;border:1px solid #ccc;' /></a><p style='margin-left: 130px;'>Presentation on the advantages and disadvantages of Mercurial (a distributed version control system) over centralized version control tools like subversion.

Goes into some detail in the concepts of how Mercurial works and a conceptual model that will help people understand how branching/merging in mercurial works.<br/><br/><a href='http://www.dzone.com/links/rss/ted_naleid_mercurial_dvcs_devjam_presentation.html'><img src='http://www.dzone.com/links/voteCountImage?linkId=284419' border='0'/></a></p>]]></content:encoded>
      <dz:linkId>284419</dz:linkId>
      <dz:submitDate>2009-11-09T02:44:59Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>5</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/284419.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>tednaleid</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/281696.gif</dz:userimage>
      </dz:submitter>
    </item>
  </channel>
</rss>

