<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Silver Stripe Blog</title>
	<atom:link href="http://www.silverstripesoftware.com/blog/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.silverstripesoftware.com/blog</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 15:42:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Control Charts in Silver Catalyst by David Joyce</title>
		<link>http://www.silverstripesoftware.com/blog/archives/246/comment-page-1#comment-159150</link>
		<dc:creator>David Joyce</dc:creator>
		<pubDate>Thu, 18 Mar 2010 15:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=246#comment-159150</guid>
		<description>Great addition, and a first. Are you planning on enabling the user to split the data?  For example if a team makes a big change they can split the data on the SPC chart to see the effect. This would then recalculate a new UCL and mean post split. An example of this is shown here http://www.vanguardcapchart.com/SplittingTheData.aspx</description>
		<content:encoded><![CDATA[<p>Great addition, and a first. Are you planning on enabling the user to split the data?  For example if a team makes a big change they can split the data on the SPC chart to see the effect. This would then recalculate a new UCL and mean post split. An example of this is shown here <a href="http://www.vanguardcapchart.com/SplittingTheData.aspx" rel="nofollow">http://www.vanguardcapchart.com/SplittingTheData.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Control Charts in Silver Catalyst by David J Anderson</title>
		<link>http://www.silverstripesoftware.com/blog/archives/246/comment-page-1#comment-159131</link>
		<dc:creator>David J Anderson</dc:creator>
		<pubDate>Thu, 18 Mar 2010 07:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=246#comment-159131</guid>
		<description>Wow! This is awesome!

Who would have believed that an Agile project management tool would embrace and support a quantitative method like SPC? This will prove a big enabler for people using Kanban as a catalyst to a Lean approach and kaizen culture in their organizations. This will really encourage more organizations to pursue high maturity behaviors. More higher maturity agile teams and organizations can only be good for our profession and industry. Thanks for showing leadership and making this happen.</description>
		<content:encoded><![CDATA[<p>Wow! This is awesome!</p>
<p>Who would have believed that an Agile project management tool would embrace and support a quantitative method like SPC? This will prove a big enabler for people using Kanban as a catalyst to a Lean approach and kaizen culture in their organizations. This will really encourage more organizations to pursue high maturity behaviors. More higher maturity agile teams and organizations can only be good for our profession and industry. Thanks for showing leadership and making this happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compensation Systems For Agile Teams by siddharta</title>
		<link>http://www.silverstripesoftware.com/blog/archives/207/comment-page-1#comment-147564</link>
		<dc:creator>siddharta</dc:creator>
		<pubDate>Fri, 26 Feb 2010 18:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/archives/207#comment-147564</guid>
		<description>Yeah, though its not easy unless you are creating a new company from scratch</description>
		<content:encoded><![CDATA[<p>Yeah, though its not easy unless you are creating a new company from scratch</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compensation Systems For Agile Teams by Ramprasad</title>
		<link>http://www.silverstripesoftware.com/blog/archives/207/comment-page-1#comment-146835</link>
		<dc:creator>Ramprasad</dc:creator>
		<pubDate>Thu, 25 Feb 2010 15:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/archives/207#comment-146835</guid>
		<description>Very nice.This requires a culture change in organizations and we need to work really hard to bring this in.</description>
		<content:encoded><![CDATA[<p>Very nice.This requires a culture change in organizations and we need to work really hard to bring this in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Questioning the end of sprint demo by Bob MacNeal</title>
		<link>http://www.silverstripesoftware.com/blog/archives/229/comment-page-1#comment-138985</link>
		<dc:creator>Bob MacNeal</dc:creator>
		<pubDate>Sat, 06 Feb 2010 19:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=229#comment-138985</guid>
		<description>The distinction you make about having a Sprint demo simply to show progress rather than to get actionable feedback is an important one. Thanks for reminding us!</description>
		<content:encoded><![CDATA[<p>The distinction you make about having a Sprint demo simply to show progress rather than to get actionable feedback is an important one. Thanks for reminding us!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From Scrum to Kanban by siddharta</title>
		<link>http://www.silverstripesoftware.com/blog/archives/172/comment-page-1#comment-138759</link>
		<dc:creator>siddharta</dc:creator>
		<pubDate>Tue, 02 Feb 2010 16:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/archives/172#comment-138759</guid>
		<description>Mario, then why bother with the Sprint plan meeting? Let the team do whatever they can in the sprint and what is done in the end gets delivered.</description>
		<content:encoded><![CDATA[<p>Mario, then why bother with the Sprint plan meeting? Let the team do whatever they can in the sprint and what is done in the end gets delivered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Evolving from ad-hoc to Agile to Kanban by Questioning the end of sprint demo &#187; Silver Stripe Blog &#187; Blog Archive</title>
		<link>http://www.silverstripesoftware.com/blog/archives/221/comment-page-1#comment-138658</link>
		<dc:creator>Questioning the end of sprint demo &#187; Silver Stripe Blog &#187; Blog Archive</dc:creator>
		<pubDate>Mon, 01 Feb 2010 04:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=221#comment-138658</guid>
		<description>[...] I explained in my talk at Agile Bengaluru (Slide 13), one problem that we faced was we were too focused on building increments of software, [...]</description>
		<content:encoded><![CDATA[<p>[...] I explained in my talk at Agile Bengaluru (Slide 13), one problem that we faced was we were too focused on building increments of software, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Evolving from ad-hoc to Agile to Kanban by siddharta</title>
		<link>http://www.silverstripesoftware.com/blog/archives/221/comment-page-1#comment-138585</link>
		<dc:creator>siddharta</dc:creator>
		<pubDate>Sat, 30 Jan 2010 05:15:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=221#comment-138585</guid>
		<description>One of the ways is by getting an end user to come in and try out the product and provide feedback. This is something that user experience professionals are good at. A lot of their work is about talking to end users. Alistair Cockburn talks about easy access to expert user. The expert user could be anyone. You don&#039;t have to rely on only the customer to give feedback.</description>
		<content:encoded><![CDATA[<p>One of the ways is by getting an end user to come in and try out the product and provide feedback. This is something that user experience professionals are good at. A lot of their work is about talking to end users. Alistair Cockburn talks about easy access to expert user. The expert user could be anyone. You don&#8217;t have to rely on only the customer to give feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is velocity a useful metric? by siddharta</title>
		<link>http://www.silverstripesoftware.com/blog/archives/224/comment-page-1#comment-138584</link>
		<dc:creator>siddharta</dc:creator>
		<pubDate>Sat, 30 Jan 2010 04:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=224#comment-138584</guid>
		<description>Most teams seem to have wildly oscillating velocity. An average velocity of 20 is more likely to go 12, 22, 24, 15, 27 rather than 19, 20, 20, 21, 20. 

Have you experienced stable velocity?</description>
		<content:encoded><![CDATA[<p>Most teams seem to have wildly oscillating velocity. An average velocity of 20 is more likely to go 12, 22, 24, 15, 27 rather than 19, 20, 20, 21, 20. </p>
<p>Have you experienced stable velocity?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is velocity a useful metric? by Mick Maguire</title>
		<link>http://www.silverstripesoftware.com/blog/archives/224/comment-page-1#comment-138562</link>
		<dc:creator>Mick Maguire</dc:creator>
		<pubDate>Fri, 29 Jan 2010 15:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.silverstripesoftware.com/blog/?p=224#comment-138562</guid>
		<description>&quot;But if velocity is a measure of capacity, then we should not cut the velocity for partial work and get a boost next sprint when a tiny bit of work is done to complete it.&quot;

Given what we use it for - this is not a helpful practice, but given how much impact it has across sprints / how infrequently it occurs it becomes noise. Therefore it doesn&#039;t interfere with what it is - a measure of capacity used for predictive calculations and an indicator of productivity variance. 

My 2 cents</description>
		<content:encoded><![CDATA[<p>&#8220;But if velocity is a measure of capacity, then we should not cut the velocity for partial work and get a boost next sprint when a tiny bit of work is done to complete it.&#8221;</p>
<p>Given what we use it for &#8211; this is not a helpful practice, but given how much impact it has across sprints / how infrequently it occurs it becomes noise. Therefore it doesn&#8217;t interfere with what it is &#8211; a measure of capacity used for predictive calculations and an indicator of productivity variance. </p>
<p>My 2 cents</p>
]]></content:encoded>
	</item>
</channel>
</rss>
