<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Joe Arnold - Latest Comments in General</title><link>http://joearnold.disqus.com/</link><description></description><language>en</language><lastBuildDate>Thu, 19 Jun 2008 15:35:07 -0000</lastBuildDate><item><title>Re: Kanban: &amp;#8220;Just set it and forget it!&amp;#8221;</title><link>http://joearnold.com/2008/05/kanban-just-set-it-and-forget-it/#comment-707329</link><description>How they handle releases is to create buckets that live in the 'done' column. Sometimes when something hits the done column it needs to be deployed immediately (like an emergency bug fix). Sometimes the team is working on two different products at the same time. The team uses different colored post-it notes for each product. Each product has its own bucket where features/bug fixes congregate -- waiting for the next release for that product. As for the 'activities related to a release' task. I don't think they create another 'thing to do' that works its way through the kanban system. When it's time, I think the team just re-evaluates everything in that bucket before launch.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">joearnold</dc:creator><pubDate>Thu, 19 Jun 2008 15:35:07 -0000</pubDate></item><item><title>Re: Kanban: &amp;#8220;Just set it and forget it!&amp;#8221;</title><link>http://joearnold.com/2008/05/kanban-just-set-it-and-forget-it/#comment-702403</link><description>Very nice - simple and transparent. One question - how are they handling releases - just another item in the 'things to do' queue?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Newman</dc:creator><pubDate>Wed, 18 Jun 2008 21:08:54 -0000</pubDate></item><item><title>Re: Leaving Yahoo!</title><link>http://joearnold.com/2008/06/leaving-yahoo/#comment-635440</link><description>Hi Joe,&lt;br&gt;&lt;br&gt;Sad to see you move back to Valley. Wishing you the very best in your new endeavour. Looking forward to see you back for HackDay / BigThinkers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Puneeth</dc:creator><pubDate>Wed, 11 Jun 2008 06:54:40 -0000</pubDate></item><item><title>Re: Leaving Yahoo!</title><link>http://joearnold.com/2008/06/leaving-yahoo/#comment-631816</link><description>Indeed! Let's do many lunches when I get back! See you soon.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">joearnold</dc:creator><pubDate>Tue, 10 Jun 2008 19:21:04 -0000</pubDate></item><item><title>Re: Leaving Yahoo!</title><link>http://joearnold.com/2008/06/leaving-yahoo/#comment-631098</link><description>I'm sure Bangalore will miss you.&lt;br&gt;&lt;br&gt;Isn't Engine Yard in South Park? Welcome home! :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Premshree Pillai</dc:creator><pubDate>Tue, 10 Jun 2008 17:57:02 -0000</pubDate></item><item><title>Re: Leaving Yahoo!</title><link>http://joearnold.com/2008/06/leaving-yahoo/#comment-623066</link><description>We will miss you! :(&lt;br&gt;&lt;br&gt;1. whoosh (you running towards our cubes) and your "Standup Time" calls  (11:00 dot )&lt;br&gt;2. Awesome discussions about CI.&lt;br&gt;3. Learnt a lot about process, and how a software is developed from you&lt;br&gt;4. Loved the Idea of Kanban and had fun developing it! (We should opensource it ;) )&lt;br&gt;5. Learnt how to finish standup meeting fast! &lt;br&gt;&lt;br&gt;We all will miss you, joe! Good luck @ Engine Yard</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alagu</dc:creator><pubDate>Mon, 09 Jun 2008 17:34:04 -0000</pubDate></item><item><title>Re: Leaving Yahoo!</title><link>http://joearnold.com/2008/06/leaving-yahoo/#comment-622326</link><description>Best of luck with the 'Ruby' thing. keep tweeting</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Praveen</dc:creator><pubDate>Mon, 09 Jun 2008 15:52:04 -0000</pubDate></item><item><title>Re: Kanban: &amp;#8220;Just set it and forget it!&amp;#8221;</title><link>http://joearnold.com/2008/05/kanban-just-set-it-and-forget-it/#comment-596982</link><description>That's one option. Usually what this team does is leave it in 'test'. The developer works with the tester to fix it. This is the 'stop-the-line' mentality of bug fixing. If a bigger issue comes up, then another ticket is created and is prioritized by the product manager. There are a couple of other possibilities too. Check out my post on 'What to do with bugs when using Kanban' &lt;br&gt;&lt;a href="http://joearnold.com/2007/12/what-to-do-with-bugs-when-using-a-kanban-system/"&gt;http://joearnold.com/2007/12/what-to-do-with-bu...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">joearnold</dc:creator><pubDate>Thu, 05 Jun 2008 06:10:04 -0000</pubDate></item><item><title>Re: Kanban: &amp;#8220;Just set it and forget it!&amp;#8221;</title><link>http://joearnold.com/2008/05/kanban-just-set-it-and-forget-it/#comment-596469</link><description>When a tester discovers a bug  in a "dev done" item what happens? does it move back into the "under development" column?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 05 Jun 2008 03:54:05 -0000</pubDate></item><item><title>Re: http://joearnold.com/2008/05/velocity-is-not-a-transitive-property/</title><link>http://joearnold.com/2008/05/velocity-is-not-a-transitive-property/#comment-476106</link><description>...more productive and effective. This system/capacity view is the perspective is what allows managers in Agile organizations to become very effective at making organizational improvements.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rdymond</dc:creator><pubDate>Fri, 16 May 2008 08:10:04 -0000</pubDate></item><item><title>Re: http://joearnold.com/2008/05/velocity-is-not-a-transitive-property/</title><link>http://joearnold.com/2008/05/velocity-is-not-a-transitive-property/#comment-476080</link><description>Great points Joe. In large organizations we see on average 30% of actual hours in a week is what you can exoect in "ideal hours." So for a 3 week 120h iteration, we expect 40 ideal hours. People are very surprised when we initially explain this. They want to use 120h. The reality is large organizations have many activities that are required but take away time. Meetings, delays in getting support, work orders, waiting for responses, rebuild of dev environments when they get corrupted, etc. Interestingly when we look at smaller companies we see ideal hours increase to 50%. Why not 80%? We aren't sure, but the points you raise here give some hints. The point isn't to make ideal hours equal actual hours. The real goal is to understand the pace of development, and then continually look for waste that slows teams down and prevents them from being</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robin Dymond</dc:creator><pubDate>Fri, 16 May 2008 07:54:59 -0000</pubDate></item></channel></rss>