<?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: Task Lists</title>
	<atom:link href="http://blog.agilezen.com/2010/02/01/task-lists/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.agilezen.com/2010/02/01/task-lists/</link>
	<description>Meditations on Zen and our love for everything Lean</description>
	<lastBuildDate>Wed, 01 Sep 2010 21:45:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: eugeneware</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-1055</link>
		<dc:creator>eugeneware</dc:creator>
		<pubDate>Fri, 19 Mar 2010 09:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-1055</guid>
		<description>Great job. I just signed up for the $99/month plan :-)&lt;br&gt;&lt;br&gt;However, I just noticed that if two people are viewing the kanban board at the same time and one makes a change... it DOESN&#039;T CHANGE on the other person screens. &lt;br&gt;&lt;br&gt;I&#039;m sure it&#039;s high on the todo list, but as a team collaboration tool, it&#039;s pretty important that this gets dealt with soon wouldn&#039;t you agree?&lt;br&gt;&lt;br&gt;This is something that Pivotal Tracker does really well using a &quot;long poll&quot; ajax script.&lt;br&gt;&lt;br&gt;Beautiful product, really nice.</description>
		<content:encoded><![CDATA[<p>Great job. I just signed up for the $99/month plan :-)</p>
<p>However, I just noticed that if two people are viewing the kanban board at the same time and one makes a change&#8230; it DOESN&#39;T CHANGE on the other person screens. </p>
<p>I&#39;m sure it&#39;s high on the todo list, but as a team collaboration tool, it&#39;s pretty important that this gets dealt with soon wouldn&#39;t you agree?</p>
<p>This is something that Pivotal Tracker does really well using a &#8220;long poll&#8221; ajax script.</p>
<p>Beautiful product, really nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DeanG</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-1017</link>
		<dc:creator>DeanG</dc:creator>
		<pubDate>Wed, 10 Mar 2010 00:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-1017</guid>
		<description>&gt;&gt; [Task Percentage] can be helpful to check the completion status of a story at a quick glance&lt;br&gt;&lt;br&gt;Here&#039;s a vote to suggest it&#039;s more of a distraction. The # of # count qualifies this, and the % brings to mind 80/20 cliches and the failures of status by percentage.&lt;br&gt;&lt;br&gt;Please consider Sparklines if you think the counts need a supplemental view.</description>
		<content:encoded><![CDATA[<p>&gt;&gt; [Task Percentage] can be helpful to check the completion status of a story at a quick glance</p>
<p>Here&#39;s a vote to suggest it&#39;s more of a distraction. The # of # count qualifies this, and the % brings to mind 80/20 cliches and the failures of status by percentage.</p>
<p>Please consider Sparklines if you think the counts need a supplemental view.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Campbell</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-836</link>
		<dc:creator>Steve Campbell</dc:creator>
		<pubDate>Wed, 10 Feb 2010 21:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-836</guid>
		<description>I&#039;m not Nate, but I can say that on our team we have discussed this quite a bit and gone back and forth on deciding how to represent defects on the board.  This is what works for us today:&lt;br&gt;&lt;br&gt;Defects are entered into our bug tracking software.  They are triaged, and if we decide to do a fix then we create a new story on the board, in orange.  This new story is then worked like any other.  We still track the issue in the bug tracking software.  This is duplicate work, but we decided that we needed the visibility of the board, but also wanted the audit trail of comments in the bug tracker software.&lt;br&gt;&lt;br&gt;Other defects discovered during testing (prior to production) are not tracked as stories on the board, although they may cause a story to be blocked.</description>
		<content:encoded><![CDATA[<p>I&#39;m not Nate, but I can say that on our team we have discussed this quite a bit and gone back and forth on deciding how to represent defects on the board.  This is what works for us today:</p>
<p>Defects are entered into our bug tracking software.  They are triaged, and if we decide to do a fix then we create a new story on the board, in orange.  This new story is then worked like any other.  We still track the issue in the bug tracking software.  This is duplicate work, but we decided that we needed the visibility of the board, but also wanted the audit trail of comments in the bug tracker software.</p>
<p>Other defects discovered during testing (prior to production) are not tracked as stories on the board, although they may cause a story to be blocked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Afif Raza</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-779</link>
		<dc:creator>Afif Raza</dc:creator>
		<pubDate>Fri, 05 Feb 2010 10:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-779</guid>
		<description>Hi Nate,&lt;br&gt;First off, great work., my question may not perhaps relate to what your tool is intended to be., but I am curious. How does your software tie into the dynamics of the delivery of software once it has been pushed to production? As in one may find anomalies against some stories., which results in assigning defects next to them? Do you recommend on using a separate bug tracking software? &lt;br&gt;&lt;br&gt;Afif</description>
		<content:encoded><![CDATA[<p>Hi Nate,<br />First off, great work., my question may not perhaps relate to what your tool is intended to be., but I am curious. How does your software tie into the dynamics of the delivery of software once it has been pushed to production? As in one may find anomalies against some stories., which results in assigning defects next to them? Do you recommend on using a separate bug tracking software? </p>
<p>Afif</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Goerlich</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-728</link>
		<dc:creator>Dave Goerlich</dc:creator>
		<pubDate>Mon, 01 Feb 2010 21:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-728</guid>
		<description>This is excellent!  We will use the task lists quite a bit I&#039;m sure.  Matter of fact, I&#039;m going to go back through our active cards right now and put them to use!&lt;br&gt;&lt;br&gt;Oh, and thanks for fixing the keyboard shortcuts.  I&#039;ll admit to having been annoyed by them more than a couple times.</description>
		<content:encoded><![CDATA[<p>This is excellent!  We will use the task lists quite a bit I&#39;m sure.  Matter of fact, I&#39;m going to go back through our active cards right now and put them to use!</p>
<p>Oh, and thanks for fixing the keyboard shortcuts.  I&#39;ll admit to having been annoyed by them more than a couple times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hellogerard</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-727</link>
		<dc:creator>hellogerard</dc:creator>
		<pubDate>Mon, 01 Feb 2010 21:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-727</guid>
		<description>My two favorite changes of this release:&lt;br&gt;&lt;br&gt;1) Task Lists&lt;br&gt;2) Removal of hot keys - I get my Ctrl-Shift-Arrow back!</description>
		<content:encoded><![CDATA[<p>My two favorite changes of this release:</p>
<p>1) Task Lists<br />2) Removal of hot keys &#8211; I get my Ctrl-Shift-Arrow back!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Douglass</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-726</link>
		<dc:creator>Danny Douglass</dc:creator>
		<pubDate>Mon, 01 Feb 2010 20:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-726</guid>
		<description>Love the tasks feature - thanks!</description>
		<content:encoded><![CDATA[<p>Love the tasks feature &#8211; thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Newland</title>
		<link>http://blog.agilezen.com/2010/02/01/task-lists/comment-page-1/#comment-725</link>
		<dc:creator>Jesse Newland</dc:creator>
		<pubDate>Mon, 01 Feb 2010 20:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilezen.com/?p=55#comment-725</guid>
		<description>No API features?  Sad panda :(&lt;br&gt;&lt;br&gt;No pressure, just wanted to give you a hard time. The task lists looks awesome :)</description>
		<content:encoded><![CDATA[<p>No API features?  Sad panda :(</p>
<p>No pressure, just wanted to give you a hard time. The task lists looks awesome :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
