<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.dzone.com/~d/styles/itemcontent.css"?><rss xmlns:dz="http://www.developerzone.com/modules/dz/1.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0" xml:base="http://agile.dzone.com/">
  <channel>
    <title>Agile Zone - Software Methodologies for Development Managers</title>
    <link>http://agile.dzone.com/</link>
    <description />
    <language>en</language>
          <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.dzone.com/zones/agile" type="application/rss+xml" /><item>
    <title>Accounting for Bugs in an Agile World - How we do it </title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/qLE1xhpsyk8/accounting-bugs-agile-world</link>
    <description>Today I'd like to share with you a really
important aspect of Agile software development - how to account for
bugs in your daily plans.
I am frequently asked by teams I consult with how to deal with bugs if
you're Agile and using Scrum. Questions like the following come up time
and time again:
&amp;quot;Should I track hours burned fixing bugs?&amp;quot;
&amp;quot;Should the hours burned on fixing bugs count...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/qLE1xhpsyk8" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/articles/accounting-bugs-agile-world#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <category domain="http://agile.dzone.com/category/tags/bugs">bugs</category>
 <category domain="http://agile.dzone.com/category/tags/capacity">capacity</category>
 <category domain="http://agile.dzone.com/category/tags/scrum">scrum</category>
 <category domain="http://agile.dzone.com/category/tags/teams">teams</category>
 <category domain="http://agile.dzone.com/category/tags/velocity">velocity</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11155</wfw:commentRss>
 <dz:submitDate>Sun, 05 Jul 2009 10:21:37 -0400</dz:submitDate>
 <dz:readCount>111</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>Agilebuddy</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-406666.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Sun, 05 Jul 2009 14:21:37 +0000</pubDate>
 <dc:creator>Agilebuddy</dc:creator>
 <guid isPermaLink="false">11155 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/articles/accounting-bugs-agile-world</feedburner:origLink></item>
  <item>
    <title>Agile Architecture Requires Modularity</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/rlksynaz02U/agile-architecture-requires</link>
    <description>A few weeks ago, I presented my view of agile architecture, and followed that up with a post on DZone
