Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cycle time instead of lead time #37

Open
jalabarzo opened this issue May 9, 2023 · 1 comment
Open

Cycle time instead of lead time #37

jalabarzo opened this issue May 9, 2023 · 1 comment

Comments

@jalabarzo
Copy link

Lead time refers to the number of hours or days between placing an order and delivery

Cycle time refers to the number of hours or days it takes to manufacture a unit.

In this simulator, all items (requests) are already created, so we're measuring cycle time, not lead time.

@mjw
Copy link

mjw commented Aug 9, 2023

In manufacturing maybe. You could argue you could use either for this explanation, which is looking specifically at team flow (in a software team in the video). Lead time is whatever you want it to mean in your circumstances, its a measurement of time between the start and end of a process, the start might be when a customer asks for something, the end might be when they receive it. But that process might be part of a bigger process, so then that measurement is a cycle time within that wider one and so on.

A better reason for using cycle time here is that littles law as its being used here (for knowledge work) is stated in terms of cycle time not lead (wait) time so would lead to less confusion if people are reading about littles law in this context.

Average cycle time = Average WIP / Average throughput

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants