WIP

Work in process
Work in progress

WIP in knowledge work isn't visual and this is the driving force behind wanting to visualize work

Manifestation

• Number of item you're working on at the same time
• A specification that is written and lying around waiting to be implemented
• Implemented code that you haven't checked in and integrated with the product code
• Untested code: build up a stock of unfinished work

Little's Law

Cycle time = Work in process / Throughput

To decrease cycle time, do less work at the same time


Low WIP

• Less work in process leads to quicker flow through the process
• Shorter lead time
• Quick feed back on quality
• Waste reduction is easier
• Information management is simpler
• Reduce overall complexity
• Create a little tension in the workflow: expose problems in your system
• Too low: resources become idle

High WIP

• Extra effort for coordination (with no value added)
• Context switching
• Delay (+risk of obsolete spec)
• Extra work (from longer feedback: fixing a bug introduced 3 months ago)
• Slow feedback
• Adaptability is lower
• Team motivation is lower
• Increase overall risk of failure

Outcome

Can create a vicious circle.