that presented two aspects of agile architecture. A process aspect,
which is temporal, and a structural aspect. Here, I embellish.References
      Reference:&amp;nbsp;
    
            
                    Agile Architecture Requires Modularity        
        


    
            
                   ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/rlksynaz02U" height="1" width="1"/&gt;</description>
     <comments>http://architects.dzone.com/news/agile-architecture-requires#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11350</wfw:commentRss>
 <dz:submitDate>Wed, 24 Jun 2009 06:43:56 -0400</dz:submitDate>
 <dz:readCount>735</dz:readCount>
 <dz:commentCount>1</dz:commentCount>
 <dz:submitter> <dz:username>kirkk</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-238461.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Wed, 24 Jun 2009 10:43:56 +0000</pubDate>
 <dc:creator>kirkk</dc:creator>
 <guid isPermaLink="false">11350 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://architects.dzone.com/news/agile-architecture-requires</feedburner:origLink></item>
  <item>
    <title>Career 2.0: Take Control of Your Life</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/VWjIbnUnHP8/career-20-take-control-your</link>
    <description>ISBN or ASIN:&amp;nbsp;
    
            
                    B00262MTOA        
        


      Cover Image:&amp;nbsp;
    
            
                    31EHsHI4p6L._SL500_AA240_.jpg        
        


      Book Author(s):&amp;nbsp;
    
            
                    Jared Richardson        
              
                    Matthew Bass        
        


      Publisher:&amp;nbsp;
    
      ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/VWjIbnUnHP8" height="1" width="1"/&gt;</description>
     <comments>http://books.dzone.com/reviews/career-20-take-control-your#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/career">Career</category>
 <category domain="http://agile.dzone.com/category/tags/developer">Developer</category>
 <category domain="http://agile.dzone.com/category/tags/goals">goals</category>
 <category domain="http://agile.dzone.com/category/tags/speaking">speaking</category>
 <category domain="http://agile.dzone.com/category/tags/strategy">strategy</category>
 <category domain="http://agile.dzone.com/category/tags/writing">writing</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11110</wfw:commentRss>
 <dz:submitDate>Wed, 17 Jun 2009 12:13:04 -0400</dz:submitDate>
 <dz:readCount>1187</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>mstine</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-197149.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Wed, 17 Jun 2009 16:13:04 +0000</pubDate>
 <dc:creator>mstine</dc:creator>
 <guid isPermaLink="false">11110 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://books.dzone.com/reviews/career-20-take-control-your</feedburner:origLink></item>
  <item>
    <title>Test Infecting Your Team</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/C4356n76Zfc/test-infecting-your-team</link>
    <description>Recently, a simple question was posed to the Yahoo Test Driven Development (TDD) group. I've seen situations where the person on a team you would single out to infect produces a high level of quality of code without unit testing. In this case you have to show the leader that their team could produce more value if they were to adopt unit testing, even when the difference it makes for them is...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/C4356n76Zfc" height="1" width="1"/&gt;</description>
     <comments>http://java.dzone.com/news/test-infecting-your-team#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/tdd">TDD</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11107</wfw:commentRss>
 <dz:submitDate>Fri, 12 Jun 2009 11:06:16 -0400</dz:submitDate>
 <dz:readCount>2932</dz:readCount>
 <dz:commentCount>7</dz:commentCount>
 <dz:submitter> <dz:username>kirkk</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-238461.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 12 Jun 2009 15:06:16 +0000</pubDate>
 <dc:creator>kirkk</dc:creator>
 <guid isPermaLink="false">11107 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://java.dzone.com/news/test-infecting-your-team</feedburner:origLink></item>
  <item>
    <title>The Scrum of Scrums</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/RIVWkFxKvII/scrum-scrums</link>
    <description>It is sometimes said that agile software development methods, such as Scrum, are ideal for small projects being delivered by small teams.Personally I would certainly agree that Scrum is ideal for small, multi-disciplined, co-located teams, working on a common purpose.References
      Reference:&amp;nbsp;
    
            
                    Using Scrum on Larger Projects: &amp;quot;The Scrum of...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/RIVWkFxKvII" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/scrum-scrums#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11086</wfw:commentRss>
 <dz:submitDate>Thu, 11 Jun 2009 08:42:47 -0400</dz:submitDate>
 <dz:readCount>246</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>kswaters</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-222612.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Thu, 11 Jun 2009 12:42:47 +0000</pubDate>
 <dc:creator>kswaters</dc:creator>
 <guid isPermaLink="false">11086 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/scrum-scrums</feedburner:origLink></item>
  <item>
    <title>Tough times out there - Scrum can show you the way out! </title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/LwlvZLrMqh4/tough-times-out-there-scrum</link>
    <description>&amp;quot;In these tough economic times&amp;quot; I've heard this so many times it's
starting to annoy me. Yet, this little proverb is sublimely relevant;
it taps into the psyche of consumers and businesses alike who continue
to say to themselves &amp;quot;Can we afford this?&amp;quot; Corollary to the fear,
budgets shrink, revenues disappear, and company objectives change from
thriving to surviving. As the...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/LwlvZLrMqh4" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/articles/tough-times-out-there-scrum#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11038</wfw:commentRss>
 <dz:submitDate>Wed, 10 Jun 2009 09:35:15 -0400</dz:submitDate>
 <dz:readCount>384</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>Agilebuddy</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-406666.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Wed, 10 Jun 2009 13:35:15 +0000</pubDate>
 <dc:creator>Agilebuddy</dc:creator>
 <guid isPermaLink="false">11038 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/articles/tough-times-out-there-scrum</feedburner:origLink></item>
  <item>
    <title>Defining Kanban</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/iawt4QjHnWk/defining-kanban</link>
    <description>There has been a long thread in the kanbandev group at Yahoo about
how to define what a kanban system is, and is not. Defining kanban is
important because without an unambiguous definition it is difficult to
discuss kanban.A kanban system is a system
for process control. Kanban was invented by Taichi Ohno at Toyota more
than fifty years ago. There are many types of kanban systems, for
production...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/iawt4QjHnWk" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/defining-kanban#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11049</wfw:commentRss>
 <dz:submitDate>Tue, 09 Jun 2009 09:21:35 -0400</dz:submitDate>
 <dz:readCount>2267</dz:readCount>
 <dz:commentCount>4</dz:commentCount>
 <dz:submitter> <dz:username>Henrik.Martensson</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-328929.png</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 09 Jun 2009 13:21:35 +0000</pubDate>
 <dc:creator>Henrik.Martensson</dc:creator>
 <guid isPermaLink="false">11049 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/defining-kanban</feedburner:origLink></item>
  <item>
    <title>Three Levels of Control (Example)</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/nggX-RMmlj4/three-levels-control-example</link>
    <description>In my last post I told you about the three levels of control
