#work-in-process

Queues in high-state are the same as congested queues, queues at high capacity utilization, with high WIP, or at high level of utilization

To make supply-focused approaches effective, you must minimize the time between the onset of congestion and the application of added resources.

It will free up resources to work on other tasks, but it will also increase the product's variance, increasing the costs associated with fixing those defects.

One of the biggest advantages of the demand-focused approaches is the speed at which you can execute them.

If you preplan which requirements your team can scrap, you can structure your product architecture to make it easy to discard them.

When WIP becomes high, you can purge WIP by decreasing the batch size of your jobs. A way to achieve this is to shed the requirements of your jobs.

Whenever WIP is high, queues are high. When queues are high, jobs in the process generate high delay costs. Most of the damage is caused by high-state queues.

Zombie projects are projects that aren't good enough to get resources and bad enough to kill. Many companies starve them for resources because of the sunk cost.

You can block queues in two ways: 1. Eject the arriving job from the system. 2. Hold back the job in an upstream queue.

If you fix the level of a WIP pool, you'd inherently synchronize the arrival and departure rates of this pool.

In this situation, if your team can execute the tasks of the bottleneck process, they can help it by increasing its capacity for a short period.

Because of the pull principle, the upstream processes can't send work to the next stage if a blockage occurs anywhere.

When you set a limit on WIP, you create positive and negative effects.

A high number of working in the process leads to a high queue capacity utilization, which causes problems such as a higher cycle time.