<?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 Dayley Agile</title>
	<atom:link href="http://www.dayleyagile.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dayleyagile.com</link>
	<description>Better teams make better business with quality Agile coaching from Dayley Agile.</description>
	<lastBuildDate>Sat, 14 Jan 2012 16:47:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Velocity Moves Forward by sharada</title>
		<link>http://www.dayleyagile.com/2012/01/velocity-moves-forward/#comment-108</link>
		<dc:creator>sharada</dc:creator>
		<pubDate>Sat, 14 Jan 2012 16:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dayleyagile.com/?p=560#comment-108</guid>
		<description>well stated..on the use of velocity in use of projects</description>
		<content:encoded><![CDATA[<p>well stated..on the use of velocity in use of projects</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Velocity Moves Forward by Glenn Smith</title>
		<link>http://www.dayleyagile.com/2012/01/velocity-moves-forward/#comment-107</link>
		<dc:creator>Glenn Smith</dc:creator>
		<pubDate>Fri, 13 Jan 2012 15:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.dayleyagile.com/?p=560#comment-107</guid>
		<description>Really great analogy with driving. I like that.</description>
		<content:encoded><![CDATA[<p>Really great analogy with driving. I like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Velocity Moves Forward by Miguel Rodriguez</title>
		<link>http://www.dayleyagile.com/2012/01/velocity-moves-forward/#comment-106</link>
		<dc:creator>Miguel Rodriguez</dc:creator>
		<pubDate>Fri, 13 Jan 2012 09:55:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.dayleyagile.com/?p=560#comment-106</guid>
		<description>Excellent analogy.  Will use it specially now that yearly goals are up.  Need a way to have top management understand that it is the quality and amount of features what counts.  Often times people see statistics and focus on the numbers instead of the meaning.</description>
		<content:encoded><![CDATA[<p>Excellent analogy.  Will use it specially now that yearly goals are up.  Need a way to have top management understand that it is the quality and amount of features what counts.  Often times people see statistics and focus on the numbers instead of the meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8220;BDUF Scrum&#8221; &#8211; Don&#8217;t do it! by Nicolas Mereaux</title>
		<link>http://www.dayleyagile.com/2010/07/bduf-scrum-dont-do-it/#comment-74</link>
		<dc:creator>Nicolas Mereaux</dc:creator>
		<pubDate>Thu, 24 Nov 2011 20:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=266#comment-74</guid>
		<description>Hi everyone,

A french translation of this post is available here : http://tinyurl.com/cddngpq</description>
		<content:encoded><![CDATA[<p>Hi everyone,</p>
<p>A french translation of this post is available here : <a href="http://tinyurl.com/cddngpq" rel="nofollow">http://tinyurl.com/cddngpq</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Limiting WIP: People, Organizations and Scrum by dayleyagile</title>
		<link>http://www.dayleyagile.com/2011/09/limiting-wip-people-organizations-and-scrum/#comment-53</link>
		<dc:creator>dayleyagile</dc:creator>
		<pubDate>Fri, 23 Sep 2011 14:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=435#comment-53</guid>
		<description>Thank you!  I will contact you by email to get this done.</description>
		<content:encoded><![CDATA[<p>Thank you!  I will contact you by email to get this done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Limiting WIP: People, Organizations and Scrum by PM Hut</title>
		<link>http://www.dayleyagile.com/2011/09/limiting-wip-people-organizations-and-scrum/#comment-52</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Fri, 23 Sep 2011 06:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=435#comment-52</guid>
		<description>Hi Alan,

I would like to republish your post (which examines a very unique topic on Scrum) under the Scrum Category on PM Hut ( http://www.pmhut.com ). Please either email me or contact me through the &quot;Contact Us&quot; form on the PM Hut website in case you&#039;re OK with this.

I think your post will be very beneficial to PM Hut readers...</description>
		<content:encoded><![CDATA[<p>Hi Alan,</p>
<p>I would like to republish your post (which examines a very unique topic on Scrum) under the Scrum Category on PM Hut ( <a href="http://www.pmhut.com" rel="nofollow">http://www.pmhut.com</a> ). Please either email me or contact me through the &#8220;Contact Us&#8221; form on the PM Hut website in case you&#8217;re OK with this.</p>
<p>I think your post will be very beneficial to PM Hut readers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Limiting WIP: People, Organizations and Scrum by Darron Roberts</title>
		<link>http://www.dayleyagile.com/2011/09/limiting-wip-people-organizations-and-scrum/#comment-51</link>
		<dc:creator>Darron Roberts</dc:creator>
		<pubDate>Wed, 21 Sep 2011 19:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=435#comment-51</guid>
		<description>That is a new way of viewing WIP for me, which is normally stock on a floor, people in a queue or papers in a try.</description>
		<content:encoded><![CDATA[<p>That is a new way of viewing WIP for me, which is normally stock on a floor, people in a queue or papers in a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agility Requires Clear Communication by Alex Forbes</title>
		<link>http://www.dayleyagile.com/2011/02/agility-requires-clear-communication/#comment-50</link>
		<dc:creator>Alex Forbes</dc:creator>
		<pubDate>Fri, 04 Mar 2011 14:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=383#comment-50</guid>
		<description>Much clearer. Thank you.

You may appreciate this article about white boards:

http://www.softwarequalityconnection.com/2011/01/informative-workspaces-using-white-boards-to-increase-productivity-and-build-trust/

I forget who said it, but it went something like, &quot;a picture of your Agile whiteboard is not an audit trail. Enterprise Agile needs an enterprise tool.&quot;

Best,
Alex</description>
		<content:encoded><![CDATA[<p>Much clearer. Thank you.</p>
<p>You may appreciate this article about white boards:</p>
<p><a href="http://www.softwarequalityconnection.com/2011/01/informative-workspaces-using-white-boards-to-increase-productivity-and-build-trust/" rel="nofollow">http://www.softwarequalityconnection.com/2011/01/informative-workspaces-using-white-boards-to-increase-productivity-and-build-trust/</a></p>
<p>I forget who said it, but it went something like, &#8220;a picture of your Agile whiteboard is not an audit trail. Enterprise Agile needs an enterprise tool.&#8221;</p>
<p>Best,<br />
Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agility Requires Clear Communication by dayleyagile</title>
		<link>http://www.dayleyagile.com/2011/02/agility-requires-clear-communication/#comment-49</link>
		<dc:creator>dayleyagile</dc:creator>
		<pubDate>Fri, 04 Mar 2011 02:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=383#comment-49</guid>
		<description>Alex.

I agree that the right use of excellent processes tools can enhance communication.  I would say your statement still puts the emphasis on the processes and tools, which I do not agree with.  Let me explain.

Nearly every team I have worked with that only used sticky notes, index cards, markers and tape to enhance their communication learned faster, gelled sooner and improved more rapidly than  teams using any computerized tool. This is because basic tools such as these play on the strengths of human communication DNA and history.  The tangible touch, visual information and natural use accelerates a team.  Fancy tools and processes designed to eliminate mistakes require humans to communicate in abstract and remove flexibility.

&quot;Over&quot; does not mean &quot;instead of.&quot;  As the Agile manifesto states, processes and tools have value.  They just should not be the first avenue of response when attempting to solve performance problems.  If it helps, reword it as &quot;Individuals and interactions before processes and tools.&quot;  That means look to individuals and interactions to solve problems and create solutions before looking at process and tooling.

I&#039;m certainly not against processes and tools.  Scrum itself is a process framework and a tool to build great stuff.  Just choose wisely and look at the possible negative side effects of a new process or tool instead of blindly expecting only benefits.</description>
		<content:encoded><![CDATA[<p>Alex.</p>
<p>I agree that the right use of excellent processes tools can enhance communication.  I would say your statement still puts the emphasis on the processes and tools, which I do not agree with.  Let me explain.</p>
<p>Nearly every team I have worked with that only used sticky notes, index cards, markers and tape to enhance their communication learned faster, gelled sooner and improved more rapidly than  teams using any computerized tool. This is because basic tools such as these play on the strengths of human communication DNA and history.  The tangible touch, visual information and natural use accelerates a team.  Fancy tools and processes designed to eliminate mistakes require humans to communicate in abstract and remove flexibility.</p>
<p>&#8220;Over&#8221; does not mean &#8220;instead of.&#8221;  As the Agile manifesto states, processes and tools have value.  They just should not be the first avenue of response when attempting to solve performance problems.  If it helps, reword it as &#8220;Individuals and interactions before processes and tools.&#8221;  That means look to individuals and interactions to solve problems and create solutions before looking at process and tooling.</p>
<p>I&#8217;m certainly not against processes and tools.  Scrum itself is a process framework and a tool to build great stuff.  Just choose wisely and look at the possible negative side effects of a new process or tool instead of blindly expecting only benefits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agility Requires Clear Communication by Alex Forbes</title>
		<link>http://www.dayleyagile.com/2011/02/agility-requires-clear-communication/#comment-48</link>
		<dc:creator>Alex Forbes</dc:creator>
		<pubDate>Thu, 03 Mar 2011 22:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dayleyagile.com/?p=383#comment-48</guid>
		<description>Agree with 99.99 % of this, and it may only be splitting hairs over the final .01. But the statement: 

”Individuals and interactions over processes and tools” is not just some feel-good mantra.  It is what we need to solve our problems and innovate!&quot;

To me should read: &quot;Individuals and interactions can be enhanced with the right processes and tools.&quot; There is some good tool innovation in the market that many teams appreciate to help communicate and collaborate, even improve resource allocation, especially when they don&#039;t share the same office walls. &quot;over&quot; is just too strong a statement for me. 

Otherwise, great read.

Alex</description>
		<content:encoded><![CDATA[<p>Agree with 99.99 % of this, and it may only be splitting hairs over the final .01. But the statement: </p>
<p>”Individuals and interactions over processes and tools” is not just some feel-good mantra.  It is what we need to solve our problems and innovate!&#8221;</p>
<p>To me should read: &#8220;Individuals and interactions can be enhanced with the right processes and tools.&#8221; There is some good tool innovation in the market that many teams appreciate to help communicate and collaborate, even improve resource allocation, especially when they don&#8217;t share the same office walls. &#8220;over&#8221; is just too strong a statement for me. </p>
<p>Otherwise, great read.</p>
<p>Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>

