tag:blogger.com,1999:blog-6178209.post3557994876125577488..comments2009-10-07T15:01:28.823-05:00Igorhttp://www.blogger.com/profile/12832903167357753682noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6178209.post-13248177965639839372009-10-07T15:01:28.823-05:002009-10-07T15:01:28.823-05:00Good post btw :)<br /><br />Always looking to pick up more info and viewpoints.Bealerhttp://www.blogger.com/profile/13552045032292142168noreply@blogger.comtag:blogger.com,1999:blog-6178209.post-56378021912694595082009-10-07T14:59:21.092-05:002009-10-07T14:59:21.092-05:00&quot;1. You should try and explain what happens when the queue limits are reached say for testing. Do we stop development.. or say ask developers to test.. what are the options ? Do we stop the line ?&quot;<br /><br />Stop-the-line is quite a common procedure. And in a truly Agile team developers should offer to help testers, or do cross-skill pair programming. Maybe help automate the testing (although in an ideal world you would have done your tests upfront). It&#39;s something you should try not see may happen, and act before it does.<br /><br />&quot;2. Estimation still cannot be eliminated IMHO since you need to have a release plan.. and also at an Iteration level in Agile you learn more about a story to estimate again. In manufacturing you never iterate or learn more about a piece you need to build&quot;<br /><br />Yeah this is slightly more contraversial. I&#39;m not sure how it relates to a release plan though. If you mean predicting when work will be done, the idea with not estimating is to break down features/stories into small, similar sized chunks of work. That way over time you develop a cycle-time and can base predictions on it.<br /><br />I&#39;m not sure what you mean about learning a story. If doing Feature Driven Development you shouldn&#39;t really run into such an issue.Bealerhttp://www.blogger.com/profile/13552045032292142168noreply@blogger.comtag:blogger.com,1999:blog-6178209.post-87386834136908193982009-07-16T11:56:57.643-05:002009-07-16T11:56:57.643-05:00Hi Anand,<br /><br />Thanks for the really good questions. <br /><br />&gt;&gt;&gt;&gt;<br /><i>1. You should try and explain what happens when the queue limits are reached say for testing. Do we stop development.. or say ask developers to test.. what are the options ? Do we stop the line ?</i><br />&lt;&lt;&lt;&lt;<br /><br />I look at Kanban just a signal/trigger for an action. What would be the action would depend on a particular team and project context.<br /><br />&quot;Stopping the line&quot; is part of a bigger set of Lean principles that could be introduced consequentially or the blog entry would become too long :-)<br /><br />&gt;&gt;&gt;&gt;<br /><i>2. Estimation still cannot be eliminated IMHO since you need to have a release plan.. and also at an Iteration level in Agile you learn more about a story to estimate again. In manufacturing you never iterate or learn more about a piece you need to build</i><br />&lt;&lt;&lt;&lt;<br /><br />Yes, this is the controversial part that I mentioned at the end of the blog post. You definitely have a point but it is an important and big enough topic that I left it for my next post entry. <br /><br /><br />Thanks again and I really appreciate your questions.Igorhttp://www.blogger.com/profile/12832903167357753682noreply@blogger.comtag:blogger.com,1999:blog-6178209.post-31473039229204004852009-07-15T22:47:25.811-05:002009-07-15T22:47:25.811-05:002 things Igor,<br /><br />1. You should try and explain what happens when the queue limits are reached say for testing. Do we stop development.. or say ask developers to test.. what are the options ? Do we stop the line ?<br /><br />2. Estimation still cannot be eliminated IMHO since you need to have a release plan.. and also at an Iteration level in Agile you learn more about a story to estimate again. In manufacturing you never iterate or learn more about a piece you need to buildAnand Vishwanathhttp://www.blogger.com/profile/04391284554540881059noreply@blogger.com