Comments on: Lean Software Development: How to find bottlenecks – Metrics that Matter

By: Bradford Cross on Lean « Mawson’s Hut

Bradford Cross on Lean « Mawson’s Hut — Thu, 03 Jun 2010 00:12:47 +0000

[...] Finger charts for finding bottlenecks - http://epistemologic.com/2007/10/02/lean-software-development-how-to-find-bottlenecks-metrics-that-m… [...]

By: PatchMetrix: Understanding and improving OSS patch contribution process capability – Bhuricha Deen Sethanandha

Fri, 09 Apr 2010 16:27:06 +0000

[...] Lean Software Development: How to find bottlenecks – Metrics that Matter, [...]

By: Don’t push requirements - pull information | Digital Dim Sum

Don’t push requirements - pull information | Digital Dim Sum — Sat, 20 Sep 2008 00:38:47 +0000

[...] understand how queuing theory can help identify and reduce bottlenecks in processes and have used finger-charts and kanban-boards to do this for a while, but I still find calling this a “pull system” [...]

By: Everybody’s Human » APLN Meet in NYC

Everybody’s Human » APLN Meet in NYC — Tue, 20 Nov 2007 06:28:08 +0000

[...] couldn’t find the speaker’s website, but I found a blog post aboutFinger Charts: http://epistemologic.com/2007/10/02/lean-software-development-how-to-find-bottlenecks-metrics-that-m…Lastly, Lentz was careful to point out that information sharing shouldbe tailored for the audience. [...]

By: Amit Rathore

Amit Rathore — Tue, 30 Oct 2007 04:56:19 +0000

1. A story card by itself, is not a quantifiable unit, in a scientific sense, yes. However, in relation to others, a story card has a fair size – as in, card A is about 2 times card B. If you assume some constant K which represents the particular team and technology and project situation and so on, then on average, K really does stay a constant. Thus, the relative measure becomes sufficient to measure the amount of work. This translates to – 12*K work being done in sprint 1, 14*K in sprint 2 and so on.

2. In my chart, I don’t measure the time a card sits in a particular state, but simply the number of cards in each state, every day. This tells me, over time, where cards are accumalating (simple to see in second graph, which is simply a visual representation of the first table).

By: Oren Golan

Oren Golan — Sat, 20 Oct 2007 18:50:05 +0000

great post Amit,
two questions:
1. a story card in software is not a quantifiable unit. each developer and each team will create different ‘size’ of a story card.
how can we improve the process if we are not measuring accurately?
2. can you elaborate about the way you get the numbers in your first chart? how do u measure the time each story sits in a queue on every given moment?
I would like to use a white board with sticky notes, but i am not sure how to measure it.
maybe I should take a ‘snapshot’ of the current cards once in every day?

thanks