Use WIP to explain lead time
Use WIP and throughput to reason about lead time in a value stream.
The platform team has 86 active change requests and completes 20 per week. Stakeholders ask why small changes take weeks. Approximate flow time = WIP / throughput when the system is stable enough to reason from averages Accepting every request into active work feels responsive but increases the line each item must wait in. Count started work WIP = 86 active requests between start and done. Only count items that have crossed the start boundary. Backlog ideas are demand, not WIP. Measure finish rate Throughput = 20 requests completed per week. Use done items, not effort hours. Flow improves when…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in