RE: SIP is not Takt Time

I can see two things going on here. One is the definitions of the
various measures in manufacturing. The other are the appropriate
measures for use in software development.

>I finally got around to reading the SIP paper you posted here in
>December. I'm afraid I cannot agree with your definition of SIP.

>You define it as the time taken for working code to emerge from the
>value stream. This is known in manufacturing as Takt Time or in
>plainer English, Lead Time or Cycle Time.

" from http://www.vmec.org/lean_corner/takttime.html 

Takt time is the goal. It must be reached to satisfy demand. 

Cycle time is a measured value, not a calculated value as takt time is.
In other words, you must go out to the floor, and measure the time it
actually does take to manufacture the product."

>In many other respects I agree with your sentiments about SIP. It is a
>vital metric for Agile processes. However, in Lean, Inventory takes
>second place to Value. With XP you always pushed working code as the
>indicator of delivered value. I think you should stick with that as
>the most important metric for Agile. Value is #1. Inventory is #2.
>Takt Time (your current SIP) is #3 (though it is related to both Value
>and Inventory). Last would be Operating Expense i.e. the cost of
>operating the value stream - the development organization.

I agree Value is #1, but I don't know how to measure it directly. SIP is
production lead time, not Takt time (takt in XP is always one week, we
just vary the size of the unit of production.)

Kent



To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/