WIP Limit for Developers
summary
Explains using WIP (work-in-progress) limits for software developers to improve flow. Describes the problem of too much concurrent work and proposes applying explicit WIP limits (a Kanban/flow control technique) to reduce context switching and increase delivery predictability.
AI-written summary · about
chapters (9)
- 0:00WIP limit for devs
- 1:16Theory of constraints
- 2:25River technique demo
- 10:50Code refactoring with River
- 22:26Test & Commit / Revert
- 30:09Refactoring with TCR & limits
- 35:59Commit strategies
- 40:12Commits in version control
- 43:05Summary
related talks
47mHow it goes to heck in a handbasket
30mTaming the Chaos: Beyond the Quick Wins
33mTaming The Chaos: After The Quick Wins
31mHow we used Kanban in Operations to Get Things Done
01h 27mPNSQC 2014 - Halim Dunsky
01h 32mPNSQC 2014 - Hillel Glazer
23mWhat is the Unit of Work in Modern Delivery?
41mEliminate waste..are we doing it all wrong?
