3 ms·
I think what is important is the gratification when a team delivers a feature. If a team can produce x amount of work, if this is divided over large number of W
by mikesabbagh 6y ago
I think what is important is the gratification when a team delivers a feature. If a team can produce x amount of work, if this is divided over large number of WIP, the team will deliver much less features and will be less happy and satisfied.
but if the team work on a smaller number of features, the team will complete and deliver more features and be happier and more excited to work more
- kqr 6y agoSure, gratification is important, but what really drives both gratification and everything else is feedback. When you have less simultaneous work you get done faster, which means you make decisions based on less old information. Imagine trying to... I don't know, play soccer where your body movements have a five-second delay. It'll feel awful because by the time you decide to move your body you know it's going to be too late for any detailed knowledge so you'll have to make do with some very primitive heuristics like "flail in the direction of the ball and hope to get lucky". That's what too much WIP is. Limiting it is starting to move and react in real time to changes.