Comments for Koo Doy

Comment on Queues understanding to improve productivity by Omar Kamal Hosney

Omar Kamal Hosney — Fri, 03 Feb 2012 06:23:29 +0000

Sameh, computing the average and maximum queue size could be easily computed using the global arrival rate (for incoming issues), it will always always have a poision distrubution with that global arrival rate (lamda).
The challange will alwasy be to identify the distribution of service or the execution of those issues, it could be exponitional, normal, lognormal, any kind of distrubution.
So, a good approach we be to log around 30 to 40 days of execution time and then using run a simple monte-carlo simulation using a “bootstrapper” techique that keep re-sampling the execution history sample (those sample of 30 or 40 days) you will get all the queuing performance for your pipeline and that will include:
1- avarage queue size
2-avaerage time for a single issue to stay in the queue
3- avaerage time for a single issue to stay in the overall system
4- average count of issues in the overall system (queue and in-progress)
5- the team utilization factor

Also, what you get maximums and minimums.

Thanks for simulation !

Comment on Lean for IT/Software.. Make knowledge explicit/2 by Lean for IT/Software projects,,, structure communication/3 « Koo Doy

Lean for IT/Software projects,,, structure communication/3 « Koo Doy — Fri, 27 Jan 2012 08:47:34 +0000

[...] my previous post here, I will continue with the 3rd step for Lean implementation in IT/Software setup. Let me explain [...]

Comment on Lean for Knowledge Work by Lean for IT/Software.. Make knowledge explicit/2 « Koo Doy

Lean for IT/Software.. Make knowledge explicit/2 « Koo Doy — Fri, 27 Jan 2012 07:28:38 +0000

[...] based on Harvard Business Review article here, you can read my previous post about visualising waste here. Making knowledge explicit does not mean [...]

Comment on Factors for choosing a project approach by Lean for Knowledge Work « Koo Doy

Lean for Knowledge Work « Koo Doy — Thu, 26 Jan 2012 01:01:56 +0000

[...] methods promote experimentation to discover the unknown but desired product. Please see my post here. Not all software or IT projects require experimentation as noted in the post. Harvard Business [...]

Comment on Managing Large Lean Software Projects by Sameh

Sameh — Sun, 22 Jan 2012 04:12:36 +0000

Thanks Henrik and look forward for your next master piece.

Comment on Managing Large Lean Software Projects by Henrik Kniberg

Henrik Kniberg — Sun, 22 Jan 2012 04:07:59 +0000

Good summary of the book

Comment on Transition of a business analyst to product-owner by hundertwasser

hundertwasser — Tue, 06 Dec 2011 00:38:26 +0000

hi, that’s a squeamish stake. There is few mistakes but the primary is here.

Comment on Set-up which Kanban serves us more by PM Hut

PM Hut — Tue, 27 Sep 2011 06:26:18 +0000

Hi Sameh, Are you sharing the details of a project from real life, or is this just an example? By the way, I have published an article lately on the definition of done, which you can see here.

Comment on Product Roadmapping with Prune the Product Tree by Innovation Games® at Work: Roadmapping with Prune the Product Tree

Innovation Games® at Work: Roadmapping with Prune the Product Tree — Wed, 24 Aug 2011 22:07:11 +0000

[...] read more and see an image of the completed tree, click here. Click here to cancel [...]

Comment on Gate Keeper by Requirements uncertainty is desired! « Methods for Software Development

Requirements uncertainty is desired! « Methods for Software Development — Sun, 22 May 2011 17:14:46 +0000

[...] Product owner as Gate Keeper [...]