Talk:Cycle time (software)

Correct primary definition and show multiple uses?

This article says that cycle time "is considering only the active, operating processing time and discarding any idle, waiting, or service times occurring mid-process".

I've read multiple definitions of cycle time, but never seen one that excludes non-touch time. It seems this definition would be equivalent to the idea of 'touch time' in Lean.

From my understanding the most common usage of cycle time is to measure from when work begins to when it's completed. This would generally be across the full value stream, but could be one step in the value stream.

I've also seen it conflated with lead time which would begin counting from when the work was requested (include the backlog time prior to beginning).

It is also commonly defined as TAKT time i.e. (hours of operation / throughput) = average time to complete a unit.

Would it be worth adding discussion to the page to these variations? I see there are links to it in the references, but the ideas are not represented on the body content. SpiritedTui (talk) 05:21, 23 June 2023 (UTC)

See the definition of https://en.wikipedia.org/wiki/Takt_time, that argues that takt time is not equal to cycle time.

I agree that there should be definitions for takt time, cycle time and lead time. It doesn't help that this article talks about the software context only, while the Cycle time is valid for any domain. 212.78.185.65 (talk) 14:03, 27 November 2023 (UTC)