for managers. I didn't have much time to go into details then, and it
was no surprise to see several readers asking for specific examples. I
am glad to oblige now, because like you I'm also trying to figure out
how these ideas would apply to my daily business.
Let's review the three levels again:References
      Reference:&amp;nbsp;
    
  ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/nggX-RMmlj4" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/three-levels-control-example#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/11001</wfw:commentRss>
 <dz:submitDate>Mon, 08 Jun 2009 09:07:48 -0400</dz:submitDate>
 <dz:readCount>163</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>jurgenappelo</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-284687.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Mon, 08 Jun 2009 13:07:48 +0000</pubDate>
 <dc:creator>jurgenappelo</dc:creator>
 <guid isPermaLink="false">11001 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/three-levels-control-example</feedburner:origLink></item>
  <item>
    <title>The Product Owner - Top 10 Responsibilities</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/cDVgGg5WkdA/product-owner-top-10</link>
    <description>Over the course of the past 5 years, I have
often been asked about the role the Product Owner plays in an Agile
company. More recently in a rather controversial blog post by Adam Bullied he raised the question – Is there such a thing as an Agile Product Manager?









	

From my experience, there is. And this role in Scrum is defined as the
Product Owner. The Product Owner from my experience...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/cDVgGg5WkdA" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/articles/product-owner-top-10#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10896</wfw:commentRss>
 <dz:submitDate>Fri, 05 Jun 2009 09:25:45 -0400</dz:submitDate>
 <dz:readCount>966</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>Agilebuddy</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-406666.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 05 Jun 2009 13:25:45 +0000</pubDate>
 <dc:creator>Agilebuddy</dc:creator>
 <guid isPermaLink="false">10896 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/articles/product-owner-top-10</feedburner:origLink></item>
  <item>
    <title>To Estimate or Not - That Is the Question</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/mSdbhrrwz0U/estimate-or-not-question</link>
    <description>Lean software development shares many of the key principles of agile software development.Although one of the key aspects of lean development is all about identifying and eliminating waste from the development process...References
      Reference:&amp;nbsp;
    
            
                    To Estimate or Not To Estimate? That is the Question!        
        


    
            
                ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/mSdbhrrwz0U" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/estimate-or-not-question#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10949</wfw:commentRss>
 <dz:submitDate>Wed, 03 Jun 2009 11:41:34 -0400</dz:submitDate>
 <dz:readCount>473</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>kswaters</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-222612.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Wed, 03 Jun 2009 15:41:34 +0000</pubDate>
 <dc:creator>kswaters</dc:creator>
 <guid isPermaLink="false">10949 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/estimate-or-not-question</feedburner:origLink></item>
  <item>
    <title>Agile Product Manager in the Enterprise (3): Responsibility-Owning the Vision</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/g5vs83J4bqI/agile-product-manager</link>
    <description>Note:
this is the third in a series of posts on the changing role of product
management as the enterprise transitions to agile development methods.
This series in turn, is a continuation of the series on the Role of
Product Manager and Product Owner in the Agile Enterprise which can be
found in the Product Manager/Product Owner series on this blog as well as a series in the Agile...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/g5vs83J4bqI" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/agile-product-manager#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile-adoption">agile adoption</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10898</wfw:commentRss>
 <dz:submitDate>Mon, 01 Jun 2009 13:01:35 -0400</dz:submitDate>
 <dz:readCount>312</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>deanleffingwell@gmail.com</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-328295.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Mon, 01 Jun 2009 17:01:35 +0000</pubDate>
 <dc:creator>deanleffingwell@gmail.com</dc:creator>
 <guid isPermaLink="false">10898 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/agile-product-manager</feedburner:origLink></item>
  <item>
    <title>Recommended Books on Agile</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/XOadcyguKAk/recommended-books-agile</link>
    <description>Quite frequently I am out talking to traditional project managers
