<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://danube.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Danube - Who is on the Scrum Team? - Comments</title>
 <link>http://danube.com/blog/michaeljames/who_is_on_the_scrum_team</link>
 <description>Comments for &quot;Who is on the Scrum Team?&quot;</description>
 <language>en</language>
<item>
 <title>shippable vs. sellable</title>
 <link>http://danube.com/blog/michaeljames/who_is_on_the_scrum_team#comment-5475</link>
 <description>&lt;p&gt;To help people get what DrDan&#039;s saying here, I sometimes explain &quot;potentially shippable&quot; does not mean &quot;potentially sellable.&quot;  We might have &quot;Hello World!&quot; fully tested, refactored, and documented.  But not many would buy it until we get more stories done.  &lt;/p&gt;
&lt;p&gt;&quot;Potentially shippable&quot; is mostly a technical distinction, while &quot;potentially sellable&quot; is a Product Owner call.&lt;/p&gt;
&lt;p&gt;--mj&lt;/p&gt;
</description>
 <pubDate>Mon, 23 Jun 2008 18:00:50 -0500</pubDate>
 <dc:creator>MichaelJames</dc:creator>
 <guid isPermaLink="false">comment 5475 at http://danube.com</guid>
</item>
<item>
 <title>Comment on &quot;potentially shippable&quot;</title>
 <link>http://danube.com/blog/michaeljames/who_is_on_the_scrum_team#comment-5474</link>
 <description>&lt;p&gt;MJ states, above, that the team&#039;s job is to produce an increment of &lt;em&gt;potentially shippable product&lt;/em&gt; every sprint. This is the party line, and I believe it, but I get lots of questions about what &lt;em&gt;potentially shippable product&lt;/em&gt; means. It does &lt;strong&gt;not&lt;/strong&gt; mean &lt;em&gt;shippable&lt;/em&gt;, as that is way too high a bar. We develop stories (PBIs), that combine to produce shippable features - it makes no sense for a story to be shippable by itself, IMHO. &lt;/p&gt;
&lt;p&gt;What we mean is, if the feature is shippable (from a functionality perspective), then each of the stories that makes up the feature is shippable (from a quality perspective). So, stories that are &lt;em&gt;done&lt;/em&gt; have the quality they need to be able to ship them, which means that the feature they are part of can be shipped as soon as it is functional - no waiting time to add in the quality! The way I refer to this is that the stories are &lt;em&gt;demonstrably done&lt;/em&gt; every sprint.&lt;/p&gt;
&lt;p&gt;Same concept, different words.&lt;/p&gt;
&lt;p&gt;Dan  ;-)&lt;/p&gt;
&lt;p&gt;dan@danube.com&lt;br /&gt;
Dan Rawsthorne, PhD, CST&lt;br /&gt;
Transformation Coach&lt;br /&gt;
http://www.danube.com&lt;/p&gt;
</description>
 <pubDate>Mon, 23 Jun 2008 14:37:37 -0500</pubDate>
 <dc:creator>Dan Rawsthorne</dc:creator>
 <guid isPermaLink="false">comment 5474 at http://danube.com</guid>
</item>
<item>
 <title>Who is on the Scrum Team?</title>
 <link>http://danube.com/blog/michaeljames/who_is_on_the_scrum_team</link>
 <description>&lt;p&gt;A Scrum Team is:
&lt;ul&gt;
&lt;li&gt;A Product Owner&lt;/li&gt;
&lt;li&gt;A Scrum Development Team&lt;/li&gt;
&lt;li&gt;A ScrumMaster&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&quot;http://danube.com/blog/michaeljames/who_is_on_the_scrum_team&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://danube.com/blog/michaeljames/who_is_on_the_scrum_team#comment</comments>
 <enclosure url="http://danube.com/system/files/Who+Is+on+the+Scrum+Team+blog.pdf" length="149148" type="application/pdf" />
 <pubDate>Mon, 23 Jun 2008 13:38:51 -0500</pubDate>
 <dc:creator>MichaelJames</dc:creator>
 <guid isPermaLink="false">1075 at http://danube.com</guid>
</item>
</channel>
</rss>
