The Art and Science of Limiting Work in Progress (WIP)
- 1 PDU &1 SEU
- Sanjay Kumar
Until five to ten years ago, in the pre-agile days, the standard way of executing a project was to go through different project phases (analysis, design, development and testing) with the entire scope in hand. There was no WIP limit – 100% of the work was in progress. It was a rigid process, changes were frowned upon – redirecting change requests from client to a Change Control Board (CCB) was one way to discourage such unwelcome changes.
As market dynamics changed, responding to change in a more effective manner became not just a priority, but a necessity. Most agile methods/frameworks use the idea of limiting work in progress in one way or the other – it is the backbone of key agile practices like adaptive planning, faster feedback cycle and emergent design.
In this webinar, we will take a closer look at how limiting work in progress helps improve the flow of work, and explore some guidelines on how to effectively limit the work in progress. While the inspiration comes from Kanban, the art and science of limiting WIP is applicable equally well to other frameworks/methos like Scrum, XP, etc.