Limiting Work in Progress

Why Limit Work in Progress?

• Work in progress (WIP) is considered waste in lean concepts.
• WIP consists of tasks that have been started but not completed.
• Too much WIP can lead to inefficiencies and bottlenecks.
• A Kanban board helps in managing and limiting WIP.
• WIP represents money spent without immediate returns.

Risks of Excessive Work in Progress

• Hides bottlenecks that slow down the process.
• Delays identifying risks until work is done.
• Examples of risks:
  • Software crashes during development.
  • Server hard drive failures.
• Work in progress increases potential risks as tasks are being completed.

Example: If you're not driving a car, you cannot get into an accident. However, the moment you start driving, the risk of an accident exists.

Agile Approach to Limiting Work in Progress

• Agile projects aim to optimize and minimize work in progress.
• Ensures efficiency by keeping WIP low.
• Using a Kanban board helps control WIP in each phase or cycle.