or new agile teams that want to learn a little bit more about all this
agile stuff. Inevitibly I get asked what books I recommend for folks
trying to sharpen their agile chops. Thought I would share a few that I
recommend the most with a few words on why I think they are important:References
      Reference:&amp;nbsp;
    
           ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/XOadcyguKAk" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/recommended-books-agile#comments</comments>
 <category domain="http://agile.dzone.com/category/tags/agile">agile</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10860</wfw:commentRss>
 <dz:submitDate>Fri, 29 May 2009 09:09:04 -0400</dz:submitDate>
 <dz:readCount>500</dz:readCount>
 <dz:commentCount>2</dz:commentCount>
 <dz:submitter> <dz:username>mcottmeyer</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-329138.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Fri, 29 May 2009 13:09:04 +0000</pubDate>
 <dc:creator>mcottmeyer</dc:creator>
 <guid isPermaLink="false">10860 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/recommended-books-agile</feedburner:origLink></item>
  <item>
    <title>Self-Organization (Part 3)</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/TRT75Jwb0D4/self-organization-part-3</link>
    <description>In part 1 and part 2 of this multi-post article I told you that self-organization does not distinguish between valuable and harmful results. This distinction is only made by humans, because we have learned to assign value to things. And command-and-control was invented to consciously steer self-organization towards that which is valuable. Like health. And gold.References
      Reference:&amp;nbsp;
  ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/TRT75Jwb0D4" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/self-organization-part-3#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10667</wfw:commentRss>
 <dz:submitDate>Wed, 27 May 2009 09:58:01 -0400</dz:submitDate>
 <dz:readCount>777</dz:readCount>
 <dz:commentCount>1</dz:commentCount>
 <dz:submitter> <dz:username>jurgenappelo</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-284687.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Wed, 27 May 2009 13:58:01 +0000</pubDate>
 <dc:creator>jurgenappelo</dc:creator>
 <guid isPermaLink="false">10667 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/self-organization-part-3</feedburner:origLink></item>
  <item>
    <title>Introducing Kanban, Flow, and Cadence</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/ZhIPSSvAkgQ/introducing-kanban-flow-and</link>
    <description>There has been some noticeable increase in interest in Kanban
recently, with a number of people asking for more basic info, and more
people writing new blogs and articles.  This is my attempt to describe
in more detail my take on it all, which I refer to as Kanban, Flow and
Cadence.References
      Reference:&amp;nbsp;
    
            
                    Kanban, Flow and Cadence        
       ...&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/ZhIPSSvAkgQ" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/news/introducing-kanban-flow-and#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10651</wfw:commentRss>
 <dz:submitDate>Tue, 26 May 2009 09:15:13 -0400</dz:submitDate>
 <dz:readCount>4008</dz:readCount>
 <dz:commentCount>2</dz:commentCount>
 <dz:submitter> <dz:username>kjscotland</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-418601.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Tue, 26 May 2009 13:15:13 +0000</pubDate>
 <dc:creator>kjscotland</dc:creator>
 <guid isPermaLink="false">10651 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/news/introducing-kanban-flow-and</feedburner:origLink></item>
  <item>
    <title>Why have a Product Owner anyway?</title>
    <link>http://feeds.dzone.com/~r/zones/agile/~3/QHYxj66j9Lk/why-have-product-owner-anyway</link>
    <description>I can’t stress enough just how important the role of the Product Owner really is. This job is not for the faint-of-heart.
In fact, the Product Owner is probably the most important individual on
the Scrum team since he single-handedly is responsible for driving the
direction the team is taking. 

The Product Owner And The Team&lt;img src="http://feeds.feedburner.com/~r/zones/agile/~4/QHYxj66j9Lk" height="1" width="1"/&gt;</description>
     <comments>http://agile.dzone.com/articles/why-have-product-owner-anyway#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://agile.dzone.com/crss/node/10728</wfw:commentRss>
 <dz:submitDate>Mon, 25 May 2009 11:29:16 -0400</dz:submitDate>
 <dz:readCount>268</dz:readCount>
 <dz:commentCount>0</dz:commentCount>
 <dz:submitter> <dz:username>Agilebuddy</dz:username>
 <dz:userimage>http://agile.dzone.com/sites/all/files/avatars/picture-406666.jpg</dz:userimage>
</dz:submitter>
 <pubDate>Mon, 25 May 2009 15:29:16 +0000</pubDate>
 <dc:creator>Agilebuddy</dc:creator>
 <guid isPermaLink="false">10728 at http://agile.dzone.com</guid>
  <feedburner:origLink>http://agile.dzone.com/articles/why-have-product-owner-anyway</feedburner:origLink></item>
  </channel>
</rss>
