<?xml version="1.0" ?>
    <rss version="2.0">
    
    
    <channel>
    <title>ProjectManagement.com - Agile</title>
    <description>Agile</description>
    <link>http://www.projectmanagement.com/Agile/</link>
    <copyright>Copyright: (C) 2013 ProjectManagement.com</copyright>
    <lastBuildDate>Fri, 24 May 2013 09:05:01 GMT</lastBuildDate>
    <image>
    <title>ProjectManagement.com</title>
    <url>http://www.projectmanagement.com/design/logo.gif</url>
    <link>http://www.projectmanagement.com/Agile/</link>
    </image>
    
    <item>
    <title>Topic Teasers Vol. 9: Story Points or Hours?</title>
    <description>&lt;i&gt;&lt;b&gt;Question:&lt;/b&gt; My team prefers to work in Story Points, but it sometimes becomes hard to deal with the realities of how to estimate a first iteration and how to deal with the availability of the team members. How do experienced agile teams handle these realities?&lt;/i&gt;
&lt;table style=&quot;margin-left:20px;&quot; border=0&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;A.&lt;/td&gt; &lt;td&gt;If you want to be agile, you must estimate in Story Points. Nothing else will really work for a team once they begin to do the work of the project.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;B.&lt;/td&gt; &lt;td&gt;Neither is the correct approach. Estimate your Product Backlog in Ideal Hours, and then they will transfer over easily to the iteration work of the team.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;C.&lt;/td&gt; &lt;td&gt;If you create software, use Story Points. If you use agile for any other type of project, estimate in work hours, which you can input into MS Project.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;D.&lt;/td&gt; &lt;td&gt;Use Story Points for the Product Backlog, but actual hours for the Iteration Backlog.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/blockquote&gt;</description>
    <link>http://www.projectmanagement.com//articles//278710/Topic-Teasers-Vol--9--Story-Points-or-Hours-</link>
    <pubDate>Wed, 15 May 2013 04:00:00 GMT</pubDate>
    </item>
    
    <item>
    <title>Agile: What&apos;s in it for the Project Manager? (Part 1)</title>
    <description>Making a transition from what you&apos;re currently doing to an effective agile process is a project in itself--but it can easily be worth it. There are no guarantees, but let&apos;s look at what we can gain by adjusting our approach...</description>
    <link>http://www.projectmanagement.com//articles//278619/Agile--What-s-in-it-for-the-Project-Manager---Part-1-</link>
    <pubDate>Thu, 09 May 2013 04:00:00 GMT</pubDate>
    </item>
    
    <item>
    <title>Agile: What&apos;s in It for the Project Manager? (Part 2) </title>
    <description>Making a transition from what you&apos;re currently doing to an effective agile process is a project in itself--but it can easily be worth it. Let&apos;s look at what we can gain by adjusting our approach--our concluding installment looks at interpreting requirements and tracking progress, and offers some further caution and advice.</description>
    <link>http://www.projectmanagement.com//articles//278621/Agile--What-s-in-It-for-the-Project-Manager---Part-2--</link>
    <pubDate>Thu, 09 May 2013 04:00:00 GMT</pubDate>
    </item>
    
    <item>
    <title>How to be Extraordinarily Agile</title>
    <description>On an agile project, we often must accomplish the extraordinary. Yet how can we do so when we must work with such...ahem...ordinary people? Here are some suggestions for helping your group of ordinary individuals to accomplish the extraordinary on your agile project.</description>
    <link>http://www.projectmanagement.com//articles//278629/How-to-be-Extraordinarily-Agile</link>
    <pubDate>Thu, 09 May 2013 04:00:00 GMT</pubDate>
    </item>
    
    <item>
    <title>Topic Teasers Vol. 7: Using Agile Hardware</title>
    <description>&lt;i&gt;&lt;b&gt;Question:&lt;/b&gt; The software developers in my IT department are hardcore agileists. I maintain legacy systems and do operational work. Is there anything I need to know about the agile world that could affect my work with hardware?&lt;/i&gt;
&lt;table style=&quot;margin-left:20px;&quot; border=0&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;A.&lt;/td&gt; &lt;td&gt;Yes. Cloud computing is an agile practice and a major trend that will probably be discussed in your workplace soon. Learn about it so you don&apos;t look dated and out of touch.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;B.&lt;/td&gt; &lt;td&gt;No. Agile is only for software developers at large shops like Google who need to support online retail sales and search engine banks.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;C.&lt;/td&gt; &lt;td&gt;Yes. All hardware purchase and installation projects should be converted to a Scrum process for the greatest impact and cohesion between teams.&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td width=&quot;10&quot; align=&quot;right&quot; valign=&quot;top&quot;&gt;D.&lt;/td&gt; &lt;td&gt;No. The government has legislation pending to block agile practices as potential antitrust violations.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/blockquote&gt;</description>
    <link>http://www.projectmanagement.com//articles//278207/Topic-Teasers-Vol--7--Using-Agile-Hardware</link>
    <pubDate>Mon, 15 Apr 2013 04:00:00 GMT</pubDate>
    </item>
    
    <item>
    <title>Injecting Extreme Customer Intimacy Into Your Project Team</title>
    <description>Have you noticed any hints that your company isn&apos;t customer intimate? Companies and their supportive corporate culture sometimes say one thing and yet practice another. Learn how to inspire your team to be customer intimate--in part by utilizing agile, which takes this approach to heart and emphasizes customer-centric product development.</description>
    <link>http://www.projectmanagement.com//articles//278107/Injecting-Extreme-Customer-Intimacy-Into-Your-Project-Team</link>
    <pubDate>Mon, 08 Apr 2013 04:00:00 GMT</pubDate>
    </item>
    
    
    </channel>
    </rss>
    
