http://leansoftwareengineering.com/2009/04/09/three-ways-to-go-about-queue-sizing/ Essays on the Continuous Delivery of High Quality Information Systems Wed, 01 Feb 2012 18:32:04 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://leansoftwareengineering.com/2009/04/09/three-ways-to-go-about-queue-sizing/comment-page-1/#comment-5269 Corey Ladas Thu, 07 May 2009 01:55:04 +0000 http://leansoftwareengineering.com/?p=1314#comment-5269 Sure, you could do that. It's more or less equivalent to starting everything at a high number. It might also be easiest to convince people to do (confirmation bias: see, my role is important) and hardest to convince them to accept the result (what do you mean my role is superfluous? you must be wrong.). The arbitrary high number neutralizes the perception of vested interest. Negative selection is more painful than positive selection--loss aversion is human nature. Sure, you could do that. It’s more or less equivalent to starting everything at a high number. It might also be easiest to convince people to do (confirmation bias: see, my role is important) and hardest to convince them to accept the result (what do you mean my role is superfluous? you must be wrong.). The arbitrary high number neutralizes the perception of vested interest. Negative selection is more painful than positive selection–loss aversion is human nature.

]]> http://leansoftwareengineering.com/2009/04/09/three-ways-to-go-about-queue-sizing/comment-page-1/#comment-5260 ObiJohn Wed, 06 May 2009 02:09:55 +0000 http://leansoftwareengineering.com/?p=1314#comment-5260 Okay, I'll bite... if the goal is to ensure maximum flow, then why not start with a WIP limit of one per every resource available at a process step/activity, and then adjust the limits based upon constraints as per ToC? Isn't this a faster way to find the bottleneck and use it to pace the workflow? Okay, I’ll bite… if the goal is to ensure maximum flow, then why not start with a WIP limit of one per every resource available at a process step/activity, and then adjust the limits based upon constraints as per ToC? Isn’t this a faster way to find the bottleneck and use it to pace the workflow?

]]>