﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Archive</title>
    <description>Rod's Articles and Blog</description>
    <link>http://www.effectiveagiledev.com/Articles/tabid/70/Default.aspx?BlogDate=2009-12-31</link>
    <language>en-US</language>
    <managingEditor>webmaster@effectiveagiledev.com</managingEditor>
    <webMaster>webmaster@effectiveagiledev.com</webMaster>
    <pubDate>Sun, 05 Feb 2012 01:00:55 GMT</pubDate>
    <lastBuildDate>Sun, 05 Feb 2012 01:00:55 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.5.1.19887</generator>
    <item>
      <title>Agile's Impact on Product Development</title>
      <description>&lt;p&gt;&amp;#160;Agile&amp;#160;and it's various implementations, including Scrum,&amp;#160;while most often discussed in software development circles, &amp;#160;can correctly be classified as Product Development methodologies.&amp;#160;Most of the time the product being developed has software as a major component, but they are products developed to solve a problem or make a job easier or more efficient. &amp;#160;When we think about products in this broader context we can often identify some impacts on product management rooted in the Agile practices and thought process.&amp;#160;We need to understand these impacts to be prepared to mitigate them and propel the organization to the next level.&lt;/p&gt;
&lt;div&gt;&amp;#160;&lt;/div&gt;
&lt;div&gt;&amp;#160;&lt;/div&gt;
&lt;div&gt;&amp;#160;&lt;/div&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/13/Agiles-Impact-on-Product-Development.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/13/Agiles-Impact-on-Product-Development.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/13/Agiles-Impact-on-Product-Development.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/13/Agiles-Impact-on-Product-Development.aspx</guid>
      <pubDate>Thu, 10 Dec 2009 23:17:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=13</trackback:ping>
    </item>
    <item>
      <title>A question about "Scrum Development for Teams Using Visual Studio / Team Foundation Server 2010"</title>
      <description>&lt;p&gt;How much of the new course will be coding vs. project managment and testing?&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/12/A-question-about-Scrum-Development-for-Teams-Using-Visual-Studio-Team-Foundation-Server-2010.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/12/A-question-about-Scrum-Development-for-Teams-Using-Visual-Studio-Team-Foundation-Server-2010.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/12/A-question-about-Scrum-Development-for-Teams-Using-Visual-Studio-Team-Foundation-Server-2010.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/12/A-question-about-Scrum-Development-for-Teams-Using-Visual-Studio-Team-Foundation-Server-2010.aspx</guid>
      <pubDate>Fri, 04 Dec 2009 18:11:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=12</trackback:ping>
    </item>
    <item>
      <title>Visual Studio / Team Foundation Sever 2010 to Launch on March 22,2010</title>
      <description>&lt;p&gt;&amp;#160;According to Mike Vincent on his blog (http://mvasoftware.com/blogs/mikev_weblog/default.aspx) the launch date for VS/TFS 2010 has been set for March 22,2010. &amp;#160;You can also check out Mike's article that lists the product features for each version of &lt;a target="_blank" href="http://mvasoftware.com/blogs/mikev_weblog/archive/2009/10/24/windows-7-visual-studio-2010-beta-2-team-development-for-all.aspx"&gt;Visual Studio 2010&lt;/a&gt;. &amp;#160;Check out our new course on &lt;a href="/LinkClick.aspx?link=http%3a%2f%2fwww.effectiveagiledev.com%2fAgileTraining%2fScrumAgileDevelopmentforTeamswithMSVSTFS%2ftabid%2f58%2fDefault.aspx&amp;amp;tabid=70"&gt;Scrum Using VS/TFS 2010&lt;/a&gt;!&lt;/p&gt;&lt;a href=http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/11/Visual-Studio-Team-Foundation-Sever-2010-to-Launch-on-March-22-2010.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/11/Visual-Studio-Team-Foundation-Sever-2010-to-Launch-on-March-22-2010.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/11/Visual-Studio-Team-Foundation-Sever-2010-to-Launch-on-March-22-2010.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/11/Visual-Studio-Team-Foundation-Sever-2010-to-Launch-on-March-22-2010.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 18:51:00 GMT</pubDate>
      <slash:comments>144</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=11</trackback:ping>
    </item>
    <item>
      <title>Bugs, bugs, BUGS!</title>
      <description>&lt;p&gt;&amp;#160;I'm sure that you all know the story of how the term "bug" got associated with a computer failure.&amp;#160;It was a moth in a computer which caused a hardware failure.&amp;#160;However, since then the term bug &amp;#160;has become synonymous with a software error.&amp;#160;There is a bug in the program.&amp;#160;Yes, there is a bug in the program, every program.&amp;#160;Many software development organizations spend a large portion of their time and effort finding and fixing bugs.&amp;#160;However the situation rarely improves.&amp;#160;&lt;span class="Apple-style-span" style="font-family: 'Helvetica Neue'; font-size: 11px; white-space: pre; "&gt;hbrfj8e3c4&lt;/span&gt;&lt;/p&gt;&lt;a href=http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/8/Bugs-bugs-BUGS.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/8/Bugs-bugs-BUGS.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/8/Bugs-bugs-BUGS.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.effectiveagiledev.com/Articles/tabid/70/EntryId/8/Bugs-bugs-BUGS.aspx</guid>
      <pubDate>Tue, 07 Jul 2009 17:04:00 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=8</trackback:ping>
    </item>
    <item>
      <title>Do you know your team's "room tone"?</title>
      <description>&lt;p&gt;&amp;#160;As a &lt;b&gt;ScrumMaster&lt;/b&gt; and &lt;b&gt;Agile Coach&lt;/b&gt;, I develop the same feeling about the team's work environment. Depending on the team the "room tone" will be different and in iterative development the tone will be different depending on the stage of the iteration the team is in.&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/2/Do-you-know-your-teams-room-tone.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/2/Do-you-know-your-teams-room-tone.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/2/Do-you-know-your-teams-room-tone.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/2/Do-you-know-your-teams-room-tone.aspx</guid>
      <pubDate>Mon, 06 Jul 2009 23:09:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=2</trackback:ping>
    </item>
    <item>
      <title>Scrum is a flexible process!</title>
      <description>&lt;p&gt;&amp;#160;I’m a white board and sticky type of agilest. Give me a team room with white boards and a bunch of multicolored stickys and I’m a happy camper! Why? Because I know that the white board and stickys are NOT the project, the people and the conversations they have with each other are the project and the white boards and stickys are used to drive those conversations and track the work.&amp;#160;However for most teams and most organizations, my agile dream project just does not exist and trying to force it to be is foolishness. Most organizations are going to need a tool to manage the project and provide&amp;#160;visibility&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/4/Scrum-is-a-flexible-process.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/4/Scrum-is-a-flexible-process.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/4/Scrum-is-a-flexible-process.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/4/Scrum-is-a-flexible-process.aspx</guid>
      <pubDate>Wed, 10 Jun 2009 08:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=4</trackback:ping>
    </item>
    <item>
      <title>Software Development Process Improvement  for Enterprise Sustainability, Why Scrum, Agile and Lean?</title>
      <description>&lt;p&gt;&amp;#160;There is a lot of information out there about why an organization would attempt to improve their software development process using any of the wide variety of methodologies, techniques, systems, coaches and mentors that market their message.&amp;#160;In fact there is so much information it is overwhelming to anyone genuinely trying to improve their process.&amp;#160;I've been out in the trenches for several years now and have seen many different approaches used with varying degrees of success.&amp;#160;In fact no two organizations have ever done the same thing or had the same results.&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/3/Software-Development-Process-Improvement-for-Enterprise-Sustainability-Why-Scrum-Agile-and-Lean.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/3/Software-Development-Process-Improvement-for-Enterprise-Sustainability-Why-Scrum-Agile-and-Lean.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/3/Software-Development-Process-Improvement-for-Enterprise-Sustainability-Why-Scrum-Agile-and-Lean.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/3/Software-Development-Process-Improvement-for-Enterprise-Sustainability-Why-Scrum-Agile-and-Lean.aspx</guid>
      <pubDate>Fri, 15 May 2009 08:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=3</trackback:ping>
    </item>
    <item>
      <title>Business Value Must Drive!</title>
      <description>&lt;p&gt;&amp;#160;Driving a software project to deliver later is just plain wrong!&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/5/Business-Value-Must-Drive.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/5/Business-Value-Must-Drive.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/5/Business-Value-Must-Drive.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/5/Business-Value-Must-Drive.aspx</guid>
      <pubDate>Tue, 21 Apr 2009 08:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=5</trackback:ping>
    </item>
    <item>
      <title>Really BIG Projects</title>
      <description>&lt;p&gt;&amp;#160;&amp;#160;I’ve been helping a pretty large team for a few months now.&amp;#160; Today I attended a user group meeting today on SecondLife delivered by Brian Harry of VSTS/TFS. &amp;#160;It is very clear that there are some issues that get exacerbated when you have a very large project. &amp;#160;&lt;/p&gt;&lt;a href=http://effectiveagiledev.com/Articles/tabid/70/EntryId/7/Really-BIG-Projects.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://effectiveagiledev.com/Articles/tabid/70/EntryId/7/Really-BIG-Projects.aspx</link>
      <author>rodclaar@effectiveagiledev.com</author>
      <comments>http://effectiveagiledev.com/Articles/tabid/70/EntryId/7/Really-BIG-Projects.aspx#Comments</comments>
      <guid isPermaLink="true">http://effectiveagiledev.com/Articles/tabid/70/EntryId/7/Really-BIG-Projects.aspx</guid>
      <pubDate>Thu, 16 Apr 2009 08:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.effectiveagiledev.com/DesktopModules/Blog/Trackback.aspx?id=7</trackback:ping>
    </item>
  </channel>
</rss>
