<?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 on: What&#8217;s So Great About Flow?</title>
	<atom:link href="http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/</link>
	<description>Adopt, Scale and Succeed with Agile Development</description>
	<lastBuildDate>Wed, 17 Mar 2010 14:33:06 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bachan</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4413</link>
		<dc:creator>Bachan</dc:creator>
		<pubDate>Sat, 24 Oct 2009 04:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4413</guid>
		<description>At this point in our Agile implementation we rely solely on story position for estimation and release plannig . Team pulls from the backlog during the sprint planning and there is no command and control on how much they pull, team know about the avreage velocity and more or less pulls the story points based on the velocity and if they wrap up story points during the Sprint period they take up additional tasks if it can be finsihed during the Sprint cycle.
We are defnietly following the 5 points you notes about , So how can you tell if your team has embraced Flow?

Do you think we should be looking the total hours  for the resources and use those for estiamtion and release planning over story points and team velocity</description>
		<content:encoded><![CDATA[<p>At this point in our Agile implementation we rely solely on story position for estimation and release plannig . Team pulls from the backlog during the sprint planning and there is no command and control on how much they pull, team know about the avreage velocity and more or less pulls the story points based on the velocity and if they wrap up story points during the Sprint period they take up additional tasks if it can be finsihed during the Sprint cycle.<br />
We are defnietly following the 5 points you notes about , So how can you tell if your team has embraced Flow?</p>
<p>Do you think we should be looking the total hours  for the resources and use those for estiamtion and release planning over story points and team velocity</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RickS</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4386</link>
		<dc:creator>RickS</dc:creator>
		<pubDate>Fri, 23 Oct 2009 00:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4386</guid>
		<description>Ok, I guess I don&#039;t get the idea of &#039;Flow&#039;. We&#039;re already scheduling only 5.5 hours of work per person. I though the idea of story points, spikes, and story decomposition was the recommended way to handle uncertainty and to build in some slack into stories. Are you saying that there needs to be additional slack built in? if so, then should we increase the amount of available time(say to 7 hrs/day), so that with slack built-in, we can get about 5 hours of work?</description>
		<content:encoded><![CDATA[<p>Ok, I guess I don&#8217;t get the idea of &#8216;Flow&#8217;. We&#8217;re already scheduling only 5.5 hours of work per person. I though the idea of story points, spikes, and story decomposition was the recommended way to handle uncertainty and to build in some slack into stories. Are you saying that there needs to be additional slack built in? if so, then should we increase the amount of available time(say to 7 hrs/day), so that with slack built-in, we can get about 5 hours of work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4033</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Thu, 24 Sep 2009 20:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4033</guid>
		<description>LOL!!!!  Should Sarah give Walter &quot;Extreme Makeover&quot; tips on his mustache as well as Agile adoption tips?  Hope your market testing and Agile adoption are both now on terra firma :- )</description>
		<content:encoded><![CDATA[<p>LOL!!!!  Should Sarah give Walter &#8220;Extreme Makeover&#8221; tips on his mustache as well as Agile adoption tips?  Hope your market testing and Agile adoption are both now on terra firma :- )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4032</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 24 Sep 2009 19:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4032</guid>
		<description>Walter is why I shaved my mustache!  A career counselor told me they don&#039;t market test well :-)</description>
		<content:encoded><![CDATA[<p>Walter is why I shaved my mustache!  A career counselor told me they don&#8217;t market test well :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4027</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Tue, 22 Sep 2009 18:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4027</guid>
		<description>I have had experience with a few skeptical/resistant Walters in my life as an Agile coach. I&#039;ve dealt with this in organizations small, medium, and large. My attempt at a humorous portrayal may have gotten in the way of portraying my real life experiences with these Project Managers and Directors.

I honestly ran into a group just last year who told me that they had been &quot;doing Agile&quot; for a while. They had been taught by their CTO who had &quot;done Agile&quot; at a previous company. And this is the truth: they were required to be 100% allocated. Their Sprint plan and all the tasks and estimates in it had to account for 100% of everyone&#039;s time in the Sprint timebox. This mindset was exacerbated by the team practice (dictated by the CTO) to therefore put in all their vacation time, holidays, and even book club meetings as part of their commitment in the Sprint. 

I had a really really tough time talking with them about only committing to delivery of valued items as their Sprint commitment, AND that that should not equate to 100% of their available time within a Sprint&#039;s timebox.

One other thing. This situation also indicated that a lot of command-and control still existed and that there were no retrospectives to inspect and adapt practices and team agreements.

I think the team could have really used a Sarah (though much nicer and less snotty than the one I thrust on Walter) I am hopeful that no one would view me as an Agile coach like Sarah :-)

Thanks for your comments.</description>
		<content:encoded><![CDATA[<p>I have had experience with a few skeptical/resistant Walters in my life as an Agile coach. I&#8217;ve dealt with this in organizations small, medium, and large. My attempt at a humorous portrayal may have gotten in the way of portraying my real life experiences with these Project Managers and Directors.</p>
<p>I honestly ran into a group just last year who told me that they had been &#8220;doing Agile&#8221; for a while. They had been taught by their CTO who had &#8220;done Agile&#8221; at a previous company. And this is the truth: they were required to be 100% allocated. Their Sprint plan and all the tasks and estimates in it had to account for 100% of everyone&#8217;s time in the Sprint timebox. This mindset was exacerbated by the team practice (dictated by the CTO) to therefore put in all their vacation time, holidays, and even book club meetings as part of their commitment in the Sprint. </p>
<p>I had a really really tough time talking with them about only committing to delivery of valued items as their Sprint commitment, AND that that should not equate to 100% of their available time within a Sprint&#8217;s timebox.</p>
<p>One other thing. This situation also indicated that a lot of command-and control still existed and that there were no retrospectives to inspect and adapt practices and team agreements.</p>
<p>I think the team could have really used a Sarah (though much nicer and less snotty than the one I thrust on Walter) I am hopeful that no one would view me as an Agile coach like Sarah :-)</p>
<p>Thanks for your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4026</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Tue, 22 Sep 2009 17:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4026</guid>
		<description>I think Walter (minus the irony, of course) is not too far off from Project Managers trying to adopt Agile just to go with the stream, which, IMO, is a big mistake.

Agile is getting bigger by the day right now, and the problem with it is that a lot of people have different understandings of what Agile really is.</description>
		<content:encoded><![CDATA[<p>I think Walter (minus the irony, of course) is not too far off from Project Managers trying to adopt Agile just to go with the stream, which, IMO, is a big mistake.</p>
<p>Agile is getting bigger by the day right now, and the problem with it is that a lot of people have different understandings of what Agile really is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricky</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4023</link>
		<dc:creator>Ricky</dc:creator>
		<pubDate>Tue, 22 Sep 2009 05:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4023</guid>
		<description>I think the info about flow is good, but Walter is looking like a bit of a “straw man.” There is much he doesn’t “get” about Agile which may be understandable. But there is also much he doesn’t seem to “get” about even reasonable non-Agile development.</description>
		<content:encoded><![CDATA[<p>I think the info about flow is good, but Walter is looking like a bit of a “straw man.” There is much he doesn’t “get” about Agile which may be understandable. But there is also much he doesn’t seem to “get” about even reasonable non-Agile development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4022</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 21 Sep 2009 22:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4022</guid>
		<description>Thanks Scott,

Yeh, it is tricky figuring personas when trying to be &quot;funny&quot; and also give useful information. So, thanks for taking the time to express your view on the goodness of the &quot;flow&quot; stuff, and the potential hazard of going too far with the Walter and Sarah exchanges. It was their first trip out of the gate. I am hopeful they will get more settled!  Thanks, Jean</description>
		<content:encoded><![CDATA[<p>Thanks Scott,</p>
<p>Yeh, it is tricky figuring personas when trying to be &#8220;funny&#8221; and also give useful information. So, thanks for taking the time to express your view on the goodness of the &#8220;flow&#8221; stuff, and the potential hazard of going too far with the Walter and Sarah exchanges. It was their first trip out of the gate. I am hopeful they will get more settled!  Thanks, Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Duncan</title>
		<link>http://www.rallydev.com/agileblog/2009/09/whats-so-great-about-flow/#comment-4020</link>
		<dc:creator>Scott Duncan</dc:creator>
		<pubDate>Mon, 21 Sep 2009 17:06:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3229#comment-4020</guid>
		<description>I think the info about flow is good, but Walter is looking like a bit of a &quot;straw man.&quot;  There is much he doesn&#039;t &quot;get&quot; about Agile which may be understandable.  But there is also much he doesn&#039;t seem to &quot;get&quot; about even reasonable non-Agile development.

On the other hand, Sarah is coming across as a tad supercilious.  I&#039;d like the exchanges to seem a bit more realistic.  I think most Walters would be a bit more &quot;careful in how they phrase what they do.  And Sarah, as a consultant coming from the outside, should likely not immediately tell the person she has to work most with that they misunderstand and need &quot;a long talk.&quot;</description>
		<content:encoded><![CDATA[<p>I think the info about flow is good, but Walter is looking like a bit of a &#8220;straw man.&#8221;  There is much he doesn&#8217;t &#8220;get&#8221; about Agile which may be understandable.  But there is also much he doesn&#8217;t seem to &#8220;get&#8221; about even reasonable non-Agile development.</p>
<p>On the other hand, Sarah is coming across as a tad supercilious.  I&#8217;d like the exchanges to seem a bit more realistic.  I think most Walters would be a bit more &#8220;careful in how they phrase what they do.  And Sarah, as a consultant coming from the outside, should likely not immediately tell the person she has to work most with that they misunderstand and need &#8220;a long talk